...
ICAO Annex 15 Obligations
This section details the analysis of the metadata obligations of ICAO Annex 15. Analysis shows different concerns addressed by the obligations. These are:
...
The following tables group the obligations according to these concerns. Emphasis is added to make clear the issues to be addressed by the obligation. Note that some obligations are repeated as they apply to different concerns. Anchor
Obligations for data collection
Identifier | Text | Source |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="4f4a5a49-eaca-4fde-931b-af860d1bc931"><ac:plain-text-body><![CDATA[
4.2.1 | Metadata shall be collected for aeronautical data processes and exchange points. |
[1]
]]></ac:plain-text-body></ac:structured-macro>
ICAO Annex 15 – Sixteenth Edition | |
4.2.2 | Metadata collection shall be applied throughout the aeronautical information data chain, from origination to distribution to the next intended user. |
Note. — Detailed specifications concerning metadata are contained in the PANS-AIM (Doc 10066). |
[1]
]]></ac:plain-text-body></ac:structured-macro>
ICAO Annex 15 – Sixteenth Edition | |
1.2.3.2 | When a different temporal reference system is used for some applications, the feature catalogue, or the metadata associated with an application schema or a data set, as appropriate, shall include either a description of that system or a citation for a document that describes that temporal reference system. |
Note.— ISO Standard 19108*, Annex D, describes some aspects of calendars that may have to be considered in such a description. |
[1]
]]></ac:plain-text-body></ac:structured-macro>
ICAO Annex 15 – Sixteenth Edition |
4.2 |
The metadata to be collected shall include, as a minimum: |
|
[2]
PANS-AIM – First Edition | |
2.1.1.2 | A record of data originators should be maintained. |
Note.— Metadata requirements in Chapter 4 specify which information is to be recorded for each originator. |
[2]
]]></ac:plain-text-body></ac:structured-macro>
...
PANS-AIM – First Edition |
Obligations for verification of data collected
Identifier | Text | Source |
2.1.2.1 | Collected |
data shall be verified and validated for compliance with |
data quality requirements. |
|
[2]
]]></ac:plain-text-body></ac:structured-macro>
...
and quality requirements (accuracy, resolution and integrity). Note 4.— Guidance material on the management of aeronautical data quality is included in the Manual on the | PANS-AIM – First Edition |
Obligations for data provision
...
Identifier | Text | Source |
5.3.1.2 | Each data set shall be provided to the next intended user together with |
at least the minimum set of metadata that ensures |
traceability |
. |
|
[1]
]]></ac:plain-text-body></ac:structured-macro>
ICAO Annex 15 – Sixteenth Edition | |
1.2.3.2 | When a different temporal reference system is used for some applications, the feature catalogue, or the metadata associated with an application schema or a data set, as appropriate, shall include either a description of that system or a citation for a document that describes that temporal reference system. |
Note.— ISO Standard 19108*, Annex D, describes some aspects of calendars that may have to be considered in such a description. |
[1]
]]></ac:plain-text-body></ac:structured-macro>
ICAO Annex 15 – Sixteenth Edition |
5.3.2 |
Each data set shall include the following minimum set of metadata: |
d) any limitations with regard to the use of the data set. |
[2]
]]></ac:plain-text-body></ac:structured-macro>
...
Note.— ISO Standard 19115 specifies requirements for geographic information metadata. | PANS-AIM – First Edition |
Other obligations
...
Identifier | Text | Source |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="70f8760f-4f59-4ef4-a7bf-17d8304fceee"><ac:plain-text-body><![CDATA[
3.6.5 | Each quality management system shall include the necessary policies, processes and procedures, including those for the use of metadata, to ensure and verify that aeronautical data is traceable throughout the aeronautical information data chain so as to allow any data anomalies or errors detected in use to be identified by root cause, corrected and communicated to affected users. |
[1]
]]></ac:plain-text-body></ac:structured-macro>
ICAO Annex 15 – Sixteenth Edition | |
5.3.1.2 | A description of |
available digital data sets shall be provided in the form of data product specifications on which basis air navigation users will be able to evaluate the products and determine whether they fulfil the requirements for their intended use (application).
|
.— ISO Standard 19131 outlines the specifications |
for geographic data products. |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="0625bff1-eb0a-4d9e-a2fa-106c4f9332cb"><ac:plain-text-body><![CDATA[Note 2.—
This may include an overview, specification scope, data product identification, data content and structure, reference system, data quality, data capture, data maintenance, data portrayal, data product delivery, additional information |
and metadata. |
[2]
PANS-AIM – First Edition |
5.3.1. |
5 | The aeronautical information model used should: |
[2]
]]></ac:plain-text-body></ac:structured-macro>
...
… | PANS-AIM – First Edition |
Obligation on the standards to use
...
Identifier | Text | Source |
5.3.1.1 |
To facilitate and support the use of exchange of digital data sets between data providers and data users, the ISO 19100 series of standards for geographic information |
should be used as a reference framework. |
[2]
]]></ac:plain-text-body></ac:structured-macro>
...
Note.— Guidance material concerning the use of the ISO 19100 series of standards is contained in Doc 8126. | PANS-AIM – First Edition |
Other Metadata Requirements Analysis
This section lists a number of other requirements which were considered in addition to those found in Annex 15. They were collected from the AIM community.
...
Identifier | Text | Source |
---|---|---|
DP1 | In order to ensure data protection, the metadata exchanged should not allow for an individual to be identified. The preference is therefore to exchange organisation and role names. |
...
Wiki Markup \[Rule\] The start of validity of a data set shall be clearly indicated through metadata.
Wiki Markup \[Rule\] An AIP Data Set that included changes under the AIRAC system shall be clearly identified through the use of the acronym "AIRAC" in the metadata.
...
- Accuracy, resolution and integrity
...
Note: This was reflected in the implementing instructions for Requirement 1. | AIM community | |
IR1 | (Rule)The start of validity of a data set shall be clearly indicated through metadata. Note: This was captured in Requirement 3. | AIXM interoperability rules |
IR2 | (Rule) An AIP Data Set that includes changes under the AIRAC system shall be clearly identified through the use of the acronym "AIRAC" in the metadata. Note: This was captured in Requirement 4. Note: Justification for this requirement comes from various parts of ICAO Annex 15:
| AIXM interoperability rules and ICAO Annex 15 – Sixteenth Edition |
FR1 | The metadata should include statement on the accuracy, resolution and integrity of the data. Note: After analysis it was decided not to include requirements for the provision of the metadata with regards to the accuracy, resolution and integrity of the data. The measurement of these is part of the "verification of data collected" and is not metadata to be included at the dataset level. |
...
However, there is a requirement to provide the data integrity assurance level for ICAO obstacle datasets. | AIM community (taken from the PowerPoint which introduced the need for metadata) |