Drone Free Zone
- Diego Cesa de Meira (Unlicensed)
Description
Drone Free Zone or “No drone zones” are areas where it may be unsafe or illegal to fly your drone. Drone Free Zone includes:
• 5.6 km from airports and 1.9 km from heliports or aerodromes used by helicopters only
• Busy, populated areas
• National parks
• Border crossings
Special Flight Operations Certificate is required for flying drone for non-recreational use in order to fly near an aerodrome.
Originator
Transport Canada
Nav Canada
Use Cases
Source(s)
Description | Source | Format | Date | Update Frequency | Metadata | Cost | Link | Remarks |
|---|---|---|---|---|---|---|---|---|
Drone Free Zone (DFZ) | Transport Canada | CSV | Current | Bi-monthly | N/A | Free | EGIS Data Folder: DroneFreeZone_Airport.gdb.zip | -Use preprocessed GDB file as provided. |
Canada Designated Airspace (at and below 400') | Current | Bi-monthly | N/A | Free | EGIS Data Folder: DroneFreeZone_AirspaceBelow400Ft.gdb.zip | -Use preprocessed GDB file as provided. |
Remarks
DFZ is created using FME based on Transport Canada No-fly Zone regulations and standards.
DFZ dataset also includes restricted airspace at or below 400' extracted from the Canada Designated Airspace dataset.
EGIS Data Folder: \\ncras382\Application Source Files\EGIS\Smartmap Files\
Process for EGIS integration
Creating DFZ Model:
In FME, transform Airport Reference Point (ARP) in Canada Airport Database to point.
Create buffers for 3 categories of aerodromes using these parameters:
-Airport: 5.6 km radius
-Seaplane Base: 5.6km radius
-Heliport: 1.9 km radiusOutput to KML, SHP or GDB as required
Import into EGIS
TC Smart Maps:
Not all GIS applications can consume KML file directly due to its unique data structures such as networklinks, folders, models etc.
Please contact Lawrence Chong, Digital Services Directorate for TC Smart Maps KML dataset and format translation.
TC Smart Maps KML link: \tc.gc.ca\tcgis\GISData\Google Mashup\Aerodrome\DroneFreeZone\DroneFreeZone.kmz
Customization:
Schema transformation: As required
Denormalization: Not required
Value coding: Not required
Attribute renaming: As required to improve readability
Attribute removal: It is highly recommended as some fields are unnecessary, this will also reduce file size and improve performance
Geoenrichment: Feature symbolization is recommended to improve visualization.
Format translation: Not required
Language translation: French version not available
Update frequency: As identified