[pgrouting-dev] [OSRM-talk] Making progress on dumping pgRouting tables to OSRM

[Daniel Kastl]

>
> 4. write stored procedures like:
>    point = osrm_locate(point)
>    point = osrm_nearest(point)
>
>    jsontext = osrm_viaroute(point[], alt, instruction, zoom)
>    status = osrm_getRouteStatus(jsontext);
>    polyline = osrm_getRouteGeometry(jsontext, alt)
>    instructions[] = osrm_getRouteInstructions(jsontext, alt)
>
>    distancematrix[][] = osrm_dmatrix(points[])
>    distancerow[] = osrm_one2many(point, points[]
>
> To support this, it would be great if Dennis had time to add two methods
> to osrm-routed like:
>
> http://server:5000/dmatrix?lat=<lat>&lon=<lon>&...
> http://server:5000/one2many?slat=<start_lat>&slon=<start_
> lon>&lat=<lat>&lon=<lon>&...
>
>
Hi Steve, Dennis and Emil,

To be able to use the route for further processing, it would be also nice,
if OSRM would return a list of original network link ID's instead of a more
or less simplified route geometry and a few via points.

This is not an issue for distance matrices, where you only need to total
distance or cost, but too much generalized routes was the reason, why I
couldn't make use of OSRM once. And especially if the OSRM routing result
could be later used again in PostgreSQL/PostGIS, having the original road
network ID's would be very helpful.

So far I couldn't find anything else than this JSON output format:
https://github.com/DennisOSRM/Project-OSRM/wiki/Output-json

Daniel










-- 
Georepublic UG & Georepublic Japan
eMail: daniel.kastl at georepublic.de
Web: http://georepublic.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pgrouting-dev/attachments/20131114/1c4b7193/attachment.html>