Florian Lohoff
OpenStreetmap RouteQA refresh
2013 i started a project to monitor routing in parts of Germany. I recalculated
~200K routes every 30 to 60 Minutes and watched them over time whether they changed
due to OpenStreetmap data changes. It was a very clunky UI and nobody really understood
it, and its notifications. So for 13 years i mostly fixed routing issues coming up
in that tool by myself. I covered the higher class road network
2013 i started a project to monitor routing in parts of Germany. I recalculated
~200K routes every 30 to 60 Minutes and watched them over time whether they changed
due to OpenStreetmap data changes. It was a very clunky UI and nobody really understood
it, and its notifications. So for 13 years i mostly fixed routing issues coming up
in that tool by myself. I covered the higher class road network from tertiary
to motorway in a part of Northrhine-Westfalia.
The last couple of days/weeks i reimplemented everything. A new engine to
calculate the routes based on C++, OSRM and Postgres/Postgis and Tilemaker and a Webinterface
based on Mojolicious, Maplibre, Leaflet. And here we are - RouteQA2.
As i gained a lot of speed i am now easily running on whole of Germany. Most of
the time is spent on bringing the Germany.pbf up to date. The calculation of the 1.25 Million
routes takes only 128 Seconds. So we are happily running on a 30 Minute cycle.
I have 58K nodes in Germany split in 4510 Clusters. Routes are calculated any2any within
each cluster. Whenever time, distance or geometry changes a notification for that cluster
is being sent that something changed.
Changes are being matched on changeset bounding boxes, so one can actually see
where the changesets were in relation to the changed route geometries.
Mappers may then analyze whether change was legitimate change, an accidental breakage, or a
fix for some issue. Processes like opening notes to track construction. Remove forgotten
tags or quickly fix leftovers are now possible within 30 minutes.
Its not a static analysis tool for OpenStreetmap data. It does not make any sense out
of the current data, or tries to tell whether the current state is right or wrong.
It shows you how the Routing adapts to changes to OpenStreetmap data and gives mappers
the opportunity to quickly inspect possible errors.
Mappers can log in and tag notifications with typical issues, comment on notifications if
there are additional findings, and create their very own RSS/Atom feed for notifications.
Some stats for a typical run:
Stats: 4510 clusters, 58755 nodes, 1259544 routes calculated (15 without route)
Stats: OSRM returned 2218420 routes (26309 equivalent alternatives), 244 geometry checks
Stats: 0 new, 1259483 unchanged, 61 changed, 6 notifications
Stats: runtime 274.9 s (routing 128.9 s)
All routes are then brought together to show the grid of the network which was used
the last time all routes were calculated. This helps to get a glimpse on what the monitored
network is. With a trained eye one can also spot issues here e.g. roads which are completely
unused etc.
So have a look: https://osm.zz.de/routeqa2
So here some Screenshots:
2013 i started a project to monitor routing in parts of Germany. I recalculated ~200K routes every 30 to 60 Minutes and watched them over time whether they changed due to OpenStreetmap data changes. It was a very clunky UI and nobody really understood it, and its notifications. So for 13 years i mostly fixed routing issues coming up in that tool by myself. I covered the higher class road network
2013 i started a project to monitor routing in parts of Germany. I recalculated
~200K routes every 30 to 60 Minutes and watched them over time whether they changed
due to OpenStreetmap data changes. It was a very clunky UI and nobody really understood
it, and its notifications. So for 13 years i mostly fixed routing issues coming up
in that tool by myself. I covered the higher class road network from tertiary
to motorway in a part of Northrhine-Westfalia.
The last couple of days/weeks i reimplemented everything. A new engine to calculate the routes based on C++, OSRM and Postgres/Postgis and Tilemaker and a Webinterface based on Mojolicious, Maplibre, Leaflet. And here we are - RouteQA2.
As i gained a lot of speed i am now easily running on whole of Germany. Most of the time is spent on bringing the Germany.pbf up to date. The calculation of the 1.25 Million routes takes only 128 Seconds. So we are happily running on a 30 Minute cycle.
I have 58K nodes in Germany split in 4510 Clusters. Routes are calculated any2any within each cluster. Whenever time, distance or geometry changes a notification for that cluster is being sent that something changed.
Changes are being matched on changeset bounding boxes, so one can actually see where the changesets were in relation to the changed route geometries.
Mappers may then analyze whether change was legitimate change, an accidental breakage, or a fix for some issue. Processes like opening notes to track construction. Remove forgotten tags or quickly fix leftovers are now possible within 30 minutes.
Its not a static analysis tool for OpenStreetmap data. It does not make any sense out of the current data, or tries to tell whether the current state is right or wrong. It shows you how the Routing adapts to changes to OpenStreetmap data and gives mappers the opportunity to quickly inspect possible errors.
Mappers can log in and tag notifications with typical issues, comment on notifications if there are additional findings, and create their very own RSS/Atom feed for notifications.
Some stats for a typical run:
Stats: 4510 clusters, 58755 nodes, 1259544 routes calculated (15 without route)
Stats: OSRM returned 2218420 routes (26309 equivalent alternatives), 244 geometry checks
Stats: 0 new, 1259483 unchanged, 61 changed, 6 notifications
Stats: runtime 274.9 s (routing 128.9 s)
All routes are then brought together to show the grid of the network which was used the last time all routes were calculated. This helps to get a glimpse on what the monitored network is. With a trained eye one can also spot issues here e.g. roads which are completely unused etc.
So have a look: https://osm.zz.de/routeqa2
So here some Screenshots:
OpenStreetMap Blogs







