GTFS Schedule Validation Report

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

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
UM Wrocław
Feed Email:
N/A
Feed Language:
Polish
Feed Start Date:
2017-03-25
Feed End Date:
2017-04-24

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. control_stops.txt
  5. feed_info.txt
  6. route_types.txt
  7. routes.txt
  8. stop_times.txt
  9. stops.txt
  10. trips.txt
  11. variants.txt
  12. vehicle_types.txt

Counts

  • Agencies: 6
  • Blocks: 0
  • Routes: 114
  • Shapes: 0
  • Stops: 2080
  • Trips: 39410

Specification Compliance report

13907 notices reported (0 errors, 13897 warnings, 10 infos)

Notice Code Severity Total
expired_calendar WARNING 4

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.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
2 "4"
3 "8"
4 "6"
5 "3"
feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20260123" "20170424" "20260130"
leading_or_trailing_whitespaces WARNING 14

leading_or_trailing_whitespaces

The value in CSV file has leading or trailing whitespaces.

This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser.

The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
"routes.txt" 2 "route_short_name" " 1"
"routes.txt" 3 "route_short_name" " 2"
"routes.txt" 4 "route_short_name" " 3"
"routes.txt" 5 "route_short_name" " 4"
"routes.txt" 6 "route_short_name" " 5"
"routes.txt" 7 "route_short_name" " 6"
"routes.txt" 8 "route_short_name" " 7"
"routes.txt" 9 "route_short_name" " 8"
"routes.txt" 10 "route_short_name" " 9"
"routes.txt" 15 "route_short_name" " 0L"
"routes.txt" 16 "route_short_name" " 0P"
"routes.txt" 28 "route_short_name" "C "
"routes.txt" 111 "route_short_name" "116 "
"routes.txt" 112 "route_short_name" "128 "
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 13875

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 13875 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" "PL. GRUNWALDZKI" 5
"stops.txt" "stop_name" "DWORZEC NADODRZE" 19
"stops.txt" "stop_name" "MOKRY DWÓR" 24
"stops.txt" "stop_name" "DWORZEC NADODRZE" 39
"stops.txt" "stop_name" "PARK POŁUDNIOWY" 63
"stops.txt" "stop_name" "DW. ŚWIEBODZKI" 95
"stops.txt" "stop_name" "KAMIEŃSKIEGO (pętla)" 96
"stops.txt" "stop_name" "SIECHNICE - OSIEDLE" 114
"stops.txt" "stop_name" "DWORZEC AUTOBUSOWY" 120
"stops.txt" "stop_name" "KSIĘŻE MAŁE" 122
"stops.txt" "stop_name" "PL. JANA PAWŁA II" 142
"stops.txt" "stop_name" "PL. GRUNWALDZKI" 183
"stops.txt" "stop_name" "DWORZEC AUTOBUSOWY" 197
"stops.txt" "stop_name" "GALERIA DOMINIKAŃSKA" 225
"stops.txt" "stop_name" "PL. GRUNWALDZKI" 226
"stops.txt" "stop_name" "PL. GRUNWALDZKI" 238
"stops.txt" "stop_name" "PL. STASZICA" 270
"stops.txt" "stop_name" "LITEWSKA (pętla)" 278
"stops.txt" "stop_name" "OSIEDLE SOBIESKIEGO (pętla)" 282
"stops.txt" "stop_name" "DWORZEC GŁÓWNY" 285
"stops.txt" "stop_name" "SIECHNICE - TIM" 307
"stops.txt" "stop_name" "LIPA PIOTROWSKA" 314
"stops.txt" "stop_name" "PRACZE ODRZAŃSKIE" 339
"stops.txt" "stop_name" "PARK POŁUDNIOWY" 342
"stops.txt" "stop_name" "DWORZEC GŁÓWNY" 371
"stops.txt" "stop_name" "GALERIA DOMINIKAŃSKA" 389
"stops.txt" "stop_name" "PL. STASZICA" 392
"stops.txt" "stop_name" "PL. DANIŁOWSKIEGO" 394
"stops.txt" "stop_name" "CENTRUM HURTU UL. GIEŁDOWA" 412
"stops.txt" "stop_name" "LITOMSKA (ZUS)" 416
"stops.txt" "stop_name" "PL. GRUNWALDZKI" 421
"stops.txt" "stop_name" "JERZMANOWSKA (pętla)" 424
"stops.txt" "stop_name" "PL. DANIŁOWSKIEGO" 433
"stops.txt" "stop_name" "DWORZEC AUTOBUSOWY" 436
"stops.txt" "stop_name" "NOWY DWÓR (pętla)" 456
"stops.txt" "stop_name" "ŚLAZOWA (pętla)" 501
"stops.txt" "stop_name" "DWORZEC GŁÓWNY" 509
"stops.txt" "stop_name" "RACŁAWICKA (pętla)" 515
"stops.txt" "stop_name" "DWORZEC GŁÓWNY" 518
"stops.txt" "stop_name" "STARODWORSKA (ZUW)" 543
"stops.txt" "stop_name" "KIEŁCZOWSKA (LZN)" 544
"stops.txt" "stop_name" "PL. DANIŁOWSKIEGO" 559
"stops.txt" "stop_name" "GALERIA DOMINIKAŃSKA" 565
"stops.txt" "stop_name" "PL. STASZICA" 607
"stops.txt" "stop_name" "DWORZEC AUTOBUSOWY" 608
"stops.txt" "stop_name" "STĘPIN - pętla" 616
"stops.txt" "stop_name" "BIELANY WROCŁAWSKIE" 617
"stops.txt" "stop_name" "IWINY - pętla" 624
"stops.txt" "stop_name" "PL. JANA PAWŁA II" 659
"stops.txt" "stop_name" "DW. ŚWIEBODZKI" 662
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.
"20260123" "20170327" "20170424"
unknown_column INFO 6

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.
"routes.txt" "route_type2_id" 7
"routes.txt" "valid_from" 8
"routes.txt" "valid_until" 9
"trips.txt" "brigade_id" 6
"trips.txt" "vehicle_id" 7
"trips.txt" "variant_id" 8
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.
"control_stops.txt"
"route_types.txt"
"variants.txt"
"vehicle_types.txt"