Search
  1. Home
  2. Poland Feeds
  3. koleje-autobusowy
  4. Source Data Validation Report

koleje-autobusowy — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-07-17T18:52:03Z,
for the dataset file:///shared/koleje-autobusowy_36de9bbb.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
kiedyPrzyjedzie.pl
Feed Email:
N/A
Feed Language:
Polish
Feed Start Date:
2026-07-16
Feed End Date:
2026-12-31

Files included

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

Counts

  • Agencies: 1
  • Blocks: 326
  • Routes: 69
  • Shapes: 0
  • Stops: 6525
  • Trips: 2621

Specification Compliance report

31 notices reported (0 errors, 25 warnings, 6 infos)

Notice Code Severity Total
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 23

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" "KRAKÓW BATOWICE" 1963
"stops.txt" "stop_name" "KRAKÓW BATOWICE" 1964
"stops.txt" "stop_name" "KRAKÓW BATOWICE" 1965
"stops.txt" "stop_name" "KRAKÓW KOŚCIELNIKI" 2052
"stops.txt" "stop_name" "KRAKÓW KOŚCIELNIKI" 2053
"stops.txt" "stop_name" "KRAKÓW LUBOCZA" 2063
"stops.txt" "stop_name" "KRAKÓW LUBOCZA" 2064
"stops.txt" "stop_name" "KRAKÓW NOWA HUTA" 2091
"stops.txt" "stop_name" "KRAKÓW NOWA HUTA" 2092
"stops.txt" "stop_name" "KRAKÓW PIASTÓW" 2118
"stops.txt" "stop_name" "KRAKÓW PIASTÓW" 2119
"stops.txt" "stop_name" "KRAKÓW PIASTÓW" 2120
"stops.txt" "stop_name" "KRAKÓW PRZYLASEK" 2144
"stops.txt" "stop_name" "KRAKÓW PRZYLASEK" 2145
"stops.txt" "stop_name" "PODBORY SKAWIŃSKIE" 3669
"stops.txt" "stop_name" "PODBORY SKAWIŃSKIE" 3670
"stops.txt" "stop_name" "PODBORY SKAWIŃSKIE" 3671
"stops.txt" "stop_name" "SŁOMNIKI MIASTO" 4519
"stops.txt" "stop_name" "SŁOMNIKI MIASTO" 4520
"stops.txt" "stop_name" "WIELKIE DROGI" 5615
"stops.txt" "stop_name" "WIELKIE DROGI" 5616
"stops.txt" "stop_name" "WIELKIE DROGI" 5617
"routes.txt" "route_long_name" "ZKA SKA2" 70
trip_headsign_matches_intermediate_stop INFO 3

trip_headsign_matches_intermediate_stop

Trip headsign matches the name of an intermediate stop, not the last stop.

The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record in `trips.txt`. tripId (?) The id of the trip with the problematic headsign. tripHeadsign (?) The headsign value that matches an intermediate stop name. stopId1 (?) The id of the intermediate stop whose name matches the headsign. stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign. stopId2 (?) The id of the actual last stop of the trip.
46 "35738389_7952" "Ochotnica Dolna Młynne Urząd Gminy" "1909518" 50 "1909517"
49 "35738392_7952" "Ochotnica Dolna Młynne Urząd Gminy" "1909518" 50 "1909517"
52 "35738395_7952" "Ochotnica Dolna Młynne Urząd Gminy" "1909518" 50 "1909517"
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.
"agency.txt" "ticketing_deep_link_id" 7
unknown_file INFO 2

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"ticketing_deep_links.txt"
"ticketing_identifiers.txt"