...
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 |
] |
4.2.2 | Metadata collection shall be applied throughout the aeronautical information data chain, from origination to distribution to the next intended user. | [1] |
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. | [1 |
] |
4.2.1 | The metadata to be collected shall include, as a minimum: | [2] |
]]></ac:plain-text-body></ac:structured-macro>
2.1.1.2 | A record of data originators should be maintained. | [2] |
...
...
Obligations for verification of data collected
Identifier | Text | Source |
2.1.2.1 | Collected data shall be verified and validated for compliance with completeness, format, timeliness, traceability and data quality requirements. | [2 |
] |
...
Obligations for data provision
Identifier | Text | Source |
5.3.1.2 | Each data set shall be provided to the next intended user together with a minimum set of metadata that ensures data traceability from the end-user to the originator. | [1] |
]]></ac:plain-text-body></ac:structured-macro>
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. | [1 |
] |
5.3.2.1 | Each data set shall include the following minimum set of metadata: | [2] |
]]></ac:plain-text-body></ac:structured-macro>
...
...
Other obligations
Identifier | Text | Source |
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>
5.3.1.2 | A description of the 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). | [2] |
]]></ac:plain-text-body></ac:structured-macro>
5.3.1.4 | The aeronautical information model used should: | [2 |
] |
...
Obligation on the standards to use
Identifier | Text | Source |
5.3.1.1 | The ISO 19100 series of standards for geographic information shall be used as a reference framework. | [2] |
]]></ac:plain-text-body></ac:structured-macro>
...
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.
- Data protection – The metadata exchanged should not allow for an individual to be identified. The preference is therefore to exchange organisation and role names.
- There are proposed interoperability rules:
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.
- Some further requirements (taken from the PowerPoint which introduced the need for metadata):
- Accuracy, resolution and integrity
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. Anchor