Versions Compared

Key

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

...

OpenLR works fundamentally differently. Instead of static identifiers, it generates dynamic location references derived from the actual geometry, topology, and attributes of the road network. Encoding a location therefore requires access to a routable digital map, as the encoder must understand how road segments connect, how paths are formed, and where decision points such as junctions and merges occur. While OpenLR is map‑agnostic in the sense that it is not tied to a specific vendor or map version, it nevertheless requires access to a suitable routable road network at encoding time. OpenLR requires source and destination target maps to meet "navigable map" standards.

...

Workflow Step

TMC (Traffic Message Channel)

OpenLR (Dynamic Location Referencing)

Key Differences / Notes

1. Location Model

Pre-coded locations stored in a Location Table with static IDsDynamic encoding based on geometry, topology, and attributesOpenLR does not rely on static tables; supports unlimited locations.

2. Map Dependency

Relatively dependent on the specific map version/revision used to build and link the TMC table codes to the road network map elementsMap‑agnostic and designed to work across multiple maps and versions

As road networks evolve, older TMC location tables may become outdated. 
OpenLR tolerates map differences, but maps should meet "navigable map" standards. Reliable decoding depends on both geometric alignment and similarity in road attribution (e.g., FRC/FoW). With OpenLR, overcoming a larger difference between source and target map versions needs careful matching to ensure correct location referencing. Larger discrepancies can reduce the decoding success rate. 

3. Location Identification

Lookup of a pre-defined TMC Location Code based on table or attributed map elements.On‑the‑fly encoding of point/line based on actual map geometryTMC is instant lookup; OpenLR requires computation.

4. Encoding Process

Encoding = selecting the right TMC Location Codes from the tableEncoding = generating a reference path via attributes + geometryOpenLR encoding is computationally heavier but flexible.

5. Message Construction

Very compact messages (a few bytes)Larger messages (~20–30 bytes for a line location)Size is rarely an issue today, but OpenLR uses more bandwidth.

6. Transmission

Typically  used in broadcast (RDS, DAB), and low‑bandwidth IP environments

Typically used in wider bandwidth IP-based environments.
TPEG enables hybrid TMC and OpenLR use in digital Broadcast transmission and IP environments.

OpenLR is suitable for richer digital ecosystems.

7. Decoding Method

Match Location Codes to same TMC table on receiver side, and look up associated map elements in map.Decoder reconstructs location using map matching + shortest-path algorithmsOpenLR decoding is more CPU-intensive compared to TMC decoding.

...