GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-23T07:14:26Z,
for the dataset file:///shared/opole.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • MZK Sp. z o.o. Opole

Feed Info

Publisher Name:
unofficial opole gtfs, generated from Pixel Ontime by lz
Feed Email:
N/A
Feed Language:
Polish
Feed Start Date:
2025-12-03
Feed End Date:
2025-12-31

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 27
  • Shapes: 278
  • Stops: 529
  • Trips: 7243

Specification Compliance report

14 notices reported (0 errors, 11 warnings, 3 infos)

Notice Code Severity Total
feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

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 "20251223" "20251231" "20260122"
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
stop_without_stop_time WARNING 9

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
68 "963" "Dobrzeń Wielki - Dworcowa Parking (963)"
69 "964" "Dobrzeń Wielki - Dworcowa Parking (964)"
70 "961" "Dobrzeń Wielki - Kościelna 3 (961)"
71 "962" "Dobrzeń Wielki - Kościelna 3 (962)"
195 "192" "Marka z Jemielnicy - Torowa (192)"
377 "316" "Pużaka - Oleska (316)"
487 "902" "Wrocławska - Cmentarz (902)"
488 "903" "Wrocławska - Cmentarz (903)"
523 "822" "Wspólna - Zbożowa - Pętla (822)"
unknown_column INFO 3

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.
"trips.txt" "brigade" 6
"feed_info.txt" "feed_timezone" 3
"feed_info.txt" "spv2" 6