cdn-zbiorkom-live-pol — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-09T16:02:39Z,
for the dataset file:///shared/cdn-zbiorkom-live-pol_7c2e1f95.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:
2026-03-28
Feed End Date:
2026-04-11

Files included


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

Counts


  • Agencies: 5
  • Blocks: 0
  • Routes: 134
  • Shapes: 1169
  • Stops: 2464
  • Trips: 41965

Specification Compliance report

7792 notices reported (0 errors, 7781 warnings, 11 infos)

Notice Code Severity Total
expired_calendar WARNING 1

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"
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 "20260409" "20260411" "20260416"
leading_or_trailing_whitespaces WARNING 3

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" 46 "route_short_name" "116 "
"routes.txt" 58 "route_short_name" "128 "
"routes.txt" 77 "route_short_name" "151 "
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 7746

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 7746 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.
"agency.txt" "agency_name" "NOWAK TRANSPORT" 4
"agency.txt" "agency_name" "PT KŁOSOK" 5
"stops.txt" "stop_name" "JANÓWEK (WOŚ)" 17
"stops.txt" "stop_name" "KSIĘŻE MAŁE" 41
"stops.txt" "stop_name" "PL. JANA PAWŁA II" 71
"stops.txt" "stop_name" "KSIĘŻE MAŁE" 116
"stops.txt" "stop_name" "PL. JANA PAWŁA II" 141
"stops.txt" "stop_name" "PARK POŁUDNIOWY" 153
"stops.txt" "stop_name" "JANÓWEK (WOŚ)" 171
"stops.txt" "stop_name" "GALERIA DOMINIKAŃSKA" 233
"stops.txt" "stop_name" "DWORZEC AUTOBUSOWY" 332
"stops.txt" "stop_name" "DWORZEC AUTOBUSOWY" 333
"stops.txt" "stop_name" "GALERIA DOMINIKAŃSKA" 339
"stops.txt" "stop_name" "PRACZE ODRZAŃSKIE" 367
"stops.txt" "stop_name" "PRACZE ODRZAŃSKIE" 368
"stops.txt" "stop_name" "DWORZEC NADODRZE" 371
"stops.txt" "stop_name" "PL. GRUNWALDZKI" 388
"stops.txt" "stop_name" "PL. GRUNWALDZKI" 410
"stops.txt" "stop_name" "GALERIA DOMINIKAŃSKA" 441
"stops.txt" "stop_name" "PARK POŁUDNIOWY" 531
"stops.txt" "stop_name" "PL. JANA PAWŁA II" 536
"stops.txt" "stop_name" "PL. JANA PAWŁA II" 537
"stops.txt" "stop_name" "DWORZEC NADODRZE" 551
"stops.txt" "stop_name" "KSIĘŻE MAŁE" 553
"stops.txt" "stop_name" "PL. GRUNWALDZKI" 554
"stops.txt" "stop_name" "PL. GRUNWALDZKI" 555
"stops.txt" "stop_name" "GAJ - pętla" 573
"stops.txt" "stop_name" "GAJ - pętla" 598
"stops.txt" "stop_name" "MOKRY DWÓR" 657
"stops.txt" "stop_name" "GAŁÓW (pętla)" 671
"stops.txt" "stop_name" "DWORZEC AUTOBUSOWY" 672
"stops.txt" "stop_name" "PL. STASZICA" 689
"stops.txt" "stop_name" "DWORZEC GŁÓWNY" 710
"stops.txt" "stop_name" "PORT LOTNICZY" 774
"stops.txt" "stop_name" "PORT LOTNICZY" 775
"stops.txt" "stop_name" "BRZEZINA (pętla)" 789
"stops.txt" "stop_name" "PL. JANA PAWŁA II" 820
"stops.txt" "stop_name" "PL. GRUNWALDZKI" 930
"stops.txt" "stop_name" "PL. STASZICA" 936
"stops.txt" "stop_name" "DWORZEC GŁÓWNY" 959
"stops.txt" "stop_name" "DWORZEC AUTOBUSOWY" 1043
"stops.txt" "stop_name" "DWORZEC AUTOBUSOWY" 1044
"stops.txt" "stop_name" "GALERIA DOMINIKAŃSKA" 1051
"stops.txt" "stop_name" "GALERIA DOMINIKAŃSKA" 1052
"stops.txt" "stop_name" "IWINY - rondo" 1081
"stops.txt" "stop_name" "GALERIA DOMINIKAŃSKA" 1093
"stops.txt" "stop_name" "GALERIA DOMINIKAŃSKA" 1101
"stops.txt" "stop_name" "PL. JANA PAWŁA II" 1141
"stops.txt" "stop_name" "PL. JANA PAWŁA II" 1142
"stops.txt" "stop_name" "DWORZEC NADODRZE" 1162
stop_too_far_from_shape WARNING 27

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.
30771 "869890" "3_16397612" 858714 "5792" "Łużycka" [51.13836675628686,17.020185224365505] 349.72813752844127
23750 "869881" "3_16396387" 641652 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
23486 "869880" "3_16396311" 630710 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
35595 "870490" "3_16398548" 1004401 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
30979 "870030" "6_16407797" 867975 "5792" "Łużycka" [51.13836675628686,17.020185224365505] 349.72813752844127
30809 "870031" "3_16397610" 858633 "5792" "Łużycka" [51.13836675628686,17.020185224365505] 349.72813752844127
30997 "870032" "6_16407803" 868224 "5792" "Łużycka" [51.13836675628686,17.020185224365505] 349.72813752844127
1100 "870233" "3_16399311" 33734 "5792" "Łużycka" [51.13836675628686,17.020185224365505] 349.72813752844127
36713 "870824" "6_16409610" 1034010 "5792" "Łużycka" [51.13836675628686,17.020185224365505] 349.72813752844127
36715 "870825" "6_16409623" 1034164 "5792" "Łużycka" [51.13836675628686,17.020185224365505] 349.72813752844127
36677 "870537" "3_16398600" 1033711 "5792" "Łużycka" [51.13836675628686,17.020185224365505] 349.72813752844127
36068 "870526" "3_16398647" 1021529 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
23953 "869992" "6_16407116" 653032 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
23785 "869994" "3_16396399" 642218 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
23964 "869998" "6_16407867" 653434 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
23789 "869997" "3_16396385" 641554 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
23616 "869981" "6_16405907" 635558 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
23617 "869982" "6_16405915" 635831 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
23520 "869988" "3_16396309" 630631 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
23626 "870375" "6_16405903" 635396 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
23639 "870378" "6_16405921" 636076 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
23641 "870380" "6_16405975" 638064 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
36587 "870116" "6_16409554" 1029401 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
36575 "870105" "6_16409556" 1029490 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
36062 "870288" "3_16398807" 1021644 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
18020 "869939" "6_16404378" 493244 "5792" "Łużycka" [51.134210425043506,17.01596310226352] 230.69925458317886
1098 "869922" "3_16399328" 34148 "5792" "Łużycka" [51.13836675628686,17.020185224365505] 349.72813752844127
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.
"20260409" "20260330" "20260410"
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" 7
"trips.txt" "vehicle_id" 8
"trips.txt" "variant_id" 9
unknown_file INFO 5

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"contracts_ext.txt"
"control_stops.txt"
"route_types.txt"
"variants.txt"
"vehicle_types.txt"