<div style="display: flex; flex-wrap: wrap; white-space: pre-wrap; align-items: center; "><img height="20" width="20" style="border-radius:50%; margin-right: 4px;" decoding="async" src="https://avatars.githubusercontent.com/u/1231218?s=20&v=4" /><strong>1ec5</strong> created an issue <a href="https://github.com/openstreetmap/openstreetmap-website/issues/6387">(openstreetmap/openstreetmap-website#6387)</a></div>
<p dir="auto"><a href="https://graphhopper.com/maps/" rel="nofollow">GraphHopper</a>, <a href="https://map.project-osrm.org/" rel="nofollow">OSRM</a>, and <a href="https://valhalla.openstreetmap.de/" rel="nofollow">Valhalla</a> all have their own first-party demo page that exposes more options and details than the <a href="https://github.com/perliedman/leaflet-routing-machine/">Leaflet Routing Machine</a> plugin we’re using, such as via points (A to B to C), turn lanes, elevation profiles, time-sensitive routing, truck routing, and isochrones. Some of these features would be useful to mappers using the OSM website, but others are mainly useful to end users. The end user experience for directions is much more open-ended. We could address their needs by linking out to the selected routing engine’s demo page, adding any supported parameters that can get the page to show something equivalent to the current directions. Then it’s up to the routing engine projects whether they want to facilitate the end user experience to that degree. For example, the GraphHopper and OSRM demo pages both have a convenient button to <a href="https://community.openstreetmap.org/t/suggestion-add-download-route-as-gpx-to-osm-org/129580" rel="nofollow">export GPX</a> (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="2535832941" data-permission-text="Title is private" data-url="https://github.com/openstreetmap/openstreetmap-website/issues/5224" data-hovercard-type="issue" data-hovercard-url="/openstreetmap/openstreetmap-website/issues/5224/hovercard" href="https://github.com/openstreetmap/openstreetmap-website/issues/5224">#5224</a>), so there’s less need for us to reimplement that functionality ourselves.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/issues/6387">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAK2OLLEDMZJQCGCOF7U5X33RW4ZXAVCNFSM6AAAAACF6FG752VHI2DSMVQWIX3LMV43ASLTON2WKOZTGM4TKMBVGU3DQOI">unsubscribe</a>.<br />You are receiving this because you are subscribed to this thread.<img src="https://github.com/notifications/beacon/AAK2OLIGJ3PCEGSK5O6LECD3RW4ZXA5CNFSM6AAAAACF6FG752WGG33NNVSW45C7OR4XAZNFJFZXG5LFVJRW63LNMVXHIX3JMTHMUXDQJE.gif" height="1" width="1" alt="" /><span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message ID: <span><openstreetmap/openstreetmap-website/issues/6387</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>

<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/issues/6387",
"url": "https://github.com/openstreetmap/openstreetmap-website/issues/6387",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>