Versions Compared

Version Old Version 24 New Version 25
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 obstacle data set makes "Area of coverage" mandatory.

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

Open
3Change the list of geographical elements to include.

The introduction on Requirement 7_ Geographical extent of the data set should become:


Panel

This requirement is fulfilled by including a geographic description (GeographicDescription) as a clear, textual description of the data set's geographical extent.

Tip
titleBest practice
The inclusion of a bounding box (GeographicBoundingBox) or a polygon (BoundingPolygon) is a good practice in the GIS world. They are useful for applications that represent the data graphically, to set the initial window size. They are also facilitate the evaluation of the geographical coverage of a data set without having to parse and decode the full data set.



The Obligation / Condition row in tables should become:

Panel

Mandatory for obstacle data sets. Optional for other ICAO data sets. If provided:

  • GeographicDescription is mandatory.
  • Either GeographicBoundingBox or BoundingPolygon is recommended.
Reflects decision to concentrate on the provision of GeographicalDescription but allow the provision of other elements if available.Open
4

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. The table will use lineage. Of note:

Implementing Instruction

When adding the lineage statement state whether critical, essential or routine data integrity level is assured.

Example encoding

Panel

<gmd:MD_Metadata>
...
<gmd:dataQualityInfo>
<gmd:DQ_DataQuality>
<gmd:scope>
<!-- gmd:level is required by ISO 19115 (2003). This should use the value "dataset". -->
<gmd:DQ_Scope>
<gmd:level>
<gmd:MD_ScopeCode codeList="https://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MD_ScopeCode" codeListValue="dataset">dataset</gmd:MD_ScopeCode>
</gmd:level>
</gmd:DQ_Scope>
</gmd:scope>
<gmd:lineage>
<gmd:LI_Lineage>
<gmd:statement>
<gco:CharacterString>The routine data integrity level is assured.</gco:CharacterString>
</gmd:statement>
</gmd:LI_Lineage>
</gmd:lineage>
</gmd:DQ_DataQuality>
</gmd:dataQualityInfo>
...
</gmd:MD_Metadata>

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 notes below. Decision was to use lineage and the levels (critical, essential, routine) to fulfill the requirement. Obstacle data is routine so that is used in the guidance.



5Rename 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
6Update 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
7Update 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
8Update guidance on

Requirement 3_ Validity of the data set

Update

Add guidance to clarify what is meant by validity in this case

. See comments on the page..

.

Panel

The start of the validity of the data set is based on "effective date" of its content. Although this is may be an AIRAC date, it can be any date. This is particularly true for obstacle data sets that do not need to follow AIRAC.

The end of the validity of the data set is based on the date and time when the first data ceases to have effect. In many cases this will be at an indeterminate time in the future.

It is important to note, that the validity of the data set is a different requirement from Requirement 2_ Date and time when provided that covers the publication of the data set before it comes into effect.

More information on baseline data and updates is available at Baseline data and updates.


Open
9Change the order of the two examples on Requirement 3_ Validity of the data setChange the order of the examples as the "End date unknown" is the more usual case.
Implemented
10Add Requirement 0_How to Provide Metadata to Metadata Requirements listAdd Requirement 0_How to Provide Metadata to Metadata Requirements list as it is currently not there.
Open

...