4.2 Route Entity Problems

Note

Route entity diagnostics are not implemented yet. The normalized route layer builds route families, itineraries, stop calls, and route-route matches, but the problem pipeline currently emits only stop-scoped Problem rows attached to stops_matched.id.

Route Entity problems identify inconsistencies at the Route object level. These problems concern the existence and global properties of a route, independent of its individual stops.

Key Question: "Does this route exist and is it defined correctly?"

4.2.1 Unmatched Route (Planned)

Definition: A route exists in one dataset but has no corresponding route in the other.

ATLAS-only: Route appears in GTFS but has no corresponding OSM route relation.
OSM-only: An OSM route relation exists but has no corresponding ATLAS route.

Priority Criteria:

Priority	Condition
P1	Routes with >20 stops
P2	Routes with 5-20 stops
P3	Routes with <5 stops

Example: GTFS shows "Bus 72" with 25 stops, but no OSM route relation exists. This is a global issue; the route is missing entirely.

4.2.2 Route Metadata Mismatch (Planned)

Definition: A route exists in both datasets (matched pair), but their global attributes conflict.

Detection Method:

Identify matched route families from line_family_matches (route-level linkage output).
Compare the currently implemented fields:
- ATLAS route_short_name against OSM ref / name
- GTFS route_type against the OSM route mode

Implementation Note:

No route_predicates package or route-level Problem persistence exists yet.
A future implementation could emit route_metadata_mismatch for mode mismatches and name/ref mismatches.
Broader metadata comparisons such as network / operator are also still future work.

Generating Report

Documentation

4.2 Route Entity Problems

4.2.1 Unmatched Route (Planned)

4.2.2 Route Metadata Mismatch (Planned)

Related Documentation