Aeronautical Data 2-Day WorkshopAeronautical Data 2-Day WorkshopModule: 3Module: 3

eTOD & Other AeroData: Data Quality Context eTOD & Other AeroData: Data Quality Context

2

ObjectivesUnderstanding of Annex 15…

eTOD Requirements; andRequirements for Related Aeronautical

Data Implications for Indonesia

Treatment of existing dataPlanning of future priorities &

programmes for eTOD and other aeronautical data

3

ISO 19000 General Requirements Audit and traceability Other metadata

Provenance Coverage Description Access status

Data Quality

Essential: Systems & Procedures*Procedures* to enable the State to satisfy these requirements For managing data within eTOD & Procedure Design

environment Particularly for supporting/enabling PBN and all RNAV flight

procedure designs For managing interchange of data with AIS/AIP – *particularly

until systems are integrated, or interfaced!

4

Annex 15 AreasAnnex 15 Areas

5

Annex 15 Areas 1 & 21. Within the area covered by a 10-km radius from the ARP,

terrain data shall be collected and recorded in accordance with the Area 2 numerical requirements.

2. In the area between 10 km and the TMA boundary or 45-km radius (whichever is smaller), data on terrain that penetrates the horizontal plane 120 m above the lowest runway elevation shall be collected and recorded in accordance with the Area 2 numerical requirements.

3. In the area between 10 km and the TMA boundary or 45-km radius (whichever is smaller), data on terrain that does not penetrate the horizontal plane 120 m above the lowest runway elevation shall be collected and recorded in accordance with the Area 1 numerical requirements.

4. In those portions of Area 2 where flight operations are prohibited due to very high terrain or other local restrictions and/or regulations, terrain data shall only be collected and recorded in accordance with the Area 1 numerical requirements.

Note.— Terrain data numerical requirements for Areas 1 and 2 are specified in Table A8-1.

6

Annex 15 AreasAnnex 15 Areas

7

Obstacle Data Collection – Areas 1 & 2

1. Obstacle data shall be collected and recorded in accordance with the Area 2 numerical requirements specified in Table A8-2:a) any obstacle that penetrates the conical surface whose origin is

at the edges of the 180-m wide rectangular area and at the nearest runway elevation measured along the runway centre line, extending at 1.2 per cent slope until it reaches 120 m above the lowest runway elevation of all operational runways at the aerodrome (1.2 per cent slope reaches 120 m at 10 km); in the remainder of Area 2 (between 10 km and the TMA boundary or 45-km radius, whichever is smaller), the horizontal surface 120 m above the lowest runway elevation; and

b) in those portions of Area 2 where flight operations are prohibited due to very high terrain or other local restrictions and/or regulations, obstacle data shall be collected and recorded in accordance with the Area 1 requirements.

2. Data on every obstacle within Area 1 whose height above the ground is 100 m or higher shall be collected and recorded in the database in accordance with the Area 1 numerical requirements specified in Table A8-2.

8

Terrain & Obstacle Data Collection – Area

3

Terrain & Obstacle Data Collection – Area

3

1. Data on terrain and obstacles that extend more than a half-metre (0.5 m) above the horizontal plane passing through the nearest point on the aerodrome/heliport movement area shall be collected and recorded.

2. Terrain and obstacle data in Area 3 shall be collected and recorded in accordance with numerical requirements specified in Table A8-1 and Table A8-2, respectively.

9

Terrain Data Collection Surface – Area 4

Only terrain data shall be collected and recorded in Area 4 in accordance with the numerical requirements specified in Table A8-1.

10

Annex 15 Classes of Data by Area Areas 1-4 Segmented by requirements for different

applications Procedure Design – TMA Enroute – Different Requirements (eg, LSALT) Area 4 – Precision Approach Cat II/III Area 3 – Surface Movement (including Taxiways)

11

Data Quality Requirements Audit & traceability – important aspects

Why? Allows you, as professionals, to judge what to do with the data Quality control and data improvement Security (eg, procedure integrity, restricted nature, etc) Corporate knowledge in humans (previously) vs systems

(increasingly necessary)

What’s required to support this capability? Metadata

Data Quality

12

• Data Quality Requirements

Metadata Data Quality

Example for Actual Data

Data Quality Name Status ReferenceVertical Resolution

Vertical Accuracy

Vertical Confidence Level

Vertical Unit (Capture)

Horizontal Resolution

Horizontal Accuracy

Horizontal Confidence Level

Horizontal Unit (Capture) Integrity

TerrainArea 1 - Required ICAO Terrain Area 1 Required Annex 15 1 30 90% Metre 3sec/90m 50 90% Second/Metre 0.001Area 2 - Required ICAO Terrain Area 2 Required Annex 15 0.1 3 90% Metre 1sec/30m 5 90% Second/Metre 0.00001Area 3 - Required ICAO Terrain Area 3 Required Annex 15 0.01 0.5 90% Metre 0.6sec/20m 0.5 90% Second/Metre 0.00001Area 4 - Required ICAO Terrain Area 4 Required Annex 15 0.1 1 90% Metre 0.3sec/9m 2.5 90% Second/Metre 0.00001

DEM 100m - Actual TW DEM 100m Estimate StratAir 0.1 1 90% Metre 100 1 80% Metre 0.001DEM 5m - Actual TW DEM 5m Estimate StratAir 0.001 1 90% Metre 5 1 80% Metre 0.00001SRTM 90m - Actual* NASA SRTM Actual NASA 1 ~7 90% Metre 3 ? 90% Arc Seconds ?

13

Data Quality

Requirements

Data Quality

Requirements

Metadata – Data Quality Terminology

Attribute Description Example Value

Resolution (Vertical and Horizontal)

The numerical resolution of the data – the number of decimal places provided in the data. This provides an indication of how much ‘rounding’ has been performed on the data.

This applies to values like coordinates and elevation data. For Horizontal Resolution related to DTMs, also see Post-Spacing below.

VertRes: x.xx (m)

HorizRes: x.xxx (m)

Accuracy (Vertical and Horizontal)

The estimated closeness of the data to the actual or real world measurement. Related to Confidence Level.

VertAcc: 7m

HorizAcc: 3m

Confidence Level (Vertical and Horizontal)

Statistical measure of the data provider's confidence in the overall accuracy of the data. For example, 90% confidence level means 10% could be reasonably expected to be outside the 7m accuracy level. 68% confidence is equal to 1 standard deviation 1SD or 1 sigma, also shown as 1σ ), 95.4% is 2SD, 99.7% is 3SD.

RNAV primary area is defined as 2σ sigma (or 95%).

VertConfid: 90% (within 7m)

HorizConfid: 95% (within 3m)

Integrity (Vertical and Horizontal)

Integrity is a measure of the number of faults (or corruptions) that could be expected to be tolerated in the data.

CRCs are applied to data to indicate that data is not corrupted from its original or intended value — particularly during data transfer operations (but also on an ongoing basis whilst stored and maintained in a system).

A CRC can be calculated for each feature record (eg, obstacle). A CRC Mask can be used to indicate which fields in the record the CRC is applied to..

One could also use a single CRC for an entire DEM tile.

If Required Integrity:: 0.001 (or 1x10-3 routine)

Then need 16-bit CRC

24-bit -> 10-5 (essential)

32-bit -> 10-8 (critical)

(ref Annex 14, ch2->App5, or Annex 15)

Post-Spacing (DTM Only)

The post-spacing is the measure of distance between each grid point in a DTM based on a regular horizontal grid, such as DEM or DTED data.

5M DEM: post-spacing = 5m, horizontal resolution = 5m.

100m DEM: post-spacing = 100m, horizontal resolution = 100m

14

Statistics !Statistics !Dark blue is less than one standard deviation from the mean. For the normal distribution, this accounts for 68.27 % of the set; while two standard deviations from the mean (medium and dark blue) account for 95.45%; three standard deviations (light, medium, and dark blue) account for 99.73%; and four standard deviations account for 99.994%. The two points of the curve which are one standard deviation from the mean are also the inflection points. Source: <http://en.wikipedia.org/wiki/Standard_deviation>

zσ percentage within CI percentage outside CI ratio outside CI

1σ 68.2689492% 31.7310508% 1 / 3.1514871

1.645σ 90% 10% 1 / 10

1.960σ 95% 5% 1 / 20

2σ 95.4499736% 4.5500264% 1 / 21.977894

2.576σ 99% 1% 1 / 100

3σ 99.7300204% 0.2699796% 1 / 370.398

3.2906σ 99.9% 0.1% 1 / 1000

4σ 99.993666% 0.006334% 1 / 15788

5σ 99.9999426697% 0.0000573303% 1 / 1744278

6σ 99.9999998027% 0.0000001973% 1 / 506800000

7σ 99.9999999997440% 0.0000000002560% 1 / 390600000000

15

Quality Management Types of Errors

Refer RTCA-DO276 5.4 Aeronautical Data Requirements Annex 4, accuracy and integrity, but also

resolution (all through the document) –

eg, Annex 4, 14.6(g) Aerodrome Ground Movement Chart – ICAO* NB: in this case it conflicts with Annex 14 & 15 requirements for same data

Example of RESOLUTION 1/100 second = approximately 0.3m or 1ft

Annex 14, App 5 Annex 15, App 7 Covered in our system since ~ 2002 Being updated to include newer and still

evolving requirements Annex 15 - Aeronautical Data Requirements:

applies to all aeronautical feature data, not just obstacles and terrain

16

Data Quality Requirements

Metadata Data Quality - Obstacles

ObstaclesArea 1 - Required ICAO Obstacle Area 1 Required Annex 15 1 30 90% Metre 1 50 90% Varies 0.001Area 2 - Required ICAO Obstacle Area 2 Required Annex 15 0.1 3 90% Metre 0.1 5 90% Varies 0.00001Area 3 - Required ICAO Obstacle Area 3 Required Annex 15 0.01 0.5 90% Metre 0.1 0.5 90% Varies 0.00001

CAA Obstacles TW CAA Obst 2008 Estimate StratAir 0.01 1 90% Metre 0.1 1 90% Varies 0.00001

17

Data Quality Requirements Metadata

Data Product Specification - Example

Data Product Specification Identification

Main Data Provider Description Scope Abstract

Data Capture Method

Default Format

Data Quality ID

Maintenance Frequency

Production Date

Geographic Description

Projection ID

Access Status

DTM 100m Terrain TW97 100m DEM ID 100m post spacing DEM data for whole of Taiwan (some minor exceptins). Derived from 5m post spacing DEM by sampling (every twenteth point) - therefore may miss local peaks. May need vertical buffer to correct for possibly missing peaks.

Medium density terrain elevation data set for for the whole of the island of Taiwan

100m DEM data for Taiwan Island based on TW97 TM projection

Derived from DEM 5m by sampling

Generic DEM GRD files, no HDR files

? As Required 2004 Coverage of Taiwain Island only

TW97 Transverse Mercator

Public

DTM 5m Data TW97 5m DEM Provider_ID 5mpost spacing DEM data captured via manual processing of aerial survey data.

Generally full coverage except that some tiles are not fully populated

5m DEM data for Taiwan Island basd on TW97 TM projection

Aerial Survey with manual processing

Generic DEM GRD files with HDR files

DQ_ID As Required 2004 Coverage of Taiwain Island only

TW97 Transverse Mercator

Restricted

18

Q&A & Discussion

Suggested discussion pointsApplying same principles to all

aeronautical data – throughout data lifecycle and system-wide

Treatment of existing dataPlanning of future priorities &

programmes for eTOD and other aeronautical data