Despite it's a pretty old thread regarding feeding OSRM with postgis
geometries, I have new lights to bring up
2017-11-30 18:09 GMT+01:00 Daniel Hofmann <hofm...@mapbox.com>:
> OSRM is a routing engine for OpenStreetMap and the OpenStreetMap extracts
> usually come in xml or pbf formats.
I find this a bit restrictive and I wonder why it's valuable to stuck osrm
on osm data only.
I work for a company which is interested to use osrm as a router for public
works (not cycling nor car or whatever).
We have lot of private data we process into a postgresql db in which osm
data is also imported.
OSM XML file production at the end of our process generate a lot of
overhead as to feed osrm.
This doesn't bring advantage at all.
> We're using https://github.com/osmcode/libosmium in the osrm-extract
> binary; you theoretically _could_ switch it out with calls to your database
> but that will be a bigger lift I guess, and we don't want to add arbitrary
> data source drivers to OSRM.
We think about creating another connector which would enable osrm-extract
to get its data directly for pgsql.
Currently we're not aware of how deep the xml/libosmium is linked to
Our use cases enlarge the potential and relevance of osrm in
We look to be as constructive as possible and it will be a pleasure to
share since osrm is great tool.
All the best
OSRM-talk mailing list