Aeroways

From OpenStreetMap Wiki
(Redirected from Airport)
Jump to: navigation, search
Available languages — Aeroways
· Afrikaans · Alemannisch · aragonés · asturianu · azərbaycanca · Bahasa Indonesia · Bahasa Melayu · Bân-lâm-gú · Basa Jawa · Baso Minangkabau · bosanski · brezhoneg · català · čeština · dansk · Deutsch · eesti · English · español · Esperanto · estremeñu · euskara · français · Frysk · Gaeilge · Gàidhlig · galego · Hausa · hrvatski · Igbo · interlingua · Interlingue · isiXhosa · isiZulu · íslenska · italiano · Kiswahili · Kreyòl ayisyen · kréyòl gwadloupéyen · Kurdî · latviešu · Lëtzebuergesch · lietuvių · magyar · Malagasy · Malti · Nederlands · Nedersaksies · norsk bokmål · norsk nynorsk · occitan · Oromoo · oʻzbekcha/ўзбекча · Plattdüütsch · polski · português · português do Brasil · română · shqip · slovenčina · slovenščina · Soomaaliga · suomi · svenska · Tiếng Việt · Türkçe · Vahcuengh · vèneto · Wolof · Yorùbá · Zazaki · српски / srpski · беларуская · български · қазақша · македонски · монгол · русский · тоҷикӣ · українська · Ελληνικά · Հայերեն · ქართული · नेपाली · मराठी · हिन्दी · অসমীয়া · বাংলা · ਪੰਜਾਬੀ · ગુજરાતી · ଓଡ଼ିଆ · தமிழ் · తెలుగు · ಕನ್ನಡ · മലയാളം · සිංහල · ไทย · မြန်မာဘာသာ · ລາວ · ភាសាខ្មែរ · ⵜⴰⵎⴰⵣⵉⵖⵜ · አማርኛ · 한국어 · 日本語 · 中文(简体)‎ · 吴语 · 粵語 · 中文(繁體)‎ · ייִדיש · עברית · اردو · العربية · پښتو · سنڌي · فارسی · ދިވެހިބަސް
Logo. Feature : Aeroways
One example for Feature : Aeroways
Description
Describes the fixed physical infrastructure associated with the air travel, including airports, runways, helipads, and terminal buildings.
Group

Aeroways

Tags

aeroway=aerodrome
aeroway=heliport
aeroway=runway
aeroway=taxiway
aeroway=apron
aeroway=terminal
aeroway=helipad

This page gives an overview of mapping airports and aviation-related items in OpenStreetMap. For a detailed list of tags see aeroway=*.

Most aviation activity is centred on aerodromes (or airports); these facilities are tagged with aeroway=*. The most well known examples are huge international airports with multiple runways, terminal buildings with large retail areas, and a lot of (non-aviation) public transport links, but these tags apply just as well to small private grass strips.

How to Map

Like most things in OSM, you can start with a node tagged only with aeroway=aerodrome and name=*, and add more detail over time. The most common elements are the aerodrome tag, runways, taxiways, aprons, terminal buildings, and often hangars. These are sometimes tied together with a site relation. More tags below.

