[OSM-talk] Navigation Debug Map Style Available

[Vincent Pottier]

Le 24/05/2010 06:52, Steve Bennett a écrit :
> On Sun, May 23, 2010 at 1:35 AM, Richard Welty<rwelty at averillpark.net>  wrote:
>    
>> yes. there's little hope for useful defaults, the defaults vary too much
>> from place to place.
>>      
> > From country to country perhaps, and maybe state to state - but not
> within states. In Victoria (Australia), guessing maxspeed=50 for
> highway=residential will be right 95% of the time. It's certainly less
> effort to build and implement a table of defaults than to tag every
> single way, but the question is: whose effort?
>
> Still, I'm going to try and make sure I tag all roads of 60kph or
> higher at least. Though it's surprisingly hard to remember them when I
> just look at the map.
>
> To Australian mappers: is there a free government source of speed limits?
>
> Steve
>    
I suggested somewhere that we could enter the defintion of default 
values, maxsped and other stuff in the relation boundary where they 
would apply, like the timezone.

Usualy those values should be entered in the country relation boundary. 
But for some values it could be a lower level : definition of holidays...

We can, if necessary, put a "def" prefix or create a special relation 
type "definition" for including those definitions (easier to manage). 
E.g (for France).
def:highway:motorway:maxspeed=130
def:highway:motorway:maxspeed:rain=110
def:highway:motorway:access:bicycle=no
def:highway:motorway:access:foot=no
def:highway:motorway:oneway=yes
def:urban=50
def:rural=90
def:highway:residential:maxspeed=urban
...

By this way, the values are :
- easy to update
- inside the osm data in .osm format
- available "just in time" for the engines, routing systems... and easy 
to get by the API for map builders (like Garmin...). An engine that 
would have "hardcoded values" woud be considered as obsolete.
- easy to use : the default value is for an area inside boundaries and 
the admin_level of the boundaries says the priority of the value to 
apply (if redefined for a smaller area)
--
FrViPofm