/
National Airport Policy

National Airport Policy

Description

The federal government's National Airports Policy (NAP) provides a framework that clearly defines the federal government's role with airports. That role will be defined through two main levels of federal involvement in airports with scheduled passenger traffic: nationally-significant airports that will form a National Airports System (NAS) and regional/local airports.

  • Regional/Local Airports are airports that handle fewer than 200,000 travelers a year for three consecutive years unless they serve the national capital or provincial or territorial capitals

  • The National Airport System (NAS) includes airports in all national, provincial and territorial capitals, as well as airports with annual traffic of 200,000 passengers or more.

  • Airports are considered to be remote if air transportation is the only reliable year round mode of transportation available to the community it serves.

  • Small airports are federally-supported airports which have no regularly-scheduled air service. They serve local interests only, such as general aviation and recreational flying.

  • Arctic Airports are northern airports own and operated by federal government which the government is negotiating the transfer to the local government.

Originator

  1. Transport Canada

  2. TC Smart Maps

Use Cases

  1.  

Source(s)

Description

Source

Format

Date

Update Frequency

Metadata

Cost

Link

Remarks

Description

Source

Format

Date

Update Frequency

Metadata

Cost

Link

Remarks

National Airport Policy (NAP)

TC Website
TC Smart Maps

HTML

2018

Completed

N/A

Free

Regional Airport
Small Airport
Remote Airport
Arctic Airport
EGIS Data Folder: NationalAirportPolicy_Airport.gdb.zip

Copy/paste web page listing as CSV

Remarks

  1.  

Process for EGIS integration.

CSV File Transformation:

  1. Copy/paste Airport listing from TC website then save as an Excel spreadsheet.

  2. In FME, use the Feature Merger to join the CSV file with the current Canada Airport dataset using Airport name as primary key.

  3. Correct any records not joined to match Canada Airport dataset Airport Name if necessary.

  4. Additional fields to include from Canada Airport: Identifier, Region, Aerodrome Status, Critical Aircraft, Owner, Runways and CFS Charts.

  5. Transform the Lat/Long to point.

  6. Output to KML, SHP or GDB as required.

  7. Import into EGIS

TC Smart Maps:

  1. Not all GIS applications can consume KML file directly due to its unique data structures such as networklinks, folders, models etc.

  2. Please contact Lawrence Chong, Digital Services Directorate for TC Smart Maps KML dataset and format translation.

  3. TC Smart Maps KML link: \\tc.gc.ca\tcgis\GISData\Google Mashup\NationalAirportPolicy\NationalAirportPolicy.kmz

Customization:

  1. Schema transformation: Not required.

  2. Denormalization: Not required.

  3. Value coding: Not required.

  4. Attribute renaming: Not required.

  5. Attribute removal: No required.

  6. Geoenrichment: Feature symbolization by theme is recommended.

  7. Format translation: As required.

  8. Language translation: French version not available.

  9. Update frequency: Completed.