Hi Elisabeth,
Great that you will want to help improve OSRM!
Do you mean that you will not touch the routing algorith, and just provide an
elevation profile of the route? Or do you also want to change the routing
algorith so it factors in elevation, ie avoid hills?
Kind regards,
Emil Tin
On
Elisabeth Leu elisabeth@camptocamp.com writes:
Hi Michal,
The way we will use OSRM, we'll compute speed independently of OSRM a
posteriori, using the height output.
been there done that
though not node based because imho this isn't good enough
see also the relevant tickets
Hi Emil
On Fri, Mar 7, 2014 at 9:26 AM, Emil Tin e...@tin.dk wrote:
Hi Elisabeth,
Great that you will want to help improve OSRM!
Actually you have to thank Radu ;)
Do you mean that you will not touch the routing algorith, and just provide
an elevation profile of the route? Or do you
Hi List,
This e-mail just to let you know that we decided to work on integrating the
elevation output in OSRM.
The goal is to have elevation in the geometry of the output JSON as well as
in the GPX, and an option in OSRM to enable elevation (disabled by default).
We might ask questions about it
hello all
I did not see it in your text, but use of elevation during calculation
of the route would increase possibilities for (at least) bicycle
routing. mainly change forward and backward speed according to meters
gained/descended (or changing impedance).
is this also one of the goals?
thanks
Hi Michal,
The way we will use OSRM, we'll compute speed independently of OSRM a
posteriori, using the height output.
So we won't adapt anything regarding the bike speed (I suppose for that, it
should be agreed upon a formula before...), but if you want to compute it
e.g. on the client side with
