Aeroways
 Feature page: Aeroways
|
|
| Description |
| Mainly for the fixed physical infrastructure associated with the air travel, including aerodromes, helipads and small airstrips. |
| Tags |
| aeroway=aerodrome aeroway=apron aeroway=runway aeroway=taxiway aeroway=helipad aeroway=terminal |
Mainly describing aerodromes large and small.
Contents |
Aerodromes
Aerodromes (or Airports) range from small private facilities with a single grass strip to major international aerodromes with multiple runways, terminals and many related facilities. An aerodrome may be mapped simply as a single node with aeroway=aerodrome and probably a name=* or can be mapped in considerable detail. In reality aerodromes often start with a simple representation and gain detail over time. The elements that make up an aerodrome can all be associated with site tag. An aerodrome will include a number of the following elements:
| Tag | Description |
|---|---|
| Aerodrome | Can be tagged as a node, an area or a multipolygon. As well as having a aeroway=aerodrome it should also have a name=* and may have an iata=* or icao=* code and many others. This node should also contain type=* to indicate what type if aerodrome it is: (public, military, private or some other type). For complex boundaries a relation:multipolygon can be used (for example, see Norwich airport). Using a relation in this way allows a boundary to be constructed from a number of elements, such as fences, walls and parts of buildings. The boundary may be for the entire aerodrome complex, or for 'airside only. |
| Apron | Use aeroway=apron to identify areas were planes are parked or are serviced. If an apron has a particular purpose or designation then provide this using name=* (eg 'Parking area 15' or 'de-icing'). |
| Beacon | Use man_made=beacon nodes to mark navigation lights. |
| Gate | Use aeroway=gate to identify each departure gate and include a ref=* if this is known. |
| Grass | Mark areas of grass with landuse=grass. |
| Hangar | Buildings where planes are stored or repaired should be tagged with aeroway=hangar. |
| Helipad | Mark helipads with aeroway=helipad using a node or area and ideally also a ref=*. |
| Holding position | Use aeroway=holding_position on nodes along the taxiway, runway to identify holding positions. |
| Papi/Vasi | A PAPI or VASI should be marked by a node and tagged as aeroway=papi or aeroway=vasi. |
| 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 uaing ref=*. |
| Runway | Each runway should be drawn as a way and tagged as aeroway=runway with ref=*. Use surface=* for the runway surface. Runways can be defined as ways or as areas. A proposed new runway, or a runway under construction should be tagged with aeroway=construction (or aeroway=proposed) and construction=runway. A disused, but generally function runway should be tagged with either disused=yes or as disused:aeroway=runway. A abandoned runway can be tagged with abandoned:aeroway=runway. |
| Service road | Mark internal service roads as ways tagged as highway=service. Include access=private if the public are not able to use them. |
| Taxiway | Each taxiway should be drawn as a way and tagged as aeroway=taxiway with ref=*. Use surface=* for the taxiway surface. A proposed new taxiway, or a taxiway under construction should be tagged with aeroway=construction (or aeroway=proposed) and construction=taxiway. A disused, but generally function taxiway should be tagged with either disused=yes or as disused:aeroway=taxiway. A abandoned taxiway can be tagged with abandoned:aeroway=taxiway. |
| Terminal | Each terminal should be drawn as an area tagged as aeroway=terminal with a name=*. Tag the entrance to the terminal using a building=entrance node. use name=* for the terminal name (eg 'terminal 1', 'main hall'). |
| Tower | Map any control towers using man_made=tower and service=aircraft_control. (Proposal Only) |
| Windsock | Mark aeroway=windsocks as a node. If it is lighted, include lit=yes. |
Aerodromes often contain numerous amenities and transport links. Where appropriate, these amenities and links should be individually mapped. 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;
- amenity=atm
- amenity=cafe
- amenity=fast_food
- highway=bus_stop
- railway=subway_entrance
- amenity=pub
- amenity=telephone
Websites such as [1] and [2] are often helpful when trying to ascertain iata or icao codes.
Routes
In addition to correct tagging of the serodromes themselves, it may be useful to map the actual services that run between these aerodromes. Currently a method for doing this is not in common use, however it may be addressed in the form of relations adding to Routes! Do not trace explicit flight routes, because they are varying (see [3])
Flight paths
Don't do it. See http://help.openstreetmap.org/questions/297/does-it-make-sense-to-upload-aviation-tracks-to-osm on help.openstreetmap.org for a discussion why.
No-fly zones/airspace
We do not map un-observable things like airspace or circuits. See Aviation for detailed reasoning.
Proposals
- Abandoned (inactive): Proposed features/Aerodrome (unified symbol set)
- aeroway=landing_light - for a light on the approach to the runway.
- There is a current discussion about how the aeroway key should also be used for installations catering to model aircraft. See Proposed_features/Model's_Aerodrome.
Example
A good example of a well mapped airport is that of Heathrow in England, which can also be seen at the bottom of the page.
| |||||||||||||||||
