You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Q7 was finalised during the telco of  



Prior revisions of answers

Proposal 3  

Short Summary Answer

OpenLR is well-documented through public resources that explain both the concept and technical implementation. For beginners and interested stakeholders, the official OpenLR website, Wikipedia, and GitHub repository offer clear and accessible entry points. More technical documentation and tools are also available for developers exploring real-world integration.

Stakeholder Relevance / Rationale

  • Public Authorities: Understand the concept and evaluate open standards for potential adoption.

  • Content Providers: Access technical specs and tools to enable consistent content delivery across platforms.

  • Service Providers: Get implementation examples and documentation for faster integration.

  • OEMs: Explore background material for evaluating compatibility with in-vehicle systems.

Detailed Explanation

Overview of OpenLR
OpenLR is a map-agnostic, compact method for describing road locations (like points or routes), which allows the same encoded data to be interpreted across different digital maps. Instead of relying on GPS coordinates or road names, it uses Location Reference Points (LRPs)—defined by coordinates, road class, direction, and more—to describe locations relative to road networks.

Where to Start

ResourceDescription
Wikipedia - OpenLRGeneral introduction and history of the method
Official OpenLR WebsiteConceptual overview, technical specs, white paper, and example use cases
OpenLR White Paper (PDF)Core specification; good summary in pages 3–5 for non-experts
TomTom OpenLR GitHubJava-based encoder/decoder tools, sample data, and usage examples
INRIX Docs on Dynamic Location ReferencingCovers OpenLR use in dynamic traffic applications

If You're New to OpenLR

  1. Start with the Wikipedia entry or the OpenLR website’s overview section.

  2. Read pages 3–5 of the white paper to understand the logic without needing deep technical background.

  3. Try a decoder tool from GitHub to experiment with real OpenLR data.

  4. Visualize results using OSM-based tools (e.g., JOSM) to confirm that decoded paths match expected roads.

Decision Guide

GoalRecommended Resource
Learn what OpenLR isWikipedia, OpenLR homepage
Understand how it worksOpenLR White Paper, Section 1–2
Try an implementationGitHub: TomTom-Tools/OpenLR
Get help with traffic-related useINRIX Dynamic Location Referencing Docs

Implementation Notes

  • All core OpenLR resources are freely accessible and open-source.

  • For implementation, use the GitHub repo which includes sample encoders, decoders, and test data.

  • The community is small but active—issues and Q&A can often be found via GitHub discussions.

References & Tools

Comments


Who

What

Decision

1


2


3


Proposal 1 

Proposal text  (MS Copilot generated)

ChatGPT generatedChatGPT Plus - OpenLR Guru

You can find detailed information about OpenLR from several reputable sources:

1. Wikipedia

The OpenLR Wikipedia page provides a comprehensive overview of the standard, its development, and its applications [1].

2. Official OpenLR Website

The OpenLR official website offers extensive information about the method, including documentation, implementation guides, and contact details for further inquiries [2].

3. INRIX Documentation

INRIX provides documentation on Dynamic Location Referencing, which includes details about OpenLR and its implementation tools [3].

These resources should give you a solid foundation to understand and implement OpenLR. 

References
[1] OpenLR - Wikipedia
[2] OpenLR
[3] Dynamic Location Referencing - INRIX documentation

🔎 What is OpenLR (in simple terms)?

OpenLR is a method to describe a road location (like a route or a point) in a compact, map-agnostic format, so it can be decoded across different map systems.

It's useful for:

  • Traffic alerts

  • Speed limit data

  • Road works

  • Any road-based data shared between different systems (e.g., TomTom → Google Maps)

🧱 Basic Idea

Instead of giving exact GPS points or road names (which may differ across maps), OpenLR uses:

  • A few location reference points (LRPs) (with coordinates, road type, direction)

  • Some extra info like length, bearing, and form of road

That’s enough to figure out the road path on any map that has similar roads.

📚 Where to Read More

✅ Official Specs & Docs

🛠 Tools to Try

  • OpenLR Test Encoder/Decoder Tool (Java) from GitHub
    → You can run this locally to test OpenLR references.

  • JOSM (OSM Editor) + GPS traces
    → You can visualize LRPs on a map for checking decoder results.

👶 Easy to Start

If you're new:

  1. Read page 3–5 of the OpenLR whitepaper – it gives a good summary.

  2. Try decoding an example reference using the GitHub tools.

  3. Visualize the results on OpenStreetMap to see if it matches.

Here are the best places to learn more about OpenLR, whether you're just starting or digging deeper into implementation:

📚 Official Resources

1. OpenLR Homepage

🔗 openlr.org

  • Overview of the method, benefits, and licensing

  • Links to the whitepaper, license, and errata

2. OpenLR Whitepaper

📄  File: openlr-whitepaper_v1.5.pdf

  • The full technical specification (latest is version 1.5 revision 2)

  • Explains encoding logic, location types, physical formats

📄 Also check the Errata for bug fixes and clarifications

3. GitHub Reference Implementation

🔗 github.com/tomtom-international/openlr

  • Open-source Java implementation by TomTom

  • Includes encoder, decoder, test examples, map interface

💬 Community and Q&A

🔍 Stack Overflow

Search: OpenLR

  • Community debugging tips, edge cases, format usage

🛠️ Other Practical Tools

  • JOSM (for OpenStreetMap): You can overlay decoded paths

  • QGIS or Leaflet.js: For rendering paths from decoded OpenLR

📨 Get In Touch

📧 Contact the OpenLR Association:
https://www.openlr.org/contact/
They respond to usage questions and membership inquiries.


Description of changes

<description of the changes>

Comments


Who

What

Decision

16/11 meetingStephanie to merge based on ChatGPT input structure
2


3



Input materials