On Wednesday, 5 December 2018 23:41:31 UTC+1, Gavinx wrote:
>
> There is an altitude widget you can configure from the Configure Screen
> menu.
>
> there are also contour maps that provide this information.
>
>
> If you are talking about selecting a specific point to get what is
> considered "e
OsmAnd does use maxspeed:advisory when just plain maxspeed=* is absent. Has
used it for a while now.
-jack
--
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 osmand+un
Jack Burke 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 (
Seems like for route planning, the safe bet would be worst case scenario,
lowest speed of the three possible maxspeed values. For example, a
mountain road that (mostly motorcycle) traffic typically whips through
curves at 70-90 km/h in a 110 km/h zone and have advisories (which are set
assuming fa
Paul Johnson writes:
> Seems like for route planning, the safe bet would be worst case scenario,
> lowest speed of the three possible maxspeed values. For example, a
> mountain road that (mostly motorcycle) traffic typically whips through
> curves at 70-90 km/h in a 110 km/h zone and have adviso
On Fri, Dec 07, 2018 at 10:01:15AM -0500, Greg Troxel wrote:
Jack Burke 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
road
"'Xavier' via Osmand" writes:
> On Fri, Dec 07, 2018 at 10:01:15AM -0500, Greg Troxel wrote:
>>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
> thi
On Fri, Dec 7, 2018, 09:27 Greg Troxel Paul Johnson writes:
>
> > Seems like for route planning, the safe bet would be worst case scenario,
> > lowest speed of the three possible maxspeed values. For example, a
> > mountain road that (mostly motorcycle) traffic typically whips through
> > curves
Paul Johnson writes:
> On Fri, Dec 7, 2018, 09:27 Greg Troxel
>> Paul Johnson writes:
>>
>> I see maxspeed:typical as being for the flow of mixed traffic that is
>> being reasonable.
>
> Not sure this is a tag we even need in this case, since it can be inferred
> automatically from the GPX data
