Hi François,
Ah. Well, the step of deduplicating and finding connected nodes will not
go away - OSRM requires a *graph*, not disconnected geometry, so you won't
be able to get away from the problem of turning your LineStrings into
connected data.
OSM's data structure (ways & nodes) has this
Hi Daniel,
2018-03-02 18:31 GMT+01:00 Daniel Patterson :
> Well, it *could* be done. It would all boil down to providing an
> alternative for `ParseOSMData` here:
> That function is responsible for parsing the OSM file, and
> copying/converting the OSM fields into a memory
Hi François,
Well, it *could* be done. It would all boil down to providing an
alternative for `ParseOSMData` here:
https://github.com/Project-OSRM/osrm-backend/blob/master/src/extractor/extractor.cpp#L211
That function is responsible for parsing the OSM file, and
copying/converting the OSM
Hi Daniel,
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 :
> OSRM is a routing engine for OpenStreetMap and the OpenStreetMap extracts
> usually come in xml or pbf
OSRM is a routing engine for OpenStreetMap and the OpenStreetMap extracts
usually come in xml or pbf formats.
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,
Yes, if all your data comes from a database the best way to get it into
OSRM is to map your data to the OpenStreetMap tagging schema.
You can either create an .osm.xml or even an .osm.pbf if you need the
compression and compactness; you can use e.g. libosmium to write both
formats.
Good luck,
Hi all,
I was recently asked to feed OSRM with other data than OSM files which are
stored in a PgSQL db.
Is this even possible ?
The data we want to process doesn't come from OSM db, should we produce an
osm xml file with those data prior to use osrm-extract ?
I know OSRM can query a postgis DB