Zarząd Transportu Miejskiego w Poznaniu

What changed since the last check

No category changes since the last check.

Top three things to fix

1. Re-export with a validity window that reaches at least 60 days out.

   Service data runs out in 8 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

   Effort: One export setting.

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   3109 of 3109 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

   Effort: A column in stops.txt; your scheduling software likely has it.

3. Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

   The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

   Effort: A small file for most flat-fare systems.

Ready to send to the agency

Hi Zarząd Transportu Miejskiego w Poznaniu team, Service data runs out in 8 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice. The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/ztm-poznan/

Copy this note from the full scorecard.

Key facts

Feed URL

https://www.ztm.poznan.pl/pl/dla-deweloperow/getGTFSFile

Last checked

2026-07-18

Service window

8 days of service data remain. Last service date 2026-07-26.

Location

Wielkopolskie, Poland