Page tree

Versions Compared

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

The different metadata requirements can be found at Basic properties for obstacles.

Discussed 16 July and no objections raised.

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 DS-META-007 - 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.

ImplementedDiscussed 16 July and no objections raised.
3Change the list of geographical elements to include.

The introduction on DS-META-007 - 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.ImplementedDiscussed 16 July. Proposal updated to reflect the outcomes.
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.

Implemented

Discussed 16 July. Proposal updated to reflect the outcomes.


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 DS-META-007 - 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.ImplementedDiscussed 16 July and no objections raised.
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.ImplementedDiscussed 16 July and no objections raised.
7Update trace for DS-META-007 - 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.ImplementedDiscussed 16 July and no objections raised.
8Update guidance on

Requirement 3_ Validity of the data set

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

Panel

The start of the validity of the data set is based on the "effective date" of its data. 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.

The validity of the data set is different from the date and time when the data set is provided but is not yet effective (Requirement 2_ Date and time when provided).

More information on baseline data and updates is available at Baseline data and updates [Work in progress] Data set variants.


ImplementedDiscussed 16 July. Proposal updated to reflect the outcomes.
9Change the order of the two examples on DS-META-003 - Validity of the data setChange the order of the examples as the "End date unknown" is the more usual case.
ImplementedImplemented without discussion as has no impact on anything else.
10Add DS-META-000 - How to Provide Metadata to Metadata Requirements listAdd DS-META-000 - How to Provide Metadata to the Metadata Requirements page as it is currently not listed there.We should not have a requirement that is not listed on the Metadata Requirements page.Implemented
11Add link to the obstacle requirements on the main page.

Implemented
12Integrate the obstacle data set requirements

The following pages were added:

changes were made to integrate the obstacle metadata to

content came from [for deletion] Obstacle metadata requirements

Bringing all of the metadata requirements into one place to make easier to manage and understandImplementedImplementation will be explained on 13 April 2021

...