[Tagging] Draft proposal for Key:aerodrome

Colin Smale colin.smale at xs4all.nl
Wed Sep 11 07:23:29 UTC 2019


On 2019-09-11 09:05, Graeme Fitzpatrick wrote:

> On Tue, 10 Sep 2019 at 20:24, Andy Townsend <ajt1047 at gmail.com> wrote: 
> 
>> That seems like a bad idea because aerodrome:type is one of the ways 
>> that mappers distinguish between military and non-military airfields.
> 
> We have at least 3 aerodromes that I know of (& I know there are others worldwide) where a common runway is shared between an Air Force base on one side, & a civilian airport on the other.

We should seperate physical characteristics (it's a runway) from
facilities provided (customs?) and usage modes (civilian and military)
and other non-mutually-exclusive dimensions. This discussion is all
about how people want to try to map an enormous number of combinations
of different aspects onto a very limited set of categories and expect it
to suit every case. It never will. We map the physical, verifiable
aspects, and not subjective data. A few people arguing not about the
objective characteristics, but about what THEY would call it in their
culture/experience, is not the best use of everyone's time. The
renderer/data consumer should be able to decide which airports to give
prominence to; we should provide the data they need to make that
judgement. If a map wants to consider all airports with a runway of at
least 3000m, an IATA code and customs facilities as "international", we
facilitate that by tagging runway length, IATA code and the presence of
customs as discrete characteristics. That's the only way to stop these
endless circular discussions which never reach real consensus anyway,
and can be considered to be "tagging for the renderer" as the tagging is
being designed to produce a particular outcome.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20190911/ef781657/attachment.html>


More information about the Tagging mailing list