Proposal talk:Airports

Name2

name2 will always be +/- 18 from name1, so there isn't much point in storing it seperately. Bruce89 13:32, 7 Aug 2006 (BST)

Also "09 Left" to "27 Right"... Ojw 14:27, 7 Aug 2006 (BST)

Woops, forgot about that. Bruce89 15:51, 7 Aug 2006 (BST)

Wouldn't heading or compass be more descriptive tags? Name1/Name2 sounds too much like alt_names. --Skippern 15:26, 3 November 2008 (UTC)

Rendering and osmarender2 rules

Just uploaded a render of Copenhagen airport. http://wiki.openstreetmap.org/index.php/Image:Osmarender-airport-EKCH.gif

Amend the osm-map-features2.xml file and add the following :

  <!-- place the following after the Non-pysical routes section -->

  <!-- draw taxiways -->
  <rule e="segment|way" k="aeroway" v="taxiway">
    <line class='aeroway-taxiway' />
  </rule>

  <!-- draw runways -->
  <rule e="segment|way" k="aeroway" v="runway">
    <line class='aeroway-runway' />
  </rule>

  <rule e="node" k="place" v="airport">
    <text k='name' class='airport-caption' />
    <text k='icao' class='airport-code-caption' dy='8' />
    <text k='iata' class='airport-code-caption' dx='20' dy='8' />
  </rule>
  
  <rule e="segment|way" k="aeroway" v="runway">
    <text k="name1" text-anchor='middle' startOffset='5%' class="aeroway-runway-name" />
    <text k="name2" text-anchor='middle' startOffset='95%' class="aeroway-runway-name" />
  </rule>

  <rule e="segment|way" k="aeroway" v="taxiway">
    <text k="name" text-anchor='middle' startOffset='33%' class="aeroway-taxiway-name" />
  </rule>

and add the following to the SVG definitions section in the osm-map-features2.xml file:

      .aeroway-taxiway {
        stroke-width: 2.5; 
        stroke-linecap: butt; 
        stroke-linejoin: round;
        stroke: lightgrey;
        fill: none;
        }

      .aeroway-taxiway-name {
        fill: black;
        font-family: verdana;
        font-size: 3;
        font-weight: normal;
        }

      .aeroway-runway {
        stroke-width: 5.5; 
        stroke-linecap: butt; 
        stroke-linejoin: round;
        stroke: grey;
        fill: none;
        }

      .aeroway-runway-name {
        fill: white;
        font-family: verdana;
        font-size: 3;
        font-weight: normal;
        }
      
      .airport-caption {
        fill: black;
        stroke: white;
        stroke-width: 0.2;
        font-family: verdana;
        font-size: 8;
        font-weight: bolder;
      }

      .airport-code-caption {
        fill: black;
        stroke: white;
        stroke-width: 0.2;
        font-family: verdana;
        font-size: 5;
      }

Dutch 10:17, 20 Aug 2006 (BST)

Consistency with existing map_features scheme

To be consistent with the existing map feature of aeroway= aerodrome, should the proposal for place=airport be replaced by aeroway=airport ? Dmgroom 15:05, 18 November 2006 (UTC)

aeroway=airport and aeroway=aerodrome and aeroway=airfield would all be my prefered way of tagging since it keeps all of the aeroway features under the same key name which may be very beneficial in the future. Blackadder 21:46, 18 November 2006 (UTC)

I agree. keeping it all under the aeroway tag makes most sense. what is wrong with the existing aeroway=aerodrome;name=XXX? --spaetz 23:20, 25 March 2007 (BST)

noting is wrong with aeroway=aerodrome, but I think the idea is that aerodromes are small places used by light aircraft, airports are much large places used by larger aircraft. Dmgroom 00:04, 26 March 2007 (BST)

Yes, in general they all are "aerodromes". Legally they are usually refined in different categories, so I understand this request to distinguish them. I believe it will be easier for all (especially renderer developers) if we add additional tags to describe airport details. There are many pieces of information to record, so we don't necessary have to swallow it all at once. For example, we can record legal type (airfield, airport, aerodrome or whatever proper english terms are), military/civil status, services (ATC, customs, maintenance, fuel), operating hours... DarkoS 15:55, 18 September 2009 (UTC)

Use of landuse for runways

Very large runways do not scale very well if drawn as ways. Would it be more appropriate to draw them as areas? They are more extensive than many features that are drawn as areas (ponds, parks, etc). Perhaps a way should be drawn along the centre of the runway to define its path and an area used to define its extent. This would be similar to the way that someone suggested drawing large rivers. 80n 10:29, 19 November 2006 (UTC)

Elevation

I propose to use Proposed_features/Altitude to denote the elevation of runways. The key is called "ele=" has been proposed for peaks and other things. So why not use that generic tag here as well? -spaetz 23:35, 25 March 2007 (BST)

I have begun marking runways elevations using "ele=XXX'" denoting feet from AirNav and Airport Facility Directory information using a node at the center of the painted number on the runway via satellite imagery. d3d9 2013/08/03 21:46

Thanks for adding elevation data. Please note that the ele=* value should be metric.--Lyx (talk) 07:22, 4 August 2013 (UTC)

Also please make sure the license of the AirNav and Airport Facility Directory give permission for copying this information. --Lyx (talk) 09:16, 4 August 2013 (UTC)

IATA and ICAO

I have made a page specifically for these two tags, as they seem to be the least controversial part of this proposal. (now at Key:icao and Key:iata) -Srw 23:32, 31 May 2007 (BST)

Holding points

Should we mark holding points on taxiways etc? NickF22 22:24, 25 September 2007 (BST)

I have begun marking runway/taxi thresholds as aeroway:holding_point using a node at the paint marker in satellite imagery. d3d9 21:43, 03 August 2013

Ground-Markings on apron

There are some thinks on the apron-area and taxiway-nodes that I would like to map and render in addition.

• aeroway=taxipath: The markings on the ground including their names (ref)
• aeroway=parkingPosition: A Position where planes park for boarding including position number (ref)
• aeroway=jetbridge: The jet-bridge including gate-number and parking-position of the plane.

Is this reasonable? --PieSchie 13:09, 18 August 2008 (UTC)

Helicopter

Many airports have designated helicopter landing zones and helicopter parking zones. Often circular marked with a large H, iluminated with a circle of green or yellow lights. In some larger cities and in connection with some important public services (such as hospitals), dedicated helicopter landing areas and helipads might be located. Such helipads often have a windsock located close by. --Skippern 01:40, 8 September 2008 (UTC)