Harm Delva1, Julián Andrés Rojas Meléndez1, Ben Abelshausen2, Pieter Colpaert1 and Ruben Verborgh1
1 IDLab, Ghent University – imec
2 Open Knowledge Belgium
If most route planners preprocess the same data
Does it make sense to share the results?
We think that the concept of Linked Data is fundamental to the publishing of spatial data on the Web: it is the links that connect data together that are the foundational to the Web of data.
W3C and OGC, Spatial Data on the Web Best Practices
Slow but sure
We need to reduce the data requirements
See also:
The ethics of performance
Source: Configuring OpenTripPlanner
Only retain data that's needed to traverse a tile
576 km²
Zoom level 11 $\rightarrow$ Zoom level 10
6.1 MB uncompressed $\rightarrow$ 3.7 MB uncompressed
576 km²
Zoom level 10
3.7 MB uncompressed $\rightarrow$ 2.0 MB uncompressed
Brussels Airport - Bruges
100 km through relatively dense urban areas
Query Time | Data Downloaded | |
---|---|---|
Raw Data | 3,393 s | 214,672 kB |
Preprocessed Data | 20 s | 9,116 kB |
What's stopping us?
Cost?
Trust?
Serverless route planning seems feasible
We should share more data
hdelva.be/slides/sotm2019/
github.com/hdelva/preprocess_routable_tiles