[OSM-talk] tagging maxspeed restricted to time span

[Stephan Schildberg]

>
>   
>> Is it possible to tag a lane which maximal speed limit (30km/h) is 
>> restrictet to a certain time span (6 am - 10 pm)?
>> How you can do that, how you can say that the time refers to speed?
>> In another case I have to relate it to oneway direction chnages.
>>     
>
> For what application do you need this information?  Is there any 
> printed map that indicates such restrictions?  Or do you plan to 
> create a route planner?
>   
When I do not store maxspeed 30 km/h and this is interupted by phases 
from 10 pm -6 am, which information is true to store. None of them?
In the city where I map this gives us apretty good overview for a dense 
population which we like to protect from noise emissions, thats almost 
why we have this limit.

When I go through the city, which has in its boundaries 1,7 m 
inhabitants I want to do this once only in a street, otherwise this 
would be endless. While storing significant information I just cannot 
decide which will be important or not. In this particular cases, I feel 
either to drop information or just give half-wrong input into the 
database. Even in cases of oneway-switches, depending on time, this will 
be significant to plan a route (only by yourself and the map, without 
software).

These are only two samples, but considering ferries, roads flodded 
during saisons of rain etc. , you would have the same problem to store 
timetables.
I want to have the possibility to store exceptions, because there are so 
many of them, they are part of my world, my model and I don not yet 
which correlations of data with other data will be useful one day, one 
project.

> My principle: Store the information so that it is useful to the 
> application you have in mind.  Let your output guide your input.
> If there is no application, don't store the information.
>
> With time information, you need to consider the local timezone,
> which currently isn't stored in OSM.
>   

This is a question of the point of view, I could store it in (GMT 5h  
until GMT 9h) or with 6 am - 10 pm (when I am sure the map will be in 
use only locally). As long as I have no renderer which calculates an 
SVG-output with javascript (which is an idea) the timezone-model is a 
bit far off.
Then the timezone should not be stored in each tag, which is ridiculous, 
but in a super-tag for a city (place = city, name = Hamburg, timezone =  
GMT +1h) , which leads us to an RDF-like structure.
> In principle this should be no harder than name:sv = Åbo,
> name:fi = Turku.  I.e. speed_limit:6am-10pm = 30 km/h
> or something to that effect.
>   

Thank you for your suggestions,

regards Stephan.