Item Tags Description
Aerodrome aeroway=aerodrome
NodeAreaRelation
aerodrome=*
name=*
iata=*/icao=*
A place from which flight operations take place. Term includes airports, aerodromes, airfields, and landing strips whether international, private, military or otherwise; optional aerodrome=* may be used to classify what type of aerodrome it is. Other common tags include name=*, iata=*/icao=*, ele=*. An aerodrome may include 0 or more runways, taxiways, hangars, aprons, terminals or helipads. A Heliport is a special type of aerodrome serving only helicopters. Aerodromes can be drawn as a node, area or a multipolygon.
Heliport aeroway=heliport
NodeAreaRelation
A Heliport is a special type of aerodrome serving only helicopters. Differentiated from an aerodrome by the typical lack of a runway; uses the same tags as aeroway=aerodrome. May include 0 or more helipads, taxiways, hangars, aprons or terminals. Not the same as aeroway=helipad (an area, on an aerodrome or heliport, used for the landing or takeoff of helicopters)
Runway aeroway=runway
Way
surface=*
width=*
The area of an aerodrome used for the landing and takeoff of aircraft. ref=* indicates the runway designator (e.g. 03L/21R). Other common tags include surface=* and width=*. Drawn as a way; area mapping is becoming more common but is disupted; (see discussion here and here). Optional Lifecycle tags may apply.
Helipad aeroway=helipad
NodeArea
surface=*
An area used for the landing or takeoff of helicopters. May be found at a Heliport, Aerodrome, or as a standalone facility. Common tags include name=*, ref=* and surface=*. Drawn as a node or area.
Taxiway aeroway=taxiway
Way
surface=*
width=*
Taxiways are paths connecting various parts of an airport so that aircraft may move between them. Usually labeled alphabetically (e.g. A; or Q1, Q2, Q3); use ref=*. Other common tags include surface=* and width=*. Drawn as a way; like runways, area mapping is disputed (see discussion here and here). Optional Lifecycle tags may apply.
Holding position aeroway=holding_position
Node
Holding positions are tagged on nodes along a taxiway, or runway to indicate locations at which aircraft may be required to stop, typically in order to remain safely clear of an intersecting runway or taxiway.
Apron aeroway=apron
Area
surface=*
Areas were aircraft are parked or are serviced. Usually named either alphabetically (e.g. "Alpha") or by purpose (e.g. "Cargo Apron"). Common tags include name=* and surface=*. May contain parking positions, taxiways, and helipads. Drawn as an area.
Aircraft Parking aeroway=parking_position
Node
A location (usually on an apron) at which an aircraft may park. Name and location doesn't necessarliy correspond with aeroway=gate. Drawn as a node.
Gate aeroway=gate
Node
ref=*
Location, usually inside a terminal building where passangers go to board/disembark an aircraft. Not the same as aeroway=parking_position. Common tags include ref=*. Drawn as a node.
Terminal aeroway=terminal
Area
Building used for the prcessing of passengers and cargo. Implies building=yes; entrance may be tagged with building=entrance. Common tags include name=*. Often contain shops, other amenities, and links to other public transport systems. Usually associated with one or more gates. Drawn as an area.
Hangar aeroway=hangar
Area
Buildings where aircraft are stored or repaired. Implies building=yes. Drawn as an area.
Grass landuse=grass
Area
Areas of grass that aren't part of something else. Combinations of aeroway=*, surface=grass may be more appropriate, but only if the area has a specific function.
Navigation aid airmark=beacon Use airmark=beacon on nodes representing navigation aids such as VORs, ILS and NDBs.
Beacon man_made=beacon Use man_made=beacon nodes to mark navigation lights.
Papi/Vasi aeroway=papi
aeroway=vasi
A visual landing aid consisting of a number of lights; shows pilots whether they're approaching a runway at the correct angle. Drawn as a node. See also Wikipedia-16px.png PAPI or Wikipedia-16px.png VASI.
Windsock aeroway=windsock
Node
lit=*
Shows wind direction; consists of a (fabric) cone mounted on top of a mast. May be lit (lit=yes). Drawn as a node.
Public Parking amenity=parking Many aerodromes also include various forms of parking, mapped as areas tagged with amenity=parking. Multistorey Car Parks should be mapped as areas tagged as amenity=parking and parking=multi-storey. Provide an identifier or name using ref=*.
Service road highway=service Mark internal service roads as ways tagged with highway=service. Include access=private if the public are not able to use them.
Tower man_made=tower Map any control towers using man_made=tower and service=aircraft_control. (Proposal Only)

Aerodromes often contain numerous amenities and transport links which can be mapped individually. Guidelines for each of the transport links can be found in their individual pages. Railway stations, Subways, Taxi Ranks, Bus Stations.

Some amenities often found in and around aerodromes can be found below;

Websites such as flightaware.com and skyvector.com are often helpful for finding ICAO codes. IATA codes can be obtained from the official IATA database (search by → location name).

Not for aeronautical use!

Main article: Aviation. The mission-critical nature of aviation means that data you find in OSM is not suitable for aeronautical use. Wiki-derived data is unlikely to pass strict certification requirements (not even for simple recreational flying). OSM data is generally very accurate, but it just might not be accurate enough for aviation.

That said, many will still find such information useful, so don’t stop contributing.

See [discussion on uploading aviation tracks] on help.openstreetmap.org, and Aviation for detailed reasoning

Don't map airspace

The regular on-the-ground rule of OSM applies. If it’s something tangible that you can point at (like a runway, helipad, or gate) then you can add it. If you can't do that (as with airspace, routes, and aeronautical waypoints) then you should leave it out; check out OpenAviationMap instead. Similarly, don’t upload your flight path traces, or draw air routes on the map: routes vary because of weather, time of day, amount of traffic, serviceability of facilities, and the number of ants in the coffee machine. Besides, they’ll probably annoy other mappers (the routes, and maybe the ants too).

Routes

There’s no method for mapping airline services between airports. This might be solved by using relations but airline schedules change regularly, so OSM might not be the best place to store such data.

Proposals

Examples