GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T22:07:19Z,
for the dataset file:///shared/torun-pl.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • Miejski Zakład Komunikacji w Toruniu
  • Miejski Zakład Komunikacji w Toruniu

Feed Info

Publisher Name:
Wydział Gospodarki Komunalnej w Toruniu
Feed Email:
N/A
Feed Language:
Polish
Feed Start Date:
2026-01-01
Feed End Date:
2026-02-28

Files included

  1. [Content_Types].xml
  2. agency.txt
  3. calendar.txt
  4. calendar_dates.txt
  5. feed_info.txt
  6. routes.txt
  7. shapes.txt
  8. stop_times.txt
  9. stops.txt
  10. transfers.txt
  11. trips.txt

Counts

  • Agencies: 2
  • Blocks: 511
  • Routes: 314
  • Shapes: 314
  • Stops: 900
  • Trips: 7962

Specification Compliance report

970 notices reported (0 errors, 969 warnings, 1 infos)

Notice Code Severity Total
duplicate_route_name WARNING 3

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`.
52 "934" 68 "117" "40" "Port Drzewny -> Bielawy-40" 3 "1"
60 "873" 89 "926" "34" "Plac Skalskiego -> Olimpijska P&R-34" 3 "1"
121 "563" 273 "263" "115" "Krobia -> Dworzec Wschodni-115" 3 "1"
expired_calendar WARNING 930

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

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

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
11 "93849"
13 "93851"
23 "96494"
60 "93858"
61 "93859"
63 "96496"
72 "93862"
85 "93863"
88 "93865"
90 "93866"
95 "96497"
109 "96498"
111 "93874"
115 "93877"
125 "93883"
131 "93887"
133 "93888"
148 "93893"
152 "93896"
159 "93897"
166 "93901"
173 "96500"
192 "93908"
198 "93909"
200 "93910"
203 "93911"
218 "93916"
264 "93931"
265 "93933"
276 "93936"
281 "96504"
291 "93938"
298 "93940"
304 "93942"
306 "93943"
307 "93944"
311 "93946"
315 "96505"
316 "93947"
330 "93951"
333 "93952"
348 "93958"
359 "93959"
365 "93964"
370 "93967"
373 "93968"
384 "93972"
392 "96509"
400 "93976"
401 "93977"
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
missing_recommended_field WARNING 1

missing_recommended_field

A recommended field is missing.

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

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.
"feed_info.txt" 2 "feed_version"
mixed_case_recommended_field WARNING 33

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" "MAZOWIECKA (pętla) 00" 20
"stops.txt" "stop_name" "PLAC ŚW. KATARZYNY 03" 45
"stops.txt" "stop_name" "ALEJA SOLIDARNOŚCI 02" 46
"stops.txt" "stop_name" "LUBICZ GÓRNY-OSIEDLE 00" 65
"stops.txt" "stop_name" "MAZOWIECKA (pętla) 01" 66
"stops.txt" "stop_name" "ALEJA SOLIDARNOŚCI 01" 96
"stops.txt" "stop_name" "DWORZEC GŁÓWNY 03" 105
"stops.txt" "stop_name" "PLAC RAPACKIEGO 01" 108
"stops.txt" "stop_name" "PRZY LESIE 01" 167
"stops.txt" "stop_name" "OSIEDLE LEŚNE - POLANA 01" 239
"stops.txt" "stop_name" "PLAC RAPACKIEGO 02" 244
"stops.txt" "stop_name" "DWORZEC GŁÓWNY 00" 246
"stops.txt" "stop_name" "NAD STRUGĄ 00" 287
"stops.txt" "stop_name" "PLAC SKALSKIEGO 01" 307
"stops.txt" "stop_name" "PLAC SKALSKIEGO 02" 312
"stops.txt" "stop_name" "PLAC SKALSKIEGO 03" 329
"stops.txt" "stop_name" "PORT DRZEWNY 00" 372
"stops.txt" "stop_name" "KOLONIA PAPOWSKA 01" 484
"stops.txt" "stop_name" "PLAC ŚW. KATARZYNY 04" 495
"stops.txt" "stop_name" "PORT DRZEWNY 01" 539
"stops.txt" "stop_name" "NAD STRUGĄ 01" 549
"stops.txt" "stop_name" "CMENTARZ CENTRALNY 01" 579
"stops.txt" "stop_name" "OLIMPIJSKA P&R nż. 03" 601
"stops.txt" "stop_name" "WSCHODNIA (pętla) 01" 637
"stops.txt" "stop_name" "LUBICZ GÓRNY-OSIEDLE 02" 662
"stops.txt" "stop_name" "OSIEDLE LEŚNE - POLANA 00" 680
"stops.txt" "stop_name" "LUBICZ GÓRNY-OSIEDLE 01" 683
"stops.txt" "stop_name" "ROZGARTY - STARA SZKOŁA 01" 703
"stops.txt" "stop_name" "DZIAŁKI RUDAK 02" 726
"stops.txt" "stop_name" "PLAC ŚW. KATARZYNY 09" 728
"stops.txt" "stop_name" "DWORZEC WSCHODNI 08" 729
"stops.txt" "stop_name" "EC GRĘBOCIN 01" 833
"stops.txt" "stop_name" "GRĘBOCIN (pętla) 04" 892
stop_too_far_from_shape WARNING 1

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.
1526 "209" "60899" 35630 "64" "Bractwa Kurkowego nż. 01" [53.0404550874477,18.5817861557007] 627.569619304474
unknown_file INFO 1

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"[Content_Types].xml"