Pražská integrovaná doprava (PID)

What this grade measures

The quality of the schedule data this agency publishes for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Progress this period

No newly cleared items this period. The score and trend above reflect where the feed stands today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

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

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

   Estimated effort: One 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.

   Estimated 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.

   Estimated effort: Varies.