GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T18:12:09Z,
for the dataset file:///shared/mdl.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. frequencies.txt
  4. routes.txt
  5. shapes.txt
  6. stop_times.txt
  7. stops.txt
  8. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 10
  • Shapes: 10
  • Stops: 50
  • Trips: 122

Specification Compliance report

33 notices reported (0 errors, 32 warnings, 1 infos)

Notice Code Severity Total
duplicate_route_name WARNING 2

duplicate_route_name

Two distinct routes have either the same route_short_name, the same route_long_name, or the same combination of route_short_name and route_long_name.

All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.

Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route.

Example of bad data:

route_id route_short_name route_long_name
route1 U1 Southern
route2 U1 Southern

You can see more about this notice here.

csvRowNumber1 (?) The row number of the first occurrence. routeId1 (?) The id of the the first occurrence. csvRowNumber2 (?) The row number of the other occurrence. routeId2 (?) The id of the the other occurrence. routeShortName (?) Common `routes.route_short_name`. routeLongName (?) Common `routes.route_long_name`. routeTypeValue (?) Common `routes.route_type`. agencyId (?) Common `routes.agency_id`.
3 "4922" 5 "165" "" "Amarela - RATO" 1 "2"
4 "164" 11 "4921" "" "Amarela - ODIVELAS" 1 "2"
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 19

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" "ALTO DOS MOINHOS" 5
"stops.txt" "stop_name" "AMADORA ESTE" 7
"stops.txt" "stop_name" "BAIXA-CHIADO" 13
"stops.txt" "stop_name" "BELA VISTA" 14
"stops.txt" "stop_name" "CABO RUIVO" 15
"stops.txt" "stop_name" "CAIS DO SODRÉ" 16
"stops.txt" "stop_name" "CAMPO GRANDE" 17
"stops.txt" "stop_name" "CAMPO PEQUENO" 18
"stops.txt" "stop_name" "CIDADE UNIVERSITÁRIA" 21
"stops.txt" "stop_name" "COLÉGIO MILITAR-LUZ" 22
"stops.txt" "stop_name" "JARDIM ZOOLÓGICO" 26
"stops.txt" "stop_name" "MARQUÊS DE POMBAL" 29
"stops.txt" "stop_name" "MARTIM MONIZ" 30
"stops.txt" "stop_name" "PRAÇA DE ESPANHA" 39
"stops.txt" "stop_name" "QUINTA DAS CONCHAS" 40
"stops.txt" "stop_name" "SANTA APOLÓNIA" 47
"stops.txt" "stop_name" "SÃO SEBASTIÃO" 48
"stops.txt" "stop_name" "SR. ROUBADO" 49
"stops.txt" "stop_name" "TERREIRO DO PAÇO" 51
stop_too_far_from_shape WARNING 10

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
92 "170" "28046080" 1064 "M08" "SÃO SEBASTIÃO" [38.73483,-9.14528] 731.8420066852195
107 "171" "28046091" 1196 "M49" "AEROPORTO" [38.77499000000001,-9.11538] 1327.441170210009
2 "164" "28046026" 702 "M19" "RATO" [38.72593,-9.14965] 789.3634958425313
15 "165" "28046043" 923 "M42" "ODIVELAS" [38.78576,-9.1719] 864.2127467843679
28 "166" "28045988" 18 "M50" "REBOLEIRA" [38.75855000000001,-9.21794] 886.5816668427296
47 "167" "28046009" 396 "M46" "SANTA APOLÓNIA" [38.70722,-9.13286] 1183.420573837525
66 "168" "28046118" 1530 "M37" "TELHEIRAS" [38.76016,-9.15788] 711.8652132622514
79 "169" "28046121" 1569 "M30" "CAIS DO SODRÉ" [38.71041000000001,-9.14018] 703.0421849552085
122 "4921" "25816318" 2 "M19" "RATO" [38.72593,-9.14965] 789.3634958425313
123 "4922" "25816319" 10 "M13" "CAMPO GRANDE" [38.75144,-9.159150000000002] 975.8549378698358
unknown_column INFO 1

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the unknown column. index (?) The index of the faulty column.
"shapes.txt" "shape_seg_id" 1