GTFS Schedule Validation Report

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

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
unofficial ełk gtfs, generated from Pixel Ontime by lz
Feed Email:
N/A
Feed Language:
Polish
Feed Start Date:
2025-11-09
Feed End Date:
2025-12-30

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 16
  • Shapes: 109
  • Stops: 312
  • Trips: 1787

Specification Compliance report

35 notices reported (0 errors, 32 warnings, 3 infos)

Notice Code Severity Total
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 "20251223" "20251230" "20251230"
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 24

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.
2 "90" "11-go Listopada — kościół 01 (90)"
29 "159" "Buczki (159)"
30 "253" "Buczki (253)"
49 "98" "Chrzanowo II (98)"
50 "227" "Chrzanowo II (227)"
78 "275" "Grabnik (275)"
79 "262" "Grabnik (262)"
80 "263" "Grabnik — Sołectwo (263)"
81 "267" "Grabnik — Sołectwo (267)"
82 "266" "Grabnik II (266)"
83 "265" "Grabnik II (265)"
84 "264" "Grabnik Osada (264)"
85 "56b" "Grodzieńska Sikorskiego Rondo (56b)"
86 "43a" "Grodzieńska Sikorskiego ZS NR6 (43a)"
103 "56a" "Kajki ZS Nr 6 (56a)"
117 "225a" "Kolejowa (225a)"
120 "86a" "Kolejowa86 (86a)"
179 "130" "Ogródki — Pętla (130)"
210 "306-01" "Produkcyjna 01 (306-01)"
219 "190" "Rogale (190)"
263 "158" "Suwalska — Bojar (158)"
264 "252" "Suwalska — Bojar (252)"
287 "57a" "Wileńska Sikorskiego stadion (57a)"
288 "42a" "Wileńska Sikorskiego ZS nr2 (42a)"
unexpected_enum_value WARNING 6

unexpected_enum_value

An enum has an unexpected value.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row number of the faulty record. fieldName (?) The name of the field where the error occurred. fieldValue (?) Faulty value.
"fare_attributes.txt" 7 "transfers" 5
"fare_attributes.txt" 9 "transfers" 5
"fare_attributes.txt" 11 "transfers" 5
"fare_attributes.txt" 13 "transfers" 5
"fare_attributes.txt" 15 "transfers" 5
"fare_attributes.txt" 17 "transfers" 5
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