[OSRM-talk] Elevation in OSRM result (for profile)

Elisabeth Leu elisabeth.leu at camptocamp.com
Fri Mar 7 07:55:28 UTC 2014


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 your own formula, it should be possible.
(Yves, Stéphane, Radu correct me if I'm wrong ;)

Kind regards,
Elisabeth





On Thu, Mar 6, 2014 at 4:56 PM, Michal Palenik <michal.palenik at freemap.sk>wrote:

> 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
>
> michal
> On Thu, Mar 06, 2014 at 03:06:52PM +0100, Elisabeth Leu wrote:
> > 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 in the next days / weeks, with the final
> > goal to suggest this feature as a pull request for reviewing.
> >
> > We are open to take opinions and remarks about it, esp. concering a
> future
> > pull request for OSRM master/develop.
> >
> > Best regards,
> > Radu, Yves, Stéphane and Elisabeth
> >
> >
> >
> > On Fri, Jan 31, 2014 at 8:49 AM, Yves Bolognini <
> > yves.bolognini at camptocamp.com<javascript:_e(%7B%7D,'cvml','
> yves.bolognini at camptocamp.com');>
> > > wrote:
> >
> > > Hi,
> > >
> > > Thanks for your answer. Actually yes, for now our need is simply to
> > > show elevation in the output.
> > >
> > > I thought of using the way.name attribute to pass node elevations.
> But:
> > > 1) Elevation is on nodes, not on ways. So we would need to implement
> > > some hack to pass both nodes' evelations on every way's name
> > > 2) I thought maybe the profile thing in OSRM output would be
> > > interesting for other devs, so it may be good to code it the clean way
> > >
> > > Anyone has an idea how hard it would be to add such a feature inside
> > > OSRM? Is someone interested in this addition?
> > >
> > > Best,
> > > Yves
> > >
> > >
> > > 2014-01-30 Florian Lohoff <f at zz.de<javascript:_e(%7B%7D,'cvml','
> f at zz.de');>
> > > >:
> > > >
> > > > Hi,
> > > >
> > > > On Thu, Jan 30, 2014 at 02:28:39PM +0100, Yves Bolognini wrote:
> > > >> Hello List,
> > > >>
> > > >> We have elevation data in our source graph. Each vertex has
> elevation
> > > >> information ("ele" key in OSM-like data). We'd like to have this
> info
> > > >> in OSRM result in order to display profile.
> > > >
> > > > My understanding would be that you need to put this into some tag
> OSRM
> > > > stores the hsrm file and shows it in the JSON e.g. name.
> > > >
> > > > I do something like the following:
> > > >
> > > >   if speed_profile[highway] ~= nil then
> > > >         way.speed=speed_profile[highway]
> > > >         way.name=table.concat({way.id,highway,way.name,way.ref},"|")
> > > >   end
> > > >
> > > > So i get way.id, highway type, name and ref ...
> > > >
> > > >> What are the chances that elevation data will be available one day
> in
> > > >> the output?
> > > >> What do you estimate regarding the complexity to implement it?
> > > >> Would a contribution for this feature be considered?
> > > >
> > > > From using elevation data i would expect to have elevation on nodes
> > > > and if adjacent nodes have different elevation, you would need to
> split
> > > > the way and make it 2 oneways with different costs.
> > > >
> > > > Uphill more expensive than downhill.
> > > >
> > > > Or is it just you'd like to show elevation data in the output?
> > > >
> > > > Flo
> > > > --
> > > > Florian Lohoff
> f at zz.de<javascript:_e(%7B%7D,'cvml','f at zz.de');>
> > > >
> > > > -----BEGIN PGP SIGNATURE-----
> > > > Version: GnuPG v1.4.10 (GNU/Linux)
> > > >
> > > > iQIVAwUBUup2BJDdQSDLCfIvAQgJgA//VTwAdXc41GeJediOMp+nTkr3ztmfQ1Lx
> > > > a1JETnmTbdrdUZsYqQZrGKpSDwCTAwOXx8Vu018dhIpNmSGhrH1Jn2qWTsazBmSQ
> > > > r6T0a/vk/Ow8NXkZTR2vy66XBO/F4ZClYxWZm0O3J5p/cGPRgNyDZWsaCACAGdLf
> > > > eJzv2UoCO9Mq27V2fzHwCEB1TBwQBy8a/heN1VJuIREkmWiLZTSIEpr8FkjjjWts
> > > > o66Yna48jYqEWW0DYqC9v3hPvQb7suvT508zetTJeONiYXcHENfaD3orsBLkWCH2
> > > > 8qjKo3BJ0qWin92y9J3Su0Vf8+MWb/TQ55a6OqEzqWu696UkYn7pmkk/lbpZVMY3
> > > > DB1Pd84S1/lGLUmPJbG9sm/ouCJbkresTKvHfvHkPVZB0CiOEg/zpZOCzzziul5r
> > > > 0iF2XloVGInhG6c6pbtn6lSpsnRe7ZfuOp9dbtWey5SXzmPqlt0D5J7/G/y8/Nqo
> > > > 5z5zTqczEKRnh1oPoa5D1t9TTyKFngAEMa7jwoAxUQEuRpFOUPuI8zGJzc7doRgi
> > > > GKrVGi6Dt42CFzlwvneKUrq0e+PqQvN8zMjJ0a4d3fPd9/a2zSyFCV7HtuoAgSXL
> > > > XzMDjGnjJBJIoWDfQoW3hdIwmRP6txbf/qWKk5scSDYvD6C2KTnw7mWvGcdB5CTg
> > > > cH6g7uCak70=
> > > > =JgTX
> > > > -----END PGP SIGNATURE-----
> > > >
> > >
> > > _______________________________________________
> > > OSRM-talk mailing list
> > > OSRM-talk at openstreetmap.org<javascript:_e(%7B%7D,'cvml','
> OSRM-talk at openstreetmap.org');>
> > > https://lists.openstreetmap.org/listinfo/osrm-talk
> > >
> >
> >
> >
> > --
> > Elisabeth Leu
> >
> > Camptocamp SA
> > PSE A
> > CH-1015 Lausanne
> > www.camptocamp.com
> >
> > Phone: +41 21 619 10 21
> >
> >
> > --
> > Elisabeth Leu
> >
> > Camptocamp SA
> > PSE A
> > CH-1015 Lausanne
> > www.camptocamp.com
> >
> > Phone: +41 21 619 10 21
>
> > _______________________________________________
> > OSRM-talk mailing list
> > OSRM-talk at openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/osrm-talk
>
>
> --
> michal palenik
> www.freemap.sk
> www.oma.sk
>



-- 
Elisabeth Leu

Camptocamp SA
PSE A
CH-1015 Lausanne
www.camptocamp.com

Phone: +41 21 619 10 21
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osrm-talk/attachments/20140307/cf2d9b90/attachment-0001.html>


More information about the OSRM-talk mailing list