Even in the Netherlands, it's often better than Google Maps. And it can serve as the basis for apps building on top of it like https://cycle.travel/.
Even in the Netherlands, it's often better than Google Maps. And it can serve as the basis for apps building on top of it like https://cycle.travel/.
It uses OpenStreetMap data plus a heavily customised instance of OSRM (Open Source Routing Machine, a fast routeplanning engine). The routing "profile", which calculates the weighting, is a few thousand lines of code alone, never mind various other stuff like custom elevation calculations.
It's a great project to work on, and the best reward of all is when people plan multi-day tours with it and say how much they've enjoyed the route.
Edit: This looks pretty great, but I should probably point out that it turned my 5.5 mile commute into a 8.5 mile one. Realize it's probably trying to avoid larger streets; Hope this is or becomes configurable.
Edit: Thanks everyone for the feedback! Just pushed a quick fix:
- USA now defaults to miles & feet
- Canada and Mexico now default to km & metres
- Britain defaults to miles & metres (as before, yes we're weird)
- mainland Europe, Australia and NZ default to km & metres (as before)
The USA should be feet and miles.
Canada should be metres and kilometres.
But you did say North America, it seems these might use miles per hour for road speeds, so they might not want metres and kilometres. I don't know if they want feet, yards or metres though.
Antigua, Bahamas, Barbuda, British Virgin Islands, Grenada, Puerto Rico, St Kitts and Nevis, St Lucia, St Vincent and the Grenadines, or the US Virgin Islands.
It'd be better to prefer roads that are further from busy roads. I understand that's very hand-wavey and probably super tricky to implement.
I've got a page of notes on possible ways of fixing this - it is a hard problem. One possibility I'm toying with is a massive grid of "scenic value" for (say) each 0.01° x 0.01° square, so I could downrate the surroundings of motorways and uprate routes through (say) national parks.
The OSM directions for biking to my office involve going through a decommissioned oil field (fenced off, so the road isn't actually passable) and a swamp. What's weird is that it looks like OSM knows the road is closed but still tries to route me through it. Google's directions for the same destination aren't perfect either but at least they'd get me to my destination (they include a short jaunt down an eroding hillside where I have to walk my bike because the sand is so loose).
That cycle.travel site looks really promising. They give the same route as Google Maps, but do a much better job explaining that part of it is an unpaved dirt trail.
The routing errors you describe could be issues with the particular route planner you used, or they could be issues with the OSM data itself.
Some parts of the world are indeed better mapped than others (this is also true of Google Maps), but the great thing about OSM is if you find an error you can fix it yourself in seconds.
Just click that “edit” button right there in the OSM interface...
Is that actually true if you are on a bike? In my city OSM is a good source of unofficial bikeways. What does the cycle layer have to say?
If you click on the mouse cursor button on the right and then click on the symbol, it will show you the details for that object.
Nobody needs a single entity corporation to do everything for them, it's really time people see that there is shopping experience besides Amazon and search/map experiences besides Google.
Google maps is the default option for most people. Why would we want to make it harder for people to start cycling by forcing them to hunt down some specialist app that they don't even know exists? Why not just have the information in the app they're already using?
* in the general sense, not just today’s sense, like roads, bridges, power, water etc.
I have no reference to hand agreeing with me, but somehow I suspect that Google Maps is not the biggest barrier between Joe Commuter and the bicycle.
The set of people who would happily upload cycling data minus their precise start/endpoint is probably 1000x larger than the set of people who enjoy map curation in their free time, but I’m not sure what solution I can present to bicyclist friends that would let them contribute.
The Strava heatmap is also licensed for usage in OSM, and in a lot of areas it has pretty good coverage of bike paths already (https://wiki.openstreetmap.org/wiki/Strava).
[1] https://osmcha.org/?filters={"source"%3A[{"label"%3A"strava"...}
The thing I would much prefer is clear signage. The lack of it is common.
That said, I think Portland has done a great job with the signage part of this problem. Signs like [1] are present at just about every intersection of bike routes, giving directions to neighborhoods and landmarks. And when a bike route dog-legs, directional "sharrow" symbols [2] are clearly visible on the road surface.
[1]: https://nacto.org/case-study/bikeway-network-signage-in-port...
[2]: https://nacto.org/publication/urban-bikeway-design-guide/bic...
I know I can find out by trying different apps but I appreciate you potentially saving me time. Thanks!