Martijn,
Following your lead, SR20 in Washington State is now closed from milepost
134 to 171 with a fixme to check in spring. I've signed up for an email to
notify me when the road is reopened. FWIW, RS20 is in my backyard. I take
it often.
What would be nice is a tag or note that had a follow up
Simon,
I'm not looking to add complexity. I'm looking to find a way to deal with
future events that are certain to impact a feature as described in my
original post. Basically a way to remind ourselves as a mapping community
that a feature as it exists currently should be revisited at a fairly wel
Actually, OSM is not made for real time information.
Closing a road in autumn and open it spring? Ok it's twice a year, but you're
not even sure you can maintain it. What about ski pistes, traffic lights,
traffic jams?
Yves
Le 28 novembre 2016 20:08:58 GMT+01:00, Simon Poole a écrit :
>I'm
I'm note quite sure why this use case wouldn't be covered by the normal
opening_hours specification as long as we are talking about regular
seasonal or month based openings/closures.
Given that opening_hours (and the other tags that use the same
specification) already includes everything and the k
See https://www.openstreetmap.org/changeset/44013342 for a tagging example.
Martijn van Exel
http://mvexel.github.io/
On Mon, Nov 28, 2016 at 10:52 AM, Martijn van Exel wrote:
> Hi,
>
> When mapping seasonal closures here in Utah[1] I realized I am still
> missing a solid way to mark a road as
Hi,
When mapping seasonal closures here in Utah[1] I realized I am still
missing a solid way to mark a road as closed for the season and then have
some level of confidence that someone will look at it in the spring and
'reopen' it. More generally for someone to map a feature and somehow tag it
as
6 matches
Mail list logo
