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