My best guess is it’s a busy road so it’s dangerous and not really meant for bicycle and walking. I’ve done 13 miles yesterday to get a comic book on a bike and this right here is the distance between my house and a friend’s house I told I can come on bike because what I just did gave me a feeling I could do it but my ass hurts so not right now. But yeah I want to see how this would play out. Before I would walk but I took a bike to a comic book store because it would’ve closed if I walk and I ended up getting there in time. Took longer than expected something that should’ve been an hour probably took 2 or 3 hours. So yeah I can do half of that for sure.
I think it mainly means that Google invests a lot more money in the quality of its navigation for cars than bicycles, meaning that they think it’s pretty likely that the cycling directions might lead you into a place where it might not be a good idea to cycle.
And it’s still shit. It reccomends an illegal left turn and I see every day someone that tries to make it.
Google maps became an ad platform.
Fortunately no one is forced to use it in a world where OpenStreetMap and apps that use it exist (OSM is exactly as good as volunteers made it).
I am for work. no other app has Good ETA, traffic, and multi node route planning, decent readable design.
Waze (owned by google) - no multi node
OSMand - unreadable design
organic maps - no good ETA
mapy.cz - no local traffic
Magic earth - to be tested
Circuit - it would be an overkill for my use case
“We make more money from cars. We half assed the walking instructions. Good luck and fuck you.”
It’s 100 % because they don’t really know if bikes can go on the roads it tells you. Their focus is clearly on cars, and they don’t feel comfortable in their guesses on bikes, specially considering that the risks of bad injury skyrocket if you ride somewhere where you shouldn’t.
