Here20SM

Reference implementation of the TomTom OpenLR standard to map traffic information provided by the HERE Traffic API on an OSM road network. The implementation came about as part of my master’s thesis, involving the HTW Dresden faculty of Geoinformatics and the Fraunhofer IVI Dresden.

If you want to view the master's thesis, please contact the Fraunhofer IVI Dresden.

Table of Contents

1. General Info
2. Programms and accounts needed
3. Database setup
4. Build
5. Database tables
6. FAQs
7. Technologies
8. License

General Info

---

Reference implementation implemented in Java. Uses the TomTom OpenLR standard and the TPEG2-OLR ISO/TS 21219-22 standard to map traffic information on a road network based on OpenStreetMap data.

Project status: reference implementation

Incidents visualized in QGIS

Programms and accounts needed

---

• At least a HERE Developer Freemium plan with an API KEY for the usage of the HERE Traffic API.

Programms

• IDE of your choice, e.g. IntelliJ IDEA
• PostgreSQL database with PostGIS extension
• Database client, e.g. DBeaver, pgAdmin

If you'd like to visualize the affected lines:

• QGIS to visualize the data, however, is not absolutely necessary

If you want to set up a PostgreSQL database with OSM data:

• OSM2pgsql

Database setup

---

Check out HOWTO for instructions on setting up a routable PostgreSQL database based on OSM data.

Build

---

1. Clone project from GitHub
   • Instruction for IntelliJ
2. Change database informtion dbname, user and password in:
   • DatasourceConfig.java
   • pom.xml

<!-- JDBC connection parameters -->
<jdbc>
    <driver>org.postgresql.Driver</driver>
    <url>jdbc:postgresql://localhost/dbname</url>
    <user>username</user>
    <password>password</password>
</jdbc>

3. Set your HERE Api key

private String hereApikey = "yourApiKey";

4. To build the project

mvn clean install

5. Run the program. The requested bounding must be specified as WGS84 coordinates.

Databse tables

---

The database should contain the following tables before running the programm:

• form_of_way : physical characteristics of a street. For more informationn check TomTom OpenLR White Paper.
• functional_road_class: indicates the importance of the road in the network. For more informationn check TomTom OpenLR White Paper.
• • kanten: lines in the road network.
• • knoten: nodes in the road network.
• metadata: metainformation for the map, map owner, map name and bounding box information.

After running the programm the following tables should be added to the databse:

• affected : contains all lines affected by a incident
• incidents : Contains all incidents received from the Traffic API with their ID, type, status, start date, end date, criticaliy, OpenLR code, short description, detailed description, road closure, positive offset, negative offset and creation date. If a incident couldn't be mapped the offsets are set to -1, if the OpenLR code is not valid they are set to -100.
• kanten_incidents: key table

FAQs

---

1. Is there a database example? Yes, check out the HOWTO file.
2. Can you decode a TomTom OpenLR location? You can find the decoder to be used in the TomTomDecoder class.
3. How do you visualize the data in QGIS? Check this video.
4. Can I use a different spatial database? Yes, it is possible to use another spatial databse. But you need to implement your own map loader using the MapLoader Interface. In addition, changes in the pom.xml (database connection and Jooq dialect), the DatasourceConfig class and the ApiRequest class must be made.

Technologies

---

• TomTom OpenLR implementation: https://github.com/tomtom-international/openlr
• HERE Traffic API: https://developer.here.com/documentation/traffic/dev_guide/topics/incident-data.html
• PostgreSQL: https://www.postgresql.org
• PostGIS: https://postgis.net
• pgRouting: https://pgrouting.org
• jOOQ: https://www.jooq.org

License

---

Apache License, Version 2.0