Page History
...
OpenLR is a map-agnostic, open-source location referencing method optimized for cross-platform data exchange. Its compact format and royalty-free licensing make it especially attractive for use cases involving real-time traffic information and embedded systems. While not suitable for all use cases—such as detailed geofencing or off-road locations—OpenLR OpenLR provides a robust and cost-effective solution for many ITS and mobility scenarios.
Why the need for map agnostic location referencing ?
text + visual examples with 2 maps
Stakeholder Relevance / Rationale
Public Authorities: Ensures interoperability across vendors of (open) data on National Access Points towards data consumers and platforms in traffic management and navigation systemsservices; cost-effective and aligns with open standards.
Content Providers: Facilitates scalable data aggregation across different maps; encoding efficiency supports dynamic updates.
Service Providers: Enables consistent service delivery in bandwidth-constrained or multi-map environments; open standards with royalty-free licensing avoids vendor lock-in.
OEMs: Well-suited for in-vehicle use due usedue to its compact format; supports navigation services and also dynamic updates for ADAS and connected services.
Detailed Explanation
Types / Versions / FormatsFormats
- see Q1 - Different versions/types of OpenLR: What are they each good/bad at? What should be used for a given situation.
Core Format: Line-based referencing, encoding road stretches and point locations in a compact binary format.
Strengths: Open source (Apache 2.0), vendor-neutral, efficient for mobile or embedded use.
Limitations: Not ideal for high-resolution shapes, off-road points, or complex areas (extensions like OpenLR+ may be needed)- .
Use Cases
Traffic Management Systems: Dynamic updates like congestion alerts can be reliably encoded.
Navigation and Routing: Works well in systems where map providers vary or change.
Cross-border Applications: Supports consistent interpretation regardless of underlying map data.
Connected Vehicles: Efficient data usage is ideal for bandwidth-sensitive environments.
...
Encoding/Decoding Logic: Requires correct implementation on both sender and receiver sides.
Resilience to Map Changes: Uses road topology rather than fixed coordinates, reducing errors when maps differ.
Open Tools: Available libraries and encoders/decoders simplify integration.
Decision Guide
| Need | OpenLR Fit |
|---|---|
| Cross-map compatibility | Excellent |
| Real-time traffic/event messaging | Excellent |
| Compact transmission format | Excellent |
| Royalty-free, open-source integration | Excellent |
| High-resolution polygons or zones |
| Use ISO TPEG2-OLR, TomTom format has limited support |
| Off-road or free-form location support |
| Use ISO TPEG2-OLR, TomTom format has limited support |
Implementation Notes
Use official encoders/decoders to ensure format compliance.
Ensure team familiarity with the topology-based referencing model.
For more complex POIs or areas, use ISO TPEG2-OLR, or evaluate extensions or hybrid approaches (e.g., OpenLR+).
References & Tools
...
