Metadata Requirements
- WILSON Scott
- POROSNICU Eduard
- Wolfgang Scheucher
Conventions
The following conventions are used:
- 'shall'- indicates a requirement that must be implemented; and
- 'should' - indicates a requirement that is recommended to achieve the best possible implementation.
Each requirement is detailed in a table with the following structure.
Title | Title of the requirement, used as a short name for the requirement for mnemonic and readability purposes. |
Identifier | Unique identifier of the requirement. |
Requirement | Statement expressing the requirement. |
Notes | Additional notes to clarify the requirement. |
Trace to ICAO | Justification of the existence of the requirement by tracing to ICAO |
Title | How to provide metadata |
Identifier | DS-META-000 |
Requirement | The metadata to be provided together with the ICAO data set shall be included in the same file as the data. |
Notes | - |
Trace to ICAO | Not applicable. However, this requirement was requested by the AIM community. |
Title | Name of provider |
Identifier | DS-META-001 |
Requirement | Each ICAO data set shall be provided together with metadata giving the name of the organizations or entities providing the data set. |
Notes | Note: This is the minimum set of metadata that ensures data traceability from the end-user to the originator. The next intended user has a contact from which to request supplementary metadata which the AIS has collected and stored. |
Trace to ICAO | Each data set shall include the following minimum set of metadata: Source: PANS-AIM – First Edition, s5.3.2 |
Title | Date and time when provided |
Identifier | DS-META-002 |
Requirement | Each ICAO data set shall be provided together with metadata giving the date and time when the data set was provided. |
Notes | - |
Trace to ICAO | Each data set shall include the following minimum set of metadata: Source: PANS-AIM – First Edition, s5.3.2 |
Title | Validity of the data set |
Identifier | DS-META-003 |
Requirement | Each ICAO data set shall be provided together with metadata giving the validity of the data set. |
Notes | Note: ICAO Annex 15 does not define "validity". Therefore, this document defines it as the valid date range for the dataset. |
Trace to ICAO | Each data set shall include the following minimum set of metadata: Source: PANS-AIM – First Edition, s5.3.2 |
Title | Indication that this is an AIRAC update |
Identifier | DS-META-004 |
Requirement | Each ICAO data set shall be provided together with metadata that indicates when the data set has been updated according to the AIRAC System. |
Notes | Note: This requirement covers the need to identify an AIRAC change. |
Trace to ICAO | Each data set shall include the following minimum set of metadata: Source: PANS-AIM – First Edition, s5.3.2 |
Title | Limitations on use |
Identifier | DS-META-005 |
Requirement | Each ICAO data set shall be provided together with metadata giving any limitations with regard to the use of the data set. |
Notes | Note: This includes statements such as those concerning the fitness for use of the data set. |
Trace to ICAO | Each data set shall include the following minimum set of metadata: Source: PANS-AIM – First Edition, s5.3.2 |
Title | Temporal reference system |
Identifier | DS-META-006 |
Requirement | Each ICAO data set shall, conditionally, be provided together with metadata giving a description of the temporal reference system used in the data set or a citation for a document that describes that temporal reference system when a temporal reference system other than the Gregorian calendar and Coordinated Universal Time (UTC) is used. |
Notes | - |
Trace to ICAO | 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. Source: ICAO Annex 15 – Sixteenth Edition, s1.2.3.2 |
Title | Geographical extent of the data set |
Identifier | DS-META-007 |
Requirement | 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. |
Notes | Note: The geographical extent may be a country, a territory, a geographical bounding box or polygon. Note: Although PANS-AIM requires this for obstacle datasets, it was recommended for adoption by the AIM community for all types of datasets. |
Trace to ICAO | Table A6-2. Obstacle attributes - Area of coverage - Mandatory Source: PANS-AIM – First Edition, Appendix 6 |
Title | Data integrity assurance level |
Identifier | DS-META-008 |
Requirement | Each ICAO obstacle data set shall be provided together with metadata giving the data integrity assurance level of the data set. |
Notes | - |
| Trace to ICAO | Table A6-2. Obstacle attributes - Integrity - Mandatory Source: PANS-AIM – First Edition, Appendix 6 |
Title | Horizontal confidence level |
Identifier | DS-META-009 |
Requirement | Each ICAO obstacle data set shall be provided together with metadata giving the horizontal confidence level of the accuracy of the geographical locations in the data set. |
Notes | - |
Trace to ICAO | Table A6-2. Obstacle attributes - Horizontal confidence level - Mandatory Source: PANS-AIM – First Edition, Appendix 6 |
Title | Vertical confidence level |
Identifier | DS-META-010 |
Requirement | Each ICAO obstacle data set shall be provided together with metadata giving the vertical confidence level of the accuracy of the geographical locations in the data set. |
Notes | - |
Trace to ICAO | Table A6-2. Obstacle attributes - Vertical confidence level - Mandatory Source: PANS-AIM – First Edition, Appendix 6 |