[maelito]

> "let's go up this single track road with a 20% gradient to save 2 minutes"

Not sure this is a good example : elevation data should be good enough to avoid this kind of roads. See e.g. https://sonny.4lima.de for Europe.

For your general thought, see here : https://blog.google/products/maps/google-maps-101-how-we-map...

> It all starts with imagery

> Street View and satellite imagery have long been an important part of how we’re able to identify where places are in the world—it shows us where roadways, buildings, addresses and businesses are located in a region, in addition to other important details—such as the town’s speed limits or business names.

So I guess what you're proposing is already done for several years but in more subtle ways.

Remember that Google Maps doesn't have the power of OSM. Hence the need for automation.

[globular-toast]

> Not sure this is a good example : elevation data should be good enough to avoid this kind of roads.

I'm not sure elevation data is enough, nor is speed limit. In many places, like the Cotswolds, the main route includes a 20% gradient. The difference is the road will be wide with overtaking lanes etc. and often a reduced speed limit. Then you have places like Devon where there are national speed limit (the highest) roads with such poor visibility they are best avoided unless you have no other choice. I find it's hard to know what the quality or "character" of a road will be until you actually get there, but Google seems to treat them all equally.