[Tagging] Feature proposal - RFC - Aviation obstacle light
NKA mapper
nkamapper at gmail.com
Thu Mar 8 20:42:51 UTC 2018
Date: Thu, 8 Mar 2018 08:27:42 +1100
From: Warin <61sundowner at gmail.com>
>* > conditional tagging could be used ..
*>* > light_source:conditional=high intensity flashing white
*>* > light at sunrise-sunset:low intensity flashing red light at
sunset-sunrise*
> The day/night is the conditional thing .. and there is already a syntax
> for that. So no need to invent another syntax to do the same job in a
> different way.
What I wanted to avoid is the long "high intensity flashing white
light" part where alle attributes are combined into one line. The
conditional part would work, and I am fine with that (although I have
only seen it for opening hours and for access so far). It would look
like this:
airmark=obstacle_light
+ airmark:light:colour:conditional=white at sunrise-sunset;red at sunset-sunrise
+ airmark:light:character=flashing
+ airmark:light:intensity:conditional=high at sunrise-sunset;low at sunset-sunrise
In most cases tagging will be a lot simpler, for example for an
ordinary steady red light:
airmark=obstacle_light
+ airmark:light:colour=red
+ airmark:light:character=fixed
> The syntax for the light ... has that not already been done for seamark?
Yes, and I am modeling the proposal on that. Several (sub)keys are
used to fully describe all attributes of the light.
> As the obstacle is not being tagged - leave that word out. What is being
> tagged is a warning light for aircraft .. so airmark:light I think is
> better.
I am fine with that. We still need to have airmark=obstacle_light in
the first line in the examples above because there are many other
different aeronautical lights, and we need to denote that the light is
marking an obstacle. The other attributes could use the airmark:light
key, as in the examples above.
I will copy your input to the discussion page for the proposal to keep
all comments in one place.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20180308/68c62f52/attachment.html>
More information about the Tagging
mailing list