← Back to context

Comment by eCa

2 years ago

How does https://cycle.travel/map/ perform routing-wise in Amsterdam?

(Unaffiliated happy user.)

Maybe slightly better, but still not great. It's skipping the eastern part of the Sarphatistraat. Also it struggles with street names and encourages you to only type a town, which isn't very useful.

I like that it allows you to choose between paved, gravel or any. Although gravel may still be too limited for some; mountainbikers like dirt tracks, and I've had Google Maps send me through loose sand that would probably require a BMX.

  • > Also it struggles with street names and encourages you to only type a town, which isn't very useful.

    Oh, good spot. Fixed. OSM geocoding is better than it used to be - I used to just say "town" because streetnames were partial, but they're pretty good now.

    If you have a start and endpoint that should use Sarphatistraat but don't, I'm all ears. (It's my site!)

    • That's an amazingly quick fix!

      Try "Feike de Boerlaan" to "Vondelpark". I would expect the trip to take the Czaar Peterstraat and then the Sarphatistraat, but instead it takes the Panamalaan, Zeeburgerdijk, Mauritskade, and only switches to the Sarphatistraat at the Weesperplein, which I think is also the point where the Sarphatistraat changes from a bike street to a regular street with a bike lane. Although it later switches back to bike street again yet the route stays on the bike street.

      So I have no idea what's going on with that first part of the Sarphatistraat. It's a really nice route, yet all apps hate it.

      5 replies →