en.osm.town is one of the many independent Mastodon servers you can use to participate in the fediverse.
An independent, community of OpenStreetMap people on the Fediverse/Mastodon. Funding graciously provided by the OpenStreetMap Foundation.

Server stats:

268
active users

#graphhopper

0 posts0 participants0 posts today

What #OpenStreetMap routing method would you use to draw a reasonably efficient route to visit a number of coordinates (dozens, hundreds of places)?

#OpenRouteService is the only option mentioned in wiki.openstreetmap.org/wiki/Tr .

For example: tour of 35 #Helsinki city #libraries. I did the track manually on #GraphHopper and imported it on #uMap. Surely there's a better way?
graphhopper.com/maps/?point=60
umap.openstreetmap.fr/en/map/h

Hey #OpenStreetMap peeps, how can I debug this strange routing behavior?

#GraphHopper & #OSRM make a simple left turn (correct), while #Valhalla and #OsmAnd act as if there's a turn restriction and make a U-turn instead.

This is at 51.73201° N, 9.97389° E, coming from north on B3 and going to the east on A7.

There's been a construction site here a few weeks ago, so my first suspicion was stale data, but even with OsmAnd Live it still does it.

I can't see any restrictions in the data. Ideas?

Replied in thread

@blausand Nun ja, die Routenvorschläge von #GraphHopper fürs Fahrrad sehen dann aber auch sehr nach quick'n dirty aus. Habe vorhin mal probehalber Start und Ziel fürs #mdrza eingegeben. Suboptimal wäre untertrieben. Dann doch lieber bei #osmand (ggf. mit #BRouter als offline Engine) ein paar Sekunden warten und dafür eine wirklich brauchbare Route erhalten.
Und wenn ich vorab planen kann, suche ich mir die Routen auf #bikerouter und importiere die Tracks dann zum Navigieren in OsmAnd.