Versions Compared

Old Version 49

changes.mady.by.user Teun Hendriks

Saved on

compared with

New Version Current

changes.mady.by.user Teun Hendriks

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Requirement /considerationTMCOpenLRNotes
Cross-map compatibilityLimitedExcellent

TMC location referencing requires pre‑use agreement between parties and explicit processing to insert location codes into digital maps.
OpenLR does not require prior agreement on location codes, and can be decoded against different map databases, making it source and target maps meet "navigable map" standards. This makes OpenLR significantly better suited for heterogeneous, multi‑map ecosystems.

CoverageFixed, limitedUnlimitedOpenLR does not rely on predefined location tables; any location that exists in a digital map can be encoded and transmitted.
TMC location tables are limited in size (typically around 60,000 locations per table).
In Europe, countries typically maintain a single national table, while larger markets such as the USA and China deploy multiple tables (often on the order of 30).
Real-time dynamic updatesModerateExcellent

With TMC, locations must be pre‑identified, agreed, and entered into both location tables and digital maps before they can be referenced, limiting responsiveness. 
OpenLR allows previously unidentified or newly relevant locations to be referenced immediately, for example when an unexpected incident occurs or temporary traffic management is introduced..

Decoder workloadLowHigher

TMC decoding is computationally efficient, as it relies primarily on table look‑ups.
OpenLR decoding requires on‑the‑fly map matching and routing, which increases processing demand on the receiving device.
Notwithstanding the higher workload, millions of in‑vehicle and backend systems use OpenLR decoding for traffic updates without practical issues.

InteroperabilityTable-dependentMap-agnosticTMC interoperability depends on consistent implementation of the same location tables across all parties, which complicates cross‑vendor, or multi‑provider deployments. 
OpenLR enables interoperability without shared tables, facilitating data exchange across different maps, map suppliers, service providers, and system architectures.
However, interoperability still depends on consistent encoder–decoder behavior and alignment on OpenLR formats.
Legacy embedded systemsStrongRequires migration

TMC is in very widespread use in the intelligent transportation ecosystem, with long-life expectations for e.g. in-vehicle traffic information and navigation systems.
Transitional strategies such as dual TMC/OpenLR support and phased migration are recommended to ensure service continuity while gradually increasing the scale of OpenLR adoption across a user base.

...

...