On Fri, Dec 07, 2018 at 10:01:15AM -0500, Greg Troxel wrote:
Jack Burke <[email protected]> writes:
OsmAnd does use maxspeed:advisory when just plain maxspeed=* is
absent. Has used it for a while now.
But what about when both are present?
In the US, we have the situation where on ramps (link roads, slip
roads) the regulatory white sign will be the one from the highway
(often 65 mph) and then there will be an advisory yellow sign saying
something lower, sometimes as low as 20 mph.
Then there is maxspeed:typical.
The OSM wiki has no reference for maxspeed:typical. It does have
maxspeed:practical
(https://wiki.openstreetmap.org/wiki/Key:maxspeed:practical). Perhaps
this is the tag you are referencing?
So it seems that it should use the first of
maxspeed:typical
maxspeed:advisory
maxspeed
that is present, but it sounds like you are saying that osmand only
uses maxspeed:advisory when plain maxspeed is missing.
The real question for routing is "at what speed can we expect that a
reasonable driver will traverse whis segment".
The problem there, of course, is determining what is "reasonable",
which is also a concern put forth in the OSM Wiki. In this context,
"reasonable" is highly subjective. For a competent driver, in a sports
car with good handling, their 'reasonable' traversal speed of a curvy
road will be much higher than a new driver in a vehicle with poor
handling. Even the same competent driver but in the car with poor
handling, will traverse more slowly than in the car with good handling.
So no matter what one does, or which starting point one starts from,
the computation will be wrong for some group or another of drivers.
--
You received this message because you are subscribed to the Google Groups
"Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
