/
CADORS

CADORS

Description

Civil Aviation Daily Occurrence Report System (CADORS) is a Canadian national Air Traffic Services (ATS) safety data reporting system which collects information about operational occurrences within the Canadian National Civil Air Transportation System. It is used to assist the early identification of potential aviation hazards and system deficiencies.
CADORS reports are collected from a number of sources. It captures a wide scope of safety related events including:

  • ATC operating irregularities

  • Communication, navigation, surveillance, and other air traffic systems failures

  • Controlled airspace violations

  • etc.

Originator

  1. Transport Canada

Use Cases

Source(s)

Description

Source

Format

Date

Update Frequency

Metadata

Cost

Link

Remarks

Description

Source

Format

Date

Update Frequency

Metadata

Cost

Link

Remarks

CADORS

Transport Canada

CSV

Current

Daily

N/A

Free

Transport Canada
EGIS Data Folder: CADORS_pt.gdb.zip

Non-spatial data
Requires extensive geocoding process
email: CADORS-SCREAQ@tc.gc.ca

Remarks

  1. Incident locations can comprise of airports, distance with direction, places, airways intersections, fixes, navaids, lat/long in multiple formats etc.

  2. Gecoding requires interpreting and parsing incident location into something meaningful. It is complex and time consuming. Manual validation required to ensure completeness.

  3. Interpreted/interpolated position is only approximate.

Process for EGIS integration

Geocoding Incident Locations:

Step 1 - Download Data

  1. Query the CADORS data by defining the Date Range (keep everything as default), then select Search.

     

  2. Next, select Go to Download Page, click Select All in Occurrence Information (uncheck Event). Select Download.

  3. Repeat for each set of data in "Red".

     

Step 2 - Location Interpretation and Parsing

  1. In FME, import Occurrence Information CSV file. Categorize Occurrence Location by interpreting its content as follows:
    . Airport
    . NavAids
    . Fixes / Intersections
    . Airways
    . Latitude / Longitude
    . Flight Information Centre (FIC)
    . Airspace Zones / Regions
    . Populated Places
    . Geographical Names
    . Unknown

  2. Parse location information and store as new attribute.

  3. Verify and edit the output, repeat the process if necessary.

Step 3 - Geocoding

  1. In FME, fanout location categories and join with corresponding in-house Geocoding Database to extract Lat/Long values.

  2. Geocode Geographical Places using Google, Bing or ESRI Geocoding Services and extract Lat/Long values.

  3. Extract Lat/Long into separate strings.

  4. Resolve unknown locations.

  5. Output to CSV file.

CSV File:

  1. CSV can be integrated directly into ArcMap and ArcGIS.

  2. In FME, transform Lat/Long to point.

  3. Join all files downloaed using OccNo as primary key.

  4. Output to KML, SHP or GDB as required

  5. Import into EGIS

Display Optimization:

  1. Sampled/thinned data (generated using data sampling technique) are displayed at small scale. With scale transition, original data are displayed at large scale thus improve display performance reduce cluttering.

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 nslation.

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

Customization:

  1. Schema transformation: As required

  2. Denormalization: Not required

  3. Value coding: Not required

  4. Attribute renaming: As required to improve readability

  5. Attribute removal: It is highly recommended as some fields are unnecessary, this will also reduce file size and improve performance

  6. Geoenrichment: Feature symbolization is recommended to improve visualization
    -Symbolize by aggregating numbers of incidents grouped by Lat/Long to enhance visualization.
    -Symbolize by Incident Category/Group

  7. Format translation: Not required

  8. Language translation: French version available

  9. Update frequency: As identified