[Tagging] how to care about different seasonal road close?

[Micah Cochran]

You might use the "seasonal" key, which seems like it might already be used
to indicate if a highway is open or closed seasonally.  I can't find a
proposal for that use.

This could be seasonal=spring;summer;autumn

There are 54,768 instances of seasonal=yes, which seems fairly useless
unless you are referring to natural phenomenon (streams).

However, I wouldn't count on routing software to recognize this key.  It
would be nice if the software would warned you that this route might be
closed for the season.

I would use that tagging scheme at your own risk.

Regards,
Micah
-- 

*Micah Cochran*

GIS Coordinator  -  City of Athens  -  Engineering Services & Community
Development Dept.  -  Dept. of Public Works Building  -  1600 ELM ST W,
Athens, AL  <http://g.co/maps/ncrp7> - geo:34.820608,-86.991474 -  p.
256-233-2224  -  f. 256-233-8791 - www.athensalabama.us

On Thu, Mar 16, 2017 at 9:02 AM, Hakuch <hakuch at posteo.de> wrote:

> The road after this point (northwards) is closed in the winter season.
>
> https://www.openstreetmap.org/note/917369#map=17/50.79221/15.32156
>
> But like Petr says, its each year another time. I had the bad luck to
> route through this street with maps.me because it is not tagged for
> 2017, OSRM seems to not care for the year and does not route there. But
> graphhopper and mapzen does. And Maps.me, and because it is really a
> dead end when you went up there by car its a long way backwards..
>
> So, is there a solution how to deal with roads like this, where you know
> that the road will be closed but you dont know the exact time? Because
> like here, people will forget to tag it for each year.
>
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20170322/9527e982/attachment-0001.html>