One issue with the tagging schema that you specified is that it doesn't make it clear whether the aerodrome is a "public airport".
Actually, I found out there is a better definition for what I was calling simply "airport" or "public airport". It's "public use aerodrome". According to [1], > Some States define a public use aerodrome as one that is available for use > by the general public without a requirement for prior approval of the owner > or operator > I do agree using a separate tag to define whether an airport supports international flights seems appropriate. This way we could also take into consideration the "alternatively international" airports i.e. airports that only receive international flights when the original ones can't. I read in wikipedia[2] there are some airports that do have international flights, but are limited to some close countries, and are therefore called "regional". Perhaps we could treat this case in this same key. [1]: http://www.iaopa.org/doc/icao-annex-survey.pdf [2]: https://en.wikipedia.org/wiki/Regional_airport#Regional_airport 2014-07-02 17:46 GMT-03:00 Janko Mihelić <jan...@gmail.com>: > I don't like this way of mapping. There might be some overlaps, what if > one aerodrome has a military and a public part? > > I would rather use separate tags like: > aeroway=aerodrome > access=private/public > landuse=military > international_flights=yes/no > ... > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
