i've added a feature request
https://github.com/Project-OSRM/osrm-backend/issues/2519
the unpacking of edges phase should allow for impedance vs. speed debate
to move, also allowing for elevation to be stored in osrm.
i've tried to say this in my last comment at
Michal,
Strangely enough, we don't actually have the geometry. We find a path across
the Contraction Heirachy
routing graph, this may only have a small handful of edges. We can sum these
edges to get the route
duration, but to get the actual geometry or distance, we then have to
that is what I already do, but it means a lot of (unnecessary)
connections. I assume the geometries are already available when
computing the duration.
I was hoping for a "documentation lacking behind development"
scenario...
cheers,
michal
On Fri, Apr 15, 2016 at 04:09:49PM +0200, Daniel
If you check the v5 spec you linked, you will see only Route, Trip and
Match providing a "geometries" option.
What you can do is this:
- do a Table request from your position against all Bus / Tram stops in the
area / in a buffer of a few kilometers
- pick n shortest routes from the Table
hi,
within the new api, I am trying to find how to get geometry (together
with perfect duration). is it possible?
or do I have to make N*M queries for all the possible combinations?
https://github.com/Project-OSRM/osrm-backend/wiki/New-Server-api#service-table
I am trying to make a service
