<div dir="ltr"><div><div><div>Hi Daniel,<br><br></div>For me, sending an id as name attribute sounds like the best solution.<br></div>I understand that osrm doesn't explicitly need osm (or third party) tags, but it's pretty difficult to display comprehensive information to users or ownstream services without them.<br><br></div>Would it introduce unbearable load to make tags forwarded in response of a further osrm version?<br><br><div class="gmail_extra">François<br><br><div class="gmail_quote">2018-01-22 17:57 GMT+01:00 Daniel Patterson <span dir="ltr"><<a href="mailto:daniel@mapbox.com" target="_blank">daniel@mapbox.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span style="color:rgb(136,136,136);font-size:12.8px">Hi François,</span><div><span style="color:rgb(136,136,136);font-size:12.8px"><br></span></div><div><span style="color:rgb(136,136,136);font-size:12.8px"> By default, no - OSRM doesn't save any data that it doesn't explicitly need. There are two main approaches for getting extra OSM metadata along your route:</span></div><div><span style="color:rgb(136,136,136);font-size:12.8px"><br></span></div><div><span style="color:rgb(136,136,136);font-size:12.8px"> 1) Use something like </span><font color="#888888"><span style="font-size:12.8px"><a href="https://github.com/mapbox/route-annotator" target="_blank">https://github.com/<wbr>mapbox/route-annotator</a> to get the tag information *after* the route is found.</span></font></div><div><font color="#888888"><span style="font-size:12.8px"><br></span></font></div><div><font color="#888888"><span style="font-size:12.8px"> 2) Modify the `car.lua` script to encode the tags you want inside the `name` field. Be aware that this can affect the generation of route steps, and not all steps may be returned due to obvious turn detection and step collapsing.</span></font></div><div><font color="#888888"><span style="font-size:12.8px"><br></span></font></div><div><font color="#888888"><span style="font-size:12.8px">In general, (1) is probably the most robust approach, but you'll need a second server, and you'll have to write the code to do the extra lookup.</span></font></div><div><font color="#888888"><span style="font-size:12.8px"><br></span></font></div><div><font color="#888888"><span style="font-size:12.8px">daniel</span></font></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Mon, Jan 22, 2018 at 8:29 AM, François Lacombe <span dir="ltr"><<a href="mailto:fl.infosreseaux@gmail.com" target="_blank">fl.infosreseaux@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div><div>Hi everyone,<br><br></div>i'm looking for the best strategy to get extra attributes of route legs OSRM sends me in route service response.<br><br></div>My goal is to know which type of path I should follow, e.g highway=primary, highwy=secondary, man_made=pipeline or whatever.<br><div><div>Can I get in response every tags osm ways have in osm xml file processed by osrm-extract ?<br><br></div><div>Documentation gives examples with only name forwarded, but no extra tags.<br></div><div>Is this possible to get any id as to check against third party db?<br></div><div><br></div><div>Thank you for any answer, all the best<span class="m_-9022901813733457185HOEnZb"><font color="#888888"><br><br></font></span></div><span class="m_-9022901813733457185HOEnZb"><font color="#888888"><div>François</div></font></span></div></div>
<br></div></div>______________________________<wbr>_________________<br>
OSRM-talk mailing list<br>
<a href="mailto:OSRM-talk@openstreetmap.org" target="_blank">OSRM-talk@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/osrm-talk" rel="noreferrer" target="_blank">https://lists.openstreetmap.or<wbr>g/listinfo/osrm-talk</a><br>
<br></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
OSRM-talk mailing list<br>
<a href="mailto:OSRM-talk@openstreetmap.org">OSRM-talk@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/osrm-talk" rel="noreferrer" target="_blank">https://lists.openstreetmap.<wbr>org/listinfo/osrm-talk</a><br>
<br></blockquote></div><br></div></div>