GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T15:45:36Z,
for the dataset file:///shared/um-torun.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:
Mikołaj Kuranowski
Publisher URL:
https://mkuran.pl/gtfs/
Feed Email:
N/A
Feed Language:
Polish
Feed Start Date:
2026-01-01
Feed End Date:
2026-02-28

Files included


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

Counts


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

Specification Compliance report

1270 notices reported (0 errors, 1270 warnings, 0 infos)

Notice Code Severity Total
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
mixed_case_recommended_field WARNING 338

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.

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

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" "ALEJA SOLIDARNOŚCI" 46
"stops.txt" "stop_name" "LUBICZ GÓRNY-OSIEDLE" 65
"stops.txt" "stop_name" "ALEJA SOLIDARNOŚCI" 96
"stops.txt" "stop_name" "PLAC RAPACKIEGO" 108
"stops.txt" "stop_name" "PLAC RAPACKIEGO" 244
"stops.txt" "stop_name" "PLAC SKALSKIEGO" 307
"stops.txt" "stop_name" "PLAC SKALSKIEGO" 312
"stops.txt" "stop_name" "PLAC SKALSKIEGO" 329
"stops.txt" "stop_name" "LUBICZ GÓRNY-OSIEDLE" 662
"stops.txt" "stop_name" "LUBICZ GÓRNY-OSIEDLE" 683
"stops.txt" "stop_name" "ROZGARTY - STARA SZKOŁA" 703
"trips.txt" "trip_headsign" "LUBICZ GÓRNY-OSIEDLE" 4
"trips.txt" "trip_headsign" "PLAC SKALSKIEGO" 22
"trips.txt" "trip_headsign" "LUBICZ GÓRNY-OSIEDLE" 38
"trips.txt" "trip_headsign" "ALEJA SOLIDARNOŚCI" 40
"trips.txt" "trip_headsign" "PLAC SKALSKIEGO" 72
"trips.txt" "trip_headsign" "ALEJA SOLIDARNOŚCI" 102
"trips.txt" "trip_headsign" "PLAC SKALSKIEGO" 130
"trips.txt" "trip_headsign" "ROZGARTY - STARA SZKOŁA" 151
"trips.txt" "trip_headsign" "ROZGARTY - STARA SZKOŁA" 166
"trips.txt" "trip_headsign" "ALEJA SOLIDARNOŚCI" 203
"trips.txt" "trip_headsign" "LUBICZ GÓRNY-OSIEDLE" 239
"trips.txt" "trip_headsign" "PLAC SKALSKIEGO" 306
"trips.txt" "trip_headsign" "PLAC SKALSKIEGO" 345
"trips.txt" "trip_headsign" "LUBICZ GÓRNY-OSIEDLE" 346
"trips.txt" "trip_headsign" "LUBICZ GÓRNY-OSIEDLE" 388
"trips.txt" "trip_headsign" "PLAC SKALSKIEGO" 413
"trips.txt" "trip_headsign" "PLAC SKALSKIEGO" 421
"trips.txt" "trip_headsign" "LUBICZ GÓRNY-OSIEDLE" 441
"trips.txt" "trip_headsign" "LUBICZ GÓRNY-OSIEDLE" 470
"trips.txt" "trip_headsign" "LUBICZ GÓRNY-OSIEDLE" 479
"trips.txt" "trip_headsign" "ALEJA SOLIDARNOŚCI" 489
"trips.txt" "trip_headsign" "PLAC SKALSKIEGO" 509
"trips.txt" "trip_headsign" "PLAC SKALSKIEGO" 566
"trips.txt" "trip_headsign" "ROZGARTY - STARA SZKOŁA" 583
"trips.txt" "trip_headsign" "PLAC SKALSKIEGO" 615
"trips.txt" "trip_headsign" "LUBICZ GÓRNY-OSIEDLE" 637
"trips.txt" "trip_headsign" "LUBICZ GÓRNY-OSIEDLE" 701
"trips.txt" "trip_headsign" "ROZGARTY - STARA SZKOŁA" 746
"trips.txt" "trip_headsign" "LUBICZ GÓRNY-OSIEDLE" 758
"trips.txt" "trip_headsign" "PLAC SKALSKIEGO" 768
"trips.txt" "trip_headsign" "LUBICZ GÓRNY-OSIEDLE" 814
"trips.txt" "trip_headsign" "PLAC SKALSKIEGO" 874
"trips.txt" "trip_headsign" "LUBICZ GÓRNY-OSIEDLE" 877
"trips.txt" "trip_headsign" "ROZGARTY - STARA SZKOŁA" 893
"trips.txt" "trip_headsign" "PLAC SKALSKIEGO" 939
"trips.txt" "trip_headsign" "ROZGARTY - STARA SZKOŁA" 947
"trips.txt" "trip_headsign" "PLAC SKALSKIEGO" 957
"trips.txt" "trip_headsign" "ROZGARTY - STARA SZKOŁA" 978
"trips.txt" "trip_headsign" "PLAC SKALSKIEGO" 1011
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 "22101" "Bractwa Kurkowego" [53.0404550874477,18.5817861557007] 627.569619304474