Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Current »


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:

  • Obligations concerning data collection
  • Obligations concerning the verification of data collected
  • Obligations concerning the metadata to be provided
  • Other obligations
  • Obligations on the standards to be used for describing metadata

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.

Obligations for data collection

Identifier

Text

Source

4.2.1

Metadata shall be collected for aeronautical data processes and exchange points.

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

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.

ICAO Annex 15 – Sixteenth Edition

4.2.1

The metadata to be collected shall include, as a minimum:
a) the name of the organizations or entities performing any action of originating, transmitting or manipulating the data;
b) the action performed; and
c) the date and time the action was performed.

Note.— ISO Standard 19115 specifies requirements for geographic information metadata.

PANS-AIM – First Edition Draft

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.

PANS-AIM – First Edition Draft

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.
Note 1.— Appendix 1 contains aeronautical data attributes, metadata, and accuracy requirements.

PANS-AIM – First Edition Draft

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.
Note.— Detailed specifications concerning metadata are contained in the PANS-AIM (Doc 10066).

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.

ICAO Annex 15 – Sixteenth Edition

5.3.2.1

Each data set shall include the following minimum set of metadata:
a) the name of the organizations or entities providing the data set;
b) the date and time when the data set was provided;
c) validity of the data set; and
d) any limitations with regard to the use of the data set.

PANS-AIM – First Edition Draft

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.

ICAO Annex 15 – Sixteenth Edition

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).
Note 1.— ISO Standard 19131 outlines the specifications of geographic data products.
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.

PANS-AIM – First Edition Draft

5.3.1.4

The aeronautical information model used should:

c) include provisions for metadata as specified in 5.3.2; and

PANS-AIM – First Edition Draft

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.
Note.— This is intended to facilitate and support the use and exchange of digital data sets between data providers and data users.

PANS-AIM – First Edition Draft

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.

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

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:

  • 5.3.2.1 Recommendation.— An AIP data set should be provided covering the extent of information as provided in the AIP.
  • 6.2.1 Information concerning the following circumstances shall be distributed under the regulated system (AIRAC) <...>
  • 6.3.1.1 AIP shall be amended or reissued at such regular intervals as may be necessary to keep them up to date.
  • 6.3.3.1 Data sets shall be amended or reissued at such regular intervals as may be necessary to keep them up to date.
  • 6.3.3.5 Updates to AIP, AIP data sets and Instrument Flight Procedures data sets shall be synchronised.
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)




  • No labels