Conventions
The following conventions are used:
...
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 | Name of providerHow 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 | 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. |
Trace to ICAO | Source: PANS-AIM Table A6-2. Obstacle attributes for the obstacle data sets Note: Although PANS-AIM requires this for obstacle datasets, it was recommended for adoption by the AIM community for all types of datasets. |
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 | Source: PANS-AIM Appendix 6 |