GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.0.0 at 2025-05-16T14:55:32Z,
for the dataset file:///tmp/1_in.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. routes.txt
  5. stop_times.txt
  6. stops.txt
  7. transfers.txt
  8. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 15
  • Shapes: 0
  • Stops: 706
  • Trips: 382

Specification Compliance report

49 notices reported (1 errors, 48 warnings, 0 infos)

Notice Code Severity Total
stop_time_with_arrival_before_previous_departure_time ERROR 1

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.
8119 8118 "TP844643" "00:00:00" "07:26:00"
fast_travel_between_far_stops WARNING 1

fast_travel_between_far_stops

A transit vehicle moves too fast between two far stops.

Two stops are considered "far" if they are more than 10 km apart. This normally indicates a more serious problem than too fast travel between consecutive stops.

The speed threshold depends on route type and are the same as fast_travel_between_consecutive_stops.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip. tripId (?) `trip_id` of the problematic trip. routeId (?) `route_id` of the problematic trip. speedKph (?) Travel speed (km/h). distanceKm (?) Distance between stops (km). csvRowNumber1 (?) The row number of the first stop time. stopSequence1 (?) `stop_sequence` of the first stop. stopId1 (?) `stop_id` of the first stop. stopName1 (?) `stop_name` of the first stop. departureTime1 (?) `departure_time` of the first stop. csvRowNumber2 (?) The row number of the second stop time. stopSequence2 (?) `stop_sequence` of the second stop. stopId2 (?) `stop_id` of the second stop. stopName2 (?) `stop_name` of the second stop. arrivalTime2 (?) `arrival_time` of the second stop.
373 "TP844643" "11-125" 640.3404641153464 10.672341068589107 8110 10 "767" "Centre Diefenbach" "07:05:00" 8119 19 "CABUS.CABNav507" "Rue des Champs Woustviller" "00:00:00"
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
mixed_case_recommended_field WARNING 39

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_long_name" "PUTTELANGE - SARRALBE" 2
"routes.txt" "route_long_name" "11-125 PUTTELANGE-WOUSTVILLER-SARREGUEMINES" 16
"stops.txt" "stop_name" "ST JROHR 22 NOV" 466
"stops.txt" "stop_name" "RUE DE BELGIQUE" 473
"stops.txt" "stop_name" "RUE ST JACQUES" 479
"stops.txt" "stop_name" "MAIRIE ECOLE" 488
"stops.txt" "stop_name" "RUE ERNEST SOLVAY" 507
"stops.txt" "stop_name" "RUE DE TAVAUX" 509
"stops.txt" "stop_name" "BITCHE CORA" 511
"stops.txt" "stop_name" "LE HOHBERG" 514
"stops.txt" "stop_name" "LYCEE NOMINE" 517
"stops.txt" "stop_name" "PARC MUGUET" 520
"stops.txt" "stop_name" "RUE DE NANCY" 529
"stops.txt" "stop_name" "RUE DE SARREGUEMINES" 531
"stops.txt" "stop_name" "LYCEE DE PANGE" 533
"stops.txt" "stop_name" "ROUTE DE GRUNDVILLER HECKENRANSBACH" 681
"stops.txt" "stop_name" "CARREFOUR FRAUENBERG" 688
"trips.txt" "trip_headsign" "RUE DE ZETTING" 15
"trips.txt" "trip_headsign" "RUE DE ZETTING" 16
"trips.txt" "trip_headsign" "HERMESKAPPEL CARREFOUR" 41
"trips.txt" "trip_headsign" "CENTRE NAUTIQUE" 54
"trips.txt" "trip_headsign" "CENTRE NAUTIQUE" 55
"trips.txt" "trip_headsign" "CES JEAN JAURES" 56
"trips.txt" "trip_headsign" "GARE ROUTIERE" 67
"trips.txt" "trip_headsign" "HETRES SAPINS" 130
"trips.txt" "trip_headsign" "HETRES SAPINS" 131
"trips.txt" "trip_headsign" "RUE NATIONALE ST JEAN ROHRBACH" 158
"trips.txt" "trip_headsign" "RUE NATIONALE ST JEAN ROHRBACH" 169
"trips.txt" "trip_headsign" "ST JEAN ROHRBACH" 202
"trips.txt" "trip_headsign" "REMERING LES PUTTELANGE" 280
"trips.txt" "trip_headsign" "SAINT JEAN ROHRBACH" 291
"trips.txt" "trip_headsign" "PUTTELANGE AUX LACS" 302
"trips.txt" "trip_headsign" "SAINT JEAN ROHRBACH" 313
"trips.txt" "trip_headsign" "SAINTE BARBE" 315
"trips.txt" "trip_headsign" "REMERING LES PUTTALANGE" 319
"trips.txt" "trip_headsign" "REMERIING LES PUTTELANGE" 320
"trips.txt" "trip_headsign" "CES JEAN JAURES" 368
"trips.txt" "trip_headsign" "HOPITAL ROBERT PAX" 369
"trips.txt" "trip_headsign" "HOPITAL ROBERT PAX" 370
route_color_contrast WARNING 2

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeColor (?) The faulty record's HTML route color. routeTextColor (?) The faulty record's HTML route text color.
"CABUS.CABNav24" 11 "#F196DF" "#FFFFFF"
"CABUS.CABNav4" 13 "#ECCE49" "#FFFFFF"
route_long_name_contains_short_name WARNING 4

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`.
"CABUS.CABNav10" 4 "Desserte 3" "Desserte 3"
"CABUS.CABNav5" 14 "Desserte 1" "Desserte 1"
"CABUS.CABNav9" 15 "Desserte 2" "Desserte 2"
"11-125" 16 "11-125" "11-125 PUTTELANGE-WOUSTVILLER-SARREGUEMINES"
unexpected_enum_value WARNING 1

unexpected_enum_value

An enum has an unexpected value.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row number of the faulty record. fieldName (?) The name of the field where the error occurred. fieldValue (?) Faulty value.
"routes.txt" 2 "route_type" 715