Tag:aeroway=aerodrome

From OpenStreetMap Wiki
Jump to: navigation, search
Available languages — Tag:aeroway=aerodrome
Public-images-osm logo.svg aeroway = aerodrome
600px-20 airtransportation inv.svg.png
Description
An aerodrome other than heliport
Used on these elements
may be used on nodesshould not be used on waysmay be used on areasshould not be used on relations
Useful combination
Wikidata
Wikidata-logo.svgQ1248784
Status: In use

The aeroway=aerodrome key is used to hold all the main details for an aerodrome. Preferably this is the airport's ARP, but it can also be associated with the area around the perimeter of the aerodrome.

When it is meant just for helicopters, use aeroway=heliport instead.

How to Map

Either create an enclosed way around the extent of the airport land (often co-incident with a barrier of some kind). For complex boundaries create a relation:multipolygon and add the tags to the relation. In addition to the mandatory 'aeroway=aerodrome' tag the following are available:

Useful Combination

Tag Description
addr= Contact address for management
ele= Elevation. Possibly at arbitrary position, tower, runway centerpoint, etc. See individual elevations on runways and their endpoints for more specificity.
iata= 3-character code issued by the IATA and commonly known and used to identify public airports. May not be present for smaller/private airports.
icao= 4-letter code issued by the ICAO. For US airports, often the IATA code is prefixed by a "K".[1]
operator= The name of the operator of the airport
phone= Contact phone number for airport management.
ref=* Instead of using this key for an airport code, use a more specific key, such as iata=*, icao=* and faa=*
source= Source(s) of information present in tags, semi-colon-delimited if necessary. "FAA" indicates at least some information from one or more FAA databases or imports. Often combined with an imagery tag to indicate the imagery with which the boundary was drawn.
type= To identify the operational purpose of the airport. Use values of 'public' (for all airport open to paying customers), 'military' or 'private' etc.
Note that this insufficiently qualifying tag conflicts with the tagging of polygons and multipolygons. Currently there is a proposal to change this. See aerodrome=*.
aerodrome:type= Airport type (former type), Values: public, military, military/public, private (for small airports e.g. motor-sport, gliding, etc.). taginfo
variation= dd[.d] [E|W] [yyyy[-mm[-dd]]] [d.d E|W] . Indicates the magnetic variation (declination) of the magnetic north pole relative to the geographic north pole, the date of measurement, and possibly the rate of change. Example: "12.8 E 2011-11-17 0.1 W" means that a compass will read north 12.8 degrees east (clockwise) of geographic north on 2011-11-17, and that variation currently changes at a rate of 0.1 degree west per year.

Other tags that can be added in USA

Tag Description
closest_town= Nearest city and state, as defined by FAA.
faa= 3- or 4-character code issued by the FAA. Usually the same as the IATA code, but not always [2]. Present for smaller/private airports when iata tag may not be.
FAA:LFSN= The FAA's Landing Facility Site Number - a unique identifier for airports in the US. There is generally no reason to edit this value - it is used to refer back to the FAA database for synchronization of imports. Example: "01818.*A" is the LFSN for LAX.
source:date= If imported/updated from the FAA 56-day NASR database, this tag will contain the date the database became valid.
source_ref= Key to source documents. Example: when source=FAA, you may see source_ref=nnnnnAD, which indicates the document number of the FAA Airport Diagram, which are at http://aeronav.faa.gov/d-tpp/vvvv/nnnnnAD.PDF where vvvv is the version number (incremented every 56 days).

Rendering

Information sources

Note that many are the result of import from official sources, like the FAA, so be sure your edits are not in conflict.

See also