GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-10-16

Pražská integrovaná doprava (PID)

Grade F · 31.6 / 100

Unchanged since 2026-10-15.

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 no change
  • Rider experience no change

Top three things to fix

  1. Correct feed_end_date in feed_info.txt. Set it to 2026-12-12, the last day in your calendar, or to the last day your schedule is reliable.

    feed_info.txt says this feed ends on 2026-10-29. Your service calendar runs to 2026-12-12. The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on.

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

    Effort: One field in feed_info.txt, often an export setting.

  2. Re-generate shape distances in your export; flag to your vendor if it persists.

    Some trips have stop times whose distances along the route go backwards. Apps can show transit vehicles jumping backwards or mis-order stops.

    This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

    Effort: Usually an export-tool fix, not hand editing.

  3. Review the rule documentation for 'pathway_unreachable_location' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Pathway unreachable location (flagged by the MobilityData validator). See the linked rule for what this affects.

    This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

    Effort: Varies.

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
feed_info.txt says this feed ends on 2026-10-29. Your service calendar runs to 2026-12-12.
Next action
Correct feed_end_date in feed_info.txt. Set it to 2026-12-12, the last day in your calendar, or to the last day your schedule is reliable.
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 Pražská integrovaná doprava (PID) team, feed_info.txt says this feed ends on 2026-10-29. Your service calendar runs to 2026-12-12. The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on. The fix is usually one export setting: Correct feed_end_date in feed_info.txt. Set it to 2026-12-12, the last day in your calendar, or to the last day your schedule is reliable. 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/pid-prague/

Copy this note from the full scorecard.

Key facts

Feed URL
https://data.pid.cz/PID_GTFS.zip
Last checked
2026-10-16
Service window
13 days of service data remain. Last service date 2026-12-12.
Location
Praha, Hlavní město, Czechia

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