GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-04T09:44:22Z,
for the dataset file:///shared/autunois-morvan_8f734c68.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. stops_radius.txt
  8. trip_kilometers.txt
  9. trips.txt
  10. trips_infos.txt
  11. trips_service.txt

Counts


  • Agencies: 0
  • Blocks: 0
  • Routes: 1
  • Shapes: 0
  • Stops: 16
  • Trips: 23

Specification Compliance report

287 notices reported (265 errors, 18 warnings, 4 infos)

Notice Code Severity Total
decreasing_or_equal_stop_time_distance ERROR 264

decreasing_or_equal_stop_time_distance

Decreasing or equal shape_dist_traveled in stop_times.txt.

When sorted by stop_times.stop_sequence, two consecutive entries in stop_times.txt should have increasing distance, based on the field shape_dist_traveled. If the values are equal, this is considered as an error.

You can see more about this notice here.

Only the first 50 of 264 affected records are displayed below.

tripId (?) The id of the faulty trip. stopId (?) The id of the faulty stop. csvRowNumber (?) The row number from `stop_times.txt`. shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record. stopSequence (?) The faulty record's `stop_times.stop_sequence`. prevCsvRowNumber (?) The row number from `stop_times.txt` of the previous stop time. prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous stop time. prevStopSequence (?) The previous record's `stop_times.stop_sequence`.
"876039" "876023" 101 0.0 2 100 0.0 1
"876039" "876022" 102 0.0 3 101 0.0 2
"876039" "876021" 103 0.0 4 102 0.0 3
"876039" "876020" 104 0.0 5 103 0.0 4
"876039" "876025" 105 0.0 6 104 0.0 5
"876039" "876018" 106 0.0 7 105 0.0 6
"876039" "876017" 107 0.0 8 106 0.0 7
"876039" "876026" 108 0.0 9 107 0.0 8
"876039" "876015" 109 0.0 10 108 0.0 9
"876039" "876014" 110 0.0 11 109 0.0 10
"876039" "876013" 111 0.0 12 110 0.0 11
"876039" "876012" 112 0.0 13 111 0.0 12
"876038" "876023" 87 0.0 2 86 0.0 1
"876038" "876022" 88 0.0 3 87 0.0 2
"876038" "876021" 89 0.0 4 88 0.0 3
"876038" "876020" 90 0.0 5 89 0.0 4
"876038" "876025" 91 0.0 6 90 0.0 5
"876038" "876018" 92 0.0 7 91 0.0 6
"876038" "876017" 93 0.0 8 92 0.0 7
"876038" "876026" 94 0.0 9 93 0.0 8
"876038" "876015" 95 0.0 10 94 0.0 9
"876038" "876014" 96 0.0 11 95 0.0 10
"876038" "876013" 97 0.0 12 96 0.0 11
"876038" "876012" 98 0.0 13 97 0.0 12
"876049" "876012" 233 0.0 2 232 0.0 1
"876049" "876013" 234 0.0 3 233 0.0 2
"876049" "876014" 235 0.0 4 234 0.0 3
"876049" "876015" 236 0.0 5 235 0.0 4
"876049" "876016" 237 0.0 6 236 0.0 5
"876049" "876017" 238 0.0 7 237 0.0 6
"876049" "876018" 239 0.0 8 238 0.0 7
"876049" "876019" 240 0.0 9 239 0.0 8
"876049" "876020" 241 0.0 10 240 0.0 9
"876049" "876021" 242 0.0 11 241 0.0 10
"876049" "876022" 243 0.0 12 242 0.0 11
"876049" "876023" 244 0.0 13 243 0.0 12
"876037" "876012" 73 0.0 2 72 0.0 1
"876037" "876013" 74 0.0 3 73 0.0 2
"876037" "876014" 75 0.0 4 74 0.0 3
"876037" "876015" 76 0.0 5 75 0.0 4
"876037" "876016" 77 0.0 6 76 0.0 5
"876037" "876017" 78 0.0 7 77 0.0 6
"876037" "876018" 79 0.0 8 78 0.0 7
"876037" "876019" 80 0.0 9 79 0.0 8
"876037" "876020" 81 0.0 10 80 0.0 9
"876037" "876021" 82 0.0 11 81 0.0 10
"876037" "876022" 83 0.0 12 82 0.0 11
"876037" "876023" 84 0.0 13 83 0.0 12
"876048" "876012" 219 0.0 2 218 0.0 1
"876048" "876013" 220 0.0 3 219 0.0 2
missing_required_field ERROR 1

missing_required_field

A required field is missing.

The given field has no value in some input row, even though values are required.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"agency.txt" 2 "agency_url"
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 16

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.
"stops.txt" "stop_name" "ST PANTALEON - LES TUILERIES" 2
"stops.txt" "stop_name" "ST PANTALEON - LES CHARMILLES" 3
"stops.txt" "stop_name" "ST PANTALEON - ECOLE VICTOR HU" 4
"stops.txt" "stop_name" "ST PANTALEON - PRIEURE ST MART" 5
"stops.txt" "stop_name" "ST PANTALEON - MAISON DE SANTE" 6
"stops.txt" "stop_name" "AUTUN - ST JEAN GALLION" 7
"stops.txt" "stop_name" "AUTUN - CROIX VERTE" 8
"stops.txt" "stop_name" "AUTUN - HEXAGONE" 9
"stops.txt" "stop_name" "AUTUN - SOUS PREFECTURE" 10
"stops.txt" "stop_name" "AUTUN - CHAMP DE MARS" 11
"stops.txt" "stop_name" "AUTUN - CHARLES DE GAULLE" 12
"stops.txt" "stop_name" "AUTUN - GARE SNCF" 13
"stops.txt" "stop_name" "AUTUN - CENTRE HOSPITALIER" 14
"stops.txt" "stop_name" "AUTUN - GARIBALDI" 15
"stops.txt" "stop_name" "AUTUN - LES MARBRES" 16
"stops.txt" "stop_name" "AUTUN - PORTE ST ANDRE" 17
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20260504" "20261023" "20280825"
unknown_file INFO 4

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"stops_radius.txt"
"trips_infos.txt"
"trip_kilometers.txt"
"trips_service.txt"