Is maxspeed:practical used for routing?

[riemjoe]

When planning routes, I often run into the problem that while one route might be faster based on maxspeed, turns, curves, and road conditions make it impossible to drive at maxspeed, so another route would actually be much more practical.

Here’s an example from Norway: There’s a lake - on the right runs the current road, which is well-maintained, relatively straight, passes briefly through a town, and has a speed limit of 50. At the same time, on the other side, there’s a single-lane road with sharp curves; the speed limit is 80 km/h throughout - but you can only drive 30–40 km/h.

I've had this problem with OrganicMaps quite a few times - suggests a supposedly fast route, but it also directs me down “unpleasant” streets, which makes my drive more “stressful” and ultimately takes me longer. That's why, especially in unfamiliar areas, I end up using Google Maps after all.

In OpenStreetMap, there's the controversial keyword “maxspeed:practical,” which describes how fast you can actually drive. This is controversial because practical speed is subjective and cannot be precisely defined.

Is it taken into account in Organic Maps' routing? If not, could a setting be added that allows users to choose for themselves whether practical speed should be considered? Or is there already a better solution for this?

Maybe it's also an option to factor in time spent at traffic lights and intersections and to reduce speed based on curves. But that would probably make the route calculation take much longer.

[biodranik]

• Google provides better results based on collected statistics from other Google users.
• Note that Organic Maps ignores any turn / bump / traffic light penalties at the moment.
• There are not so many maxspeed:practical tags, but it is feasible to support it.
• For roads you've experienced wrong ETA, did they have practical tag set?