On Sun, Jun 15, 2014 at 4:00 AM, Fernando Trebien
fernando.treb...@gmail.com wrote:
For several applications, such as navigation software, a distinction
would be very interesting, allowing the display of rural primaries and
secondaries when zooming out, a more accurate speed guess when the
Both maxspeed=countrycode:zone type and maxspeed=zone type are
evil, as we need to have a separate DB for those zonal limits. Please, just
use maxspeed=number.
--
Cheers,
Andrew
___
Tagging mailing list
Tagging@openstreetmap.org
2014-06-17 11:09 GMT+02:00 Andrew Shadura and...@shadura.me:
Both maxspeed=countrycode:zone type and maxspeed=zone type are
evil, as we need to have a separate DB for those zonal limits. Please, just
use maxspeed=number.
I see this similarly, use maxspeed=number and source:maxspeed (to
I disagree with just using a number, the tags are there to indicate that the
mapper had interpreted the speed limit from the type of road.
Should the limits change they make finding the limits that require changes
easier.
The number should be tagged, and I would not expect a data consumer to use
On 6/17/14 5:24 AM, Philip Barnes wrote:
The number should be tagged, and I would not expect a data consumer to use
maxspeed tags, they are useful for validation.
there are any number of reasons why a consumer might use a
maxspeed tag, the most obvious of them being a routing engine
attempting
Hello,
On 17 June 2014 13:36, Richard Welty rwe...@averillpark.net wrote:
On 6/17/14 5:24 AM, Philip Barnes wrote:
The number should be tagged, and I would not expect a data consumer to use
maxspeed tags, they are useful for validation.
there are any number of reasons why a consumer might
Hello,
On 17 June 2014 11:24, Philip Barnes p...@trigpoint.me.uk wrote:
I disagree with just using a number, the tags are there to indicate that the
mapper had interpreted the speed limit from the type of road.
Should the limits change they make finding the limits that require changes
easier.
There are several differences in my view:
1. When viewing the map offline, the user wants to see only rural roads
when zooming out really far.
2. If you don't have maxspeed for a particular way, a clever app that knows
typical speeds for each type of way in each country can make a more
educated
Andrew Shadura wrote:
Both maxspeed=countrycode:zone type and maxspeed=zone type
are evil, as we need to have a separate DB for those zonal limits.
Please, just use maxspeed=number.
Any router that deals with more than one type of traffic will need to do
that anyway, as many places have
On 6/17/14 8:24 AM, SomeoneElse wrote:
* I've yet to see a bicycle router enforce the (pedalling) furiously
implications of
http://www.legislation.gov.uk/ukpga/Vict/10-11/89#pb3-l1g18 , for
example!
i think there's a lot of interest in pedestrian and cycling routing,
but it still has a long
This was my thoughts against proposing zone tagging for Oregon speed
limits.
On Jun 17, 2014 4:10 AM, Andrew Shadura and...@shadura.me wrote:
Both maxspeed=countrycode:zone type and maxspeed=zone type are
evil, as we need to have a separate DB for those zonal limits. Please, just
use
Osmand and pretty much any other nav software worth it's salt already
interprets maxspeed (though I wish minspeed was also factored in more
often).
On Jun 17, 2014 4:25 AM, Philip Barnes p...@trigpoint.me.uk wrote:
I disagree with just using a number, the tags are there to indicate that
the
Maxspeed is not the only issue. See my previous message:
https://lists.openstreetmap.org/pipermail/tagging/2014-June/017860.html
On Tue, Jun 17, 2014 at 6:06 PM, Paul Johnson ba...@ursamundi.org wrote:
Osmand and pretty much any other nav software worth it's salt already
interprets maxspeed
Hello everyone,
Time and again I get myself thinking why is that we use a single
classification system for rural and urban ways. To me, an urban
tertiary is usually very different from a rural tertiary, both
physically and functionally.
For several applications, such as navigation software, a
14 matches
Mail list logo
