Christoph's comment is similar to what Simon Poole said on Talk:Proposed_features/Key:aerodrome
So the alternative would be to use several new property keys instead of a single key, eg: international_flights=yes/no (presence of international passenger flights) commercial_flights=yes/no (presence and nature of regular passenger flight service) access=? (openness to public from the air/access restrictions on the ground) fuel= etc. (presence of services for airplanes) surface=* (surface and length of the runway) - length already shown But it's quite a bit more work to map an airstrip as: aeroway=aerodrome + name= + access=private + fuel=no + hangar=no + commercial_flights=no + general_aviation=no + radio=no + ? etc.... Versus just mapping aeroway=aerodrome + aerodrome=airstrip + name I suspect that mappers will continue using aeroway=airstrip in most cases, instead of setting a large number of property keys to "key=no" On the other end of the spectrum, international_flights= or commercial_flights= would not be too much trouble, but international_flights=yes/ would be a little harder to verify and keep up-to-date than whether the aerodrome has customs and immigration (=international), which can't change as quickly. _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging