This page concerns v2.0 of the Specification. This requirement is new in v2.0. |
|
The geographical extent of the information can be expressed in various ways. For example it may concern a single ICAO Region (see ICAO Regions). However, it is also possible that it covers a combination of FIRs, ICAO Regions and aerodromes. Furthermore it is possible that the information covers the entire world.
The use of the geographical bounding box raises special concerns.
Note: The geoJSON standardisation group is considering the support for different coordinate reference systems. However, at the moment it only supports the World Geodetic System 1984 (WGS 84) [WGS84] datum, with longitude and latitude units of decimal degrees.
Completeness | Check that: [ ] The service description includes information about the geographical coverage of the exchanged information service payload. |
The following example shows the content as a table.
geographical extent of information | aerodrome | EADD |
---|---|---|
geometry | 100.0, 0.0 |
The following example shows an extract of the content of a JSON file that conforms to the Service Metadata Schema. It shows the use of an aerodrome location indicator and is supplemented by a geometry.
"serviceCategorisation": { ... "geospatialCategorisation": { "aerodrome": ["EADD"], "geometry": { "type": "GeometryCollection", "geometries": [{ "type": "Point", "coordinates": [100.0, 0.0] } } } } |
The following example is where the information is worldwide.
"serviceCategorisation": { ... "geospatialCategorisation": { "description": "Worldwide." } } |
The following example is for an ICAO region using the value published at https://reference.swim.aero/information-services/service-categories/CodeICAORegionType.html#EUR.
"serviceCategorisation": { ... "geospatialCategorisation": { "region": ["EUR"] } } |
Complete examples are available at Example service description.