4.2 Route Entity Problems
Warning
Route Entity problems are not yet implemented. This document defines the conceptual framework for future implementation.
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
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
Definition: A route exists in both datasets (matched pair), but their global attributes conflict.
Detection Method:
- Identify matched routes from
routes_matched(route-level linkage output). - Compare attributes:
name/short_name/long_namenetwork/operatorroute_type(e.g., Bus vs Tram)
Implementation Note:
- This problem class is intended to run after route import, using route-level metadata snapshots from both sides.