OpenLR™ - Frequently Asked Questions (FAQ)
This page provides answers to frequently asked questions about OpenLR™ in the categories: General, License, Testing, Contribution, and Usage. Questions regarding the software packages are answered in a separate FAQ section which can be found on the Maven generated package documentation (link opens in a new window).
General - Answers
are (other / new) application areas for OpenLR™
Other application areas for OpenLR™ might be:
- Exchange of data between traffic management centres
- Collecting static and dynamic map update data from road operators and governments such as speed limit information updates, planned road works, incidents
- Cooperative systems currently in research phase (vehicle to infrastructure systems) in which vehicles communicate with infrastructure, for example to create dynamic green waves
- eCall in which a Public Service Answering Point receives automatically a message of an accident, with information on the accident, car and driver
- Vehicle - to - vehicle communication for a variety of safety applications
License - Answers
are the conditions to use OpenLR™?
OpenLR™ is made available on the basis of 'copyleft' principle which allows programmers to contribute to improvements and maintenance of the "open standard". The utilized open source license Apache version 2 permits the use of the library in proprietary programs. The white paper describing the technique behind OpenLR™ is available under a Creative Commons license. The source code is published "as is": no warranty is given by any of the initiators or contributors to the initiative to any user of the code. The license to partners asserting patents is withdrawn as the license is subject to a non-assertion clause.
- Has OpenLR™ been tested (on large scale) in any applications? Are there any quality values available?
- Is there any map data available for testing?
Testing - Answers
OpenLR™ been tested (on large scale) in any applications? Are
there any quality values available?
The TomTom implementation was tested with encoding and decoding in a TomTom environment with different maps from different versions and different vendors. The tests used line locations being covered by TMC and also on non-TMC roads. The test results cover the accuracy of the OpenLR™ method and the code size: success rates for randomly selected location and with maps from same vendor are above 98% with more than 50% error detection rates and above 96% for cross map vendor with error detection rates also above 50%. TMC road stretches show a higher success rate. The average size is 16-20 Bytes per location.
there any map data available for testing?
TomTom provides map data for testing under a test license agreement. For further details please go to the test data section.
Contribution - Answers
can I contribute?
We really appreciate your intention to contribute to OpenLR™ and you can discuss your ideas with us or report any kind of issues by writing an email to firstname.lastname@example.org.
can I report issues?
Please report issues to email@example.com.
- Can the encoder and decoder be used on whatever map?
- Can it work on Google Maps, OpenStreetMap and other?
- You are using FRC map attribute for encoding. Does OpenLR™ works against different map vendor releases where the FRC types differ?
- What is the development time required to implement OpenLR™?
Usage - Answers
the encoder and decoder be used on whatever map?
OpenLR™ is a map-agnostic location referencing method, which means that encoder and decoder, respectively, can operate on map databases with different versions or from different vendors.
it work on Google Maps, OpenStreetMap and other?
A map from one of the major brands used for navigation (navigable map) should be sufficient. OpenLR™ does not favour any particular map brand. As an encoding and decoding method it is technically not biased.
are using FRC map attribute for encoding. Does OpenLR™ works
against different map vendor releases where the FRC types differ?
OpenLR™ uses an own mapping table scheme for FRC (Functional Road Class) which allows an own mapping table of FRCs to cover differences when maps are used from different vendors.
is the development time required to implement OpenLR™?
The cost of using OpenLR™ consist of the own development and testing to identify if the technology meets the requirements of the application only. There is no cost involved for licenses to use the technology.