<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" id="owaParaStyle"></style>
</head>
<body fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hi Richard,
<div><br>
</div>
<div>Thank you for your guidance. Yes, I can see that a lot of effort is required to get the datasets working cleanly. We have been able to make some adjustments resulting in improvements which are in better keeping with the requirements of our customers. But
changing the rules and configuration can only take you so far. Errors in the data will always be problematic.</div>
<div><br>
</div>
<div>Thank you for your insight. We will bear this in mind as we move forward.</div>
<div><br>
</div>
<div>Kind regards</div>
<div>Andrew</div>
<div><br>
</div>
<div><br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF858631" style="direction: ltr;"><font face="Tahoma" size="2" color="#000000"><b>From:</b> Richard Fairhurst [richard@systemed.net]<br>
<b>Sent:</b> 08 June 2021 19:14<br>
<b>To:</b> osrm-talk@openstreetmap.org<br>
<b>Subject:</b> Re: [OSRM-talk] Routing across features with "issues"<br>
</font><br>
</div>
<div></div>
<div>
<div name="messageBodySection">
<div dir="auto">Andrew King wrote:
<div dir="auto">
<div dir="auto">> What is the best way to deal with issues such as this? I could obviously </div>
<div dir="auto">> fix the data for this one case, but there are probably thousands of </div>
<div dir="auto">> similar cases such as this.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Julien has explained the issue in this particular case ("dupe" nodes).</div>
<div dir="auto"><br>
</div>
<div dir="auto">As a more general word of warning:</div>
<div dir="auto"><br>
</div>
<div dir="auto">If you want good results from pedestrian (or bike) routing with OSM, no matter what router you use, you will have to put in a lot of work. It isn't an out-of-the-box solution. OSM path and access data is messy and inconsistent, particularly
across different countries. You will have to do a lot of data fixup and a fair amount of coding (in OSRM's case, in the Lua profiles) to get something good - my profiles and other pre-processing code for cycle.travel are well into the thousands of lines of
code.</div>
<div dir="auto"><br>
</div>
<div dir="auto">As an example of the sort of issues you can encounter:</div>
<div dir="auto"> <a href="https://www.openstreetmap.org/changeset/105985206" target="_blank" rel="noopener noreferrer">https://www.openstreetmap.org/changeset/105985206</a></div>
<div dir="auto"><br>
</div>
<div dir="auto">Here you can see an angry landowner who is finding people are being diverted across his land by routing apps. I'm pretty sure I know what's happening here - certain routing apps, perhaps in this case AllTrails and Komoot, are not very good at
understanding how tagging conventions differ between countries. And bear in mind that's with a staff of over 60 (Komoot) or $75m of VC (AllTrails).</div>
<div dir="auto"><br>
</div>
<div dir="auto">I don't want to put you off - pedestrian/bike routing with OSM, when done right, is much better than with any other dataset. And, of course, it's up to you to decide the return on satisfied routing customers vs hours invested in tuning the routing.
But if you want to get it right, it takes a lot of time.</div>
</div>
</div>
</div>
<div name="messageSignatureSection"><br>
<div class="matchFont">cheers</div>
<div class="matchFont" dir="auto">Richard</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>