[OSRM-talk] Elevation in OSRM result (for profile)
Yves Bolognini
yves.bolognini at camptocamp.com
Fri Jan 31 07:49:43 UTC 2014
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>:
>
> 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
>
> -----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-----
>
More information about the OSRM-talk
mailing list