Owner

evan-siroky

Description

Quality monitoring product for GTFS Realtime data (vehicle positions, trip updates, service alerts) across California transit agencies. Ensures the recording of a historically accurate representation of performed transit operations.

Warehouse layer: Quality (sits alongside data) Lifecycle stage: Operate

⚠ Note: The original spec contains several sections that appear to be copy-pasted from the GTFS Schedule Data Quality spec (references to “Schedule” where “Realtime” is expected). These have been noted. Realtime-specific SLA and contract details need independent definition.

Intake

(TBD: formal intake process not yet defined.)

Contract

GTFS Realtime Data Quality is critical towards ensuring the recording of a historically accurate representation of performed transit operations in California.

(TBD: The following commitments appear to be Schedule-specific copy. Realtime-specific commitments need to be defined independently.)

  • SOPs are maintained and up-to-date
  • SOP automation documentation is maintained and up-to-date

Consumers

Downstream products:

Dependencies

SLA

(TBD: The original spec lists the same weekly checks as Schedule Data Quality. This needs to be replaced with realtime-specific checks, such as:)

  • (TBD) Vehicle position feed completeness and latency
  • (TBD) Trip update accuracy against observed operations
  • (TBD) Service alert coverage and timeliness

Quality

(TBD: Realtime-specific quality tests not yet defined.)

Operations

(TBD: runbook, incident log, and alert routing not yet defined.)

Lifecycle

So long as detailed data about transit operations is desired, GTFS Realtime Data Quality checking will occur. Last reviewed: (TBD)