Versions Compared

Version Old Version 16 New Version 17
Changes made by

WILSON Scott

WILSON Scott

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


TitleChange ProposalJustificationStatusNotes
1Update definition

Update Definitions page to include the different types of data sets. This can be a note in the ICAO data set entry.

Panel

A data set outlined in ICAO Annex 15.

Note: The different forms of ICAO data sets are listed in ICAO Annex 15 5.3.1.1: 

a) AIP data set;
b) terrain data sets;
c) obstacle data sets;
d) aerodrome mapping data sets; and
e) instrument flight procedure data sets. 

The obstacle data set has different requirements from the others so needs to be defined on its own.OpenThe different metadata requirements can be found at Basic properties for obstacles.
2Change wording of DS-META-007 - Geographical extent of the data set on Metadata Requirements

Reword the requirement into two clauses:

Panel

Each ICAO obstacle data set shall be provided together with metadata giving the geographical extent of the data set.

Each ICAO data set, other than obstacle data sets, should be provided together with metadata giving the geographical extent of the data set.

The new wording will be reflected on Requirement 7_ Geographical extent of the data set. 

The tables on that page will be updated. In particular the Obligation / Condition row should become: 

Panel

Mandatory for obstacle data sets. Optional for other ICAO data sets. If provided the following is required:

  • GeographicDescription; and
  • GeographicBoundingBox or BoundingPolygon.

The obstacle data set makes "Area of coverage" mandatory.

The tidy up of the table will ensure it is inline with the requirement/recommendation.

Open
3

New requirement for obstacle data sets covering integrity.


Add definition to Definitions: 

Panel
Data integrity (assurance level). A degree of assurance that an aeronautical data and its value has not been lost or altered since the origination or authorized amendment. (ICAO Annex 15)

Add new requirement to Minimal Metadata Requirements:

Panel

Each ICAO obstacle data set shall be provided together with metadata giving the data integrity assurance level of the data set.

Add dedicated page with guidance.

Panel

tbd

Update Appendix B_ Complete Informative Example to reflect the guidance.

See Basic properties for obstacles.Open

Are the levels:

  1. critical
  2. essential
  3. routine?

What figure is expected in the metadata e.g.

  • a figure between 0.00 and 1.00 as per ED-119/DO-291?
  • or a reflection of the levels

See work are below for examples...



4Rename Requirement 7_ Geographical extent of the data set, etc.

The page name should be updated to e.g.  DS-META-007 - Geographical extent of the data set. 

This change should be applied to all the individual requirements pages.


The word "requirement" can be misleading. It is better simply to use the identifier.Open
5Update Appendix A_ Requirements Analysis to reflect final version of Annex 15 and PANS-AIMCheck the paragraph numbers used. Add the obstacle data set metadata requirements. Updated numbers should be reflected on Minimal Metadata Requirements as well.Mostly tidy up.Open
6Update trace for Requirement 7_ Geographical extent of the data set on the Metadata Requirements page.The requirement is traceable to PANS-AIM Table A6-2. Obstacle attributes for the obstacle data setsThe obstacle data set makes "Area of coverage" mandatory.Open
7Update guidance on

Requirement 3_ Validity of the data set

Update guidance to clarify what is meant by validity in this case. See comments on the page...
Open

...

Work area - notes to process

...