Proposal:Air traffic control

Air traffic control
Proposal status:	Draft (under way)
Proposed by:	Kovposch
Tagging:
Applies to:	/
Definition:	Air traffic control facilities
Statistics:
Draft started:	2023-09-25

Proposal

Unify different air traffic control levels.

Rationale

General

• Different Tower has different responsibilities. It will do everything in a small airport, while gradually offloading tasks to be dedicated in larger airports.
• Different controllers can work outside the tower. Separate building in airside, landside, outside the airport, or even in the city center far away not close to airports. They are recognizable facilities.
• There exist remove and virtual towers now, providing tower service outside a tower. They can be permanent, or for contingency/emergency.

Existing

• man_made=tower , service=aircraft_control , and aeroway=tower are ambiguous on whether they refer to tower control, or the control tower structure. There can be multiple separate "tower" structures for eg ground control, and to cover a large airport entirely.
• Further to the above, ground control usually has different operator=* and other attributes.
• aeroway=control_centre is specified for ACC only. From its name, can it be used for terminal control centers?
• icao=* are coded for the Flight Information Region controlled by the Area Control Centre. It is currently specified for airports only.
• man_made=tower should be used for the structure only. The functionality should be separatable.

Tagging

• aeroway=traffic_control : This can be used orthogonal to the man_made=tower structure.
  • traffic_control=* : For single function. (For completeness, all services are listed. In practice, only some needs to be used.)
    • traffic_control=all_local
    • traffic_control=tower
    • traffic_control=ground (international term preferred over North American "ramp")
    • traffic_control=visual
    • traffic_control=terminal (traffic_control=approach not used for clarity)
      • traffic_control=arrival
      • traffic_control=departure
    • traffic_control=information
    • traffic_control=clearance
    • traffic_control=region (traffic_control=area not used for clarity)
  • traffic_control:*=* : When multiple functions need to be distinguished
    • traffic_control:*=* : Corresponds to traffic_control=*
      • traffic_control:*=only :
      • traffic_control:others=* : Used as traffic_control:others=no to show completeness.
  • callsign=* (Countries may use their own other than standard ones, and they can perform different functions)
  • icao=* : Allowed to be added to the ACC

(TBD: Indicate airport served by remote towers)

Examples

Even when they are in the same site, if they have separate names or callsigns, it is recommended they be added as separate points.

Rendering

Features/Pages affected

• Created
  • aeroway=traffic_control
  • traffic_control=*
• Modified
  • icao=*
  • service=aircraft_control : Is reserved for use with man_made=tower . (Personally tower:type=* is non-ideal style, and mixed. This proposal does not touch them.)
• Deprecated
  • aeroway=tower
  • aeroway=control_centre
  • aeroway=control_tower
  • aeroway=aircraft_control

External discussions

Comments

Please comment on the discussion page.