GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T16:49:17Z,
for the dataset file:///shared/gtfsscolai-95ec28294ce6ce.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
French
Feed Start Date:
2025-01-01
Feed End Date:
2026-12-31

Files included

  1. agency.txt
  2. calendar.txt
  3. feed_info.txt
  4. routes.txt
  5. stop_times.txt
  6. stops.txt
  7. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 36
  • Shapes: 0
  • Stops: 194
  • Trips: 136

Specification Compliance report

42 notices reported (2 errors, 40 warnings, 0 infos)

Notice Code Severity Total
stop_time_with_arrival_before_previous_departure_time ERROR 2

stop_time_with_arrival_before_previous_departure_time

Backwards time travel between stops in stop_times.txt

For a given trip_id, the arrival_time of (n+1)-th stoptime in sequence must not precede the departure_time of n-th stoptime in sequence in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. prevCsvRowNumber (?) The row of the previous stop time. tripId (?) The trip_id associated to the faulty record. arrivalTime (?) Arrival time at the faulty record. departureTime (?) Departure time at the previous stop time.
501 500 "102870-T19r" "17:50:00" "17:52:00"
490 489 "102870-T19Mr" "13:50:00" "13:52:00"
mixed_case_recommended_field WARNING 35

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

Good examples:
Field Text Dataset
"Schwerin, Hauptbahnhof" Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin" NYC Ferry
"Campo Grande Norte" Carris
Bad examples:
Field Text
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"routes.txt" "route_short_name" "RPI berjou" 7
"routes.txt" "route_short_name" "RPI segrie fontaine" 9
"trips.txt" "trip_headsign" "F1 aller mercredi" 6
"trips.txt" "trip_headsign" "F1 retour mercredi" 7
"trips.txt" "trip_headsign" "F2 aller mercredi" 11
"trips.txt" "trip_headsign" "F2 retour mercredi" 12
"trips.txt" "trip_headsign" "F3 aller mercredi" 16
"trips.txt" "trip_headsign" "F3 retour mercredi" 17
"trips.txt" "trip_headsign" "F4 aller mercredi" 21
"trips.txt" "trip_headsign" "F5 aller mercredi" 24
"trips.txt" "trip_headsign" "F5 retour mercredi" 25
"trips.txt" "trip_headsign" "F6 aller mercredi" 29
"trips.txt" "trip_headsign" "F6 retour mercredi" 30
"trips.txt" "trip_headsign" "F7 aller mercredi" 34
"trips.txt" "trip_headsign" "F7 retour mercredi" 35
"trips.txt" "trip_headsign" "F8 aller mercredi" 39
"trips.txt" "trip_headsign" "F8 retour mercredi" 40
"trips.txt" "trip_headsign" "F9 aller mercredi" 44
"trips.txt" "trip_headsign" "F9 retour mercredi" 45
"trips.txt" "trip_headsign" "F16 aller mercredi" 53
"trips.txt" "trip_headsign" "F16 retour mercredi" 54
"trips.txt" "trip_headsign" "F10 aller mercredi" 58
"trips.txt" "trip_headsign" "F10 retour mercredi" 59
"trips.txt" "trip_headsign" "F12 aller mercredi" 62
"trips.txt" "trip_headsign" "F14 retour mercredi" 63
"trips.txt" "trip_headsign" "F13 aller mercredi" 66
"trips.txt" "trip_headsign" "F13 retour mercredi" 67
"trips.txt" "trip_headsign" "F14 aller mercredi" 71
"trips.txt" "trip_headsign" "F14 retour mercredi" 72
"trips.txt" "trip_headsign" "F11 aller mercredi" 119
"trips.txt" "trip_headsign" "F11 retour mercredi" 120
"trips.txt" "trip_headsign" "B1 aller mercredi" 131
"trips.txt" "trip_headsign" "B1 retour mercredi" 132
"trips.txt" "trip_headsign" "B2 aller mercredi" 135
"trips.txt" "trip_headsign" "B2 retour mercredi" 136
route_long_name_contains_short_name WARNING 1

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name Dataset
"N"/"Judah" Muni San Fransisco
"6"/"ML King Jr Blvd" Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent" STM Montreal
"1"/"Rangiora/Cashmere" Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`. routeLongName (?) The faulty record's `route_long_name`.
"102870-36" 12 "RPI LA Carneille" "RPI LA Carneille Ronfeugerai"
route_short_name_too_long WARNING 4

route_short_name_too_long

Short name of a route is too long (more than 12 characters).

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`.
"102870-32" 4 "RPI-Chap-ST Clair"
"102870-35" 9 "RPI segrie fontaine"
"102870-34" 10 "RPI Monts D'Andaine"
"102870-36" 12 "RPI LA Carneille"