Heliport OLS and AZR
Description
Heliport Obstacle Limitation Surfaces (OLS) are conceptual (imaginary) surfaces associated with a heliport, which identify the lower limits of the aerodrome airspace above which objects become obstacles to aircraft operations.
OLS/AZR is also referred to the complex imaginary surface formed by combining all the individual surfaces as follows:
Outer horizontal surface;
Approach surface;
Transitional surface;
Helipad surface
Originator
Transport Canada
Use Cases
Source(s)
Description | Source | Format | Date | Update Frequency | Metadata | Cost | Link | Remarks |
---|---|---|---|---|---|---|---|---|
Heliport OLS | TC Smart Maps | KML | 2018 | On-going | N/A | Free | EGIS Data Folder: HeliportOLSAZR_ApproachSurface.gdb.zip | -Use preprocessed GDB file as provided. |
Remarks
OLS/AZR models are generated using advanced FME workflow based on Transport Canada TP 312 5th Edition Aerodrome Standards.
Heliport OLS model is only approximate and should be used for reference purposes only.
EGIS Data Folder: \\ncras382\Application Source Files\EGIS\Smartmap Files\
Process for EGIS integration
OLS Model Generation:
Obtain Heliport OLS Survey Plan from Heliport Operator or Civil Aviation Heliport Operation Manual.
Populate Heliport OLS Parameter Table with technical data including Approach Length, Divergence Angle and Slope, Transitional Length and Slope from survey plans.
Export OLS Survey Plans as image file format.
Digitize Approach Surface and Centreline, Landing Pad and Transition Surface in Google Earth from survey plans. Ensure each surface is uniquely labelled for use in the next step.
In FME, join the digitized OLS Surfaces from Step 4 with the Parameter Table to determine the corresponding values for Approach (Section 1&2) Length, Divergence and Slope; Transitional (Segment 1&2) Length and Slope.
Generate 3D Approach Surfaces and Transitional Surfaces polygons as per technical specification. Include Z values (height) for 3D extrusion.
Generate contours at 10m intervals for Approach Surfaces.
Output 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\OLS_Heliport\OLS-2D-Heli.kmz
Customization:
Schema transformation: As required
Denormalization: Not required
Value coding: Not required
Attribute renaming: As required to improve readability
Attribute removal: Not required
Geoenrichment: Feature symbolization and 3D extrusion is recommended to improve visualization
Format translation: Not required
Language translation: French version not available
Update frequency: As identified