GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-10-16

Zarząd Transportu Miejskiego w Poznaniu

Grade F · 41.8 / 100

Down 0.5 points since 2026-10-15 (F to F).

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.

What changed since the last check

  • Correctness no change
  • Freshness down 1.7
  • Rider experience no change

Top three things to fix

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

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

    This one is about the feed as a whole, so there is no share of it to count.

    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.

    3261 of 3261 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.

    Fixing this covers all 3,261 stops in the feed.

    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.

    This one is about the feed as a whole, so there is no share of it to count.

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

Riders and need behind these fixes

  • Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
  • The served-area need overlays cover the United States and Canada, so none of them applies to this feed.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Feed evidence
Service data runs out in 15 day(s).
Next action
Re-export with a validity window that reaches at least 60 days out.
Recheck
Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text

Ready to send to the agency

Hi Zarząd Transportu Miejskiego w Poznaniu team, Service data runs out in 15 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-10-16
Service window
15 days of service data remain. Last service date 2026-10-31.
Location
Wielkopolskie, Poland

Part of the Poland portfolio: see where this agency sits among the other feeds in that group before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.4, validator 8.0.1.