Google Maps Adds Elevation Profiles To Bike Routes
techcrunch.com
techcrunch.com
When a device moves rapidly in a short period of time, you know that the sensor data will be reflecting the altitude changes and not the weather changes. Moving the device from my feet to my head shows a clear change of ~.5mb typically.
Share the recommendation for komoot, although it's quite new, and a bit buggy.
OSMAnd is also useful, not so polished, but you get a lot of power over the way you use the map, for instance searching for attractions, pubs, cycle parking, etc along the way, and it's completely offline.
Thanks for sharing
It looks nice, but still needs some polish before it's usable for me.
It's interesting to see that problem from the other direction. That site is useless for me because it can't easily decode US addresses.
Am I missing something? with the amount of effort gone into OSM I dont really understand why there isnt a top quality app to display and use all that data.
(I've never used the app, just pointing you at the router)
Then I went and bought a manual transmission car of my own. The drive back home from the dealer was one hell of a trip. I learned very quickly how tricky it is to get a car moving when you're stopped on a hill.
So I totally could have used this back then. :)
So we drove a few lurchy blocks around San Francisco - yes, San Francisco, the city of seven hills. Ah, if it were only seven!
After a while he said, "Doing great, drive me back to the dealership and you're on your own."
I knew my way home, but I couldn't remember where the hills were.
I could have used elevation data that day...
"...sweat beading upon his brow, he might recount that Damp Morning when he drove his Manual Transmission up the Impossible Grade, and was forced to stop, just below the top! In frantic pantomime, he’ll pull the emergency brake and disengage the clutch. Crane his neck to peer anxiously at the car sniffing his downhill bumper. Bulge his eyes. Gun the engine. Pop the clutch. Release the brakes. Lay down some rubber with a piercing squeal. Float his steed slowly onto the flat. Wave the smoke from his eyes. Pump his arms in brief celebration. And finally, grouse about that sadistic driving instructor who got him into the pickle in the first place. What a jerk!"
http://www.datapointed.net/2009/11/the-steeps-of-san-francis...
I followed Google Maps suggested bike route and the ones provided by Transport for London for several weeks before I figured out that I should use the main road in certain sections. Plenty of other cyclists were on the main road going roughly the same direction. The 'cyclist' route had me going on quieter roads that were just not that good. I would find myself going against the main flow of the traffic at junctions and having to navigate a lot more of them, never with the lights in my favour. Plus the distance was longer.
Why is nobody on Strava on this road? Is probably the best way to decide if a bike route is any good.
Regarding the data quality: At least in Germany the ADFC maintains its own cycle path network which also contains metadata about road surface, motor traffic and such things. This is also one of the sources Google licensed for their bike stuff in Maps (although back when they introduced it they had a very hard time matching up their two or three different data sets and there were lots of errors where junctions wouldn't connect, etc.).
Sadly in west Texas good shoulders tend to be covered in chipseal resulting in days/weeks of much vibration.
I couldn't get it to work together with a bike route.
But, but ..... what if you like those steep hills, what then?