The service enables users to request aeronautical features stored in the EANS AIM database. These features, provided as structured digital objects, include airports and heliports, runways and landing areas, taxiways and aprons, airspace structures, navigation aids, flight procedures, waypoints, routes, and obstacles.
AIRM Conformant
False
AIRM Correspondence
True
Datatype
The default feature version of the query responses is AIXM 5.1. The service supports AIXM 5.1 features described in Aeronautical Information Request Service Information Definition Appendix B.
Definition
The service shall offer features defined in the Aeronautical Information Exchange Model (AIXM) 5.1.1.
The service implements core elements of the OGC WFS-TE (Web Feature Service – Temporal Extension) specification, which is designed to enable standardized querying and retrieval of geospatial features with temporal attributes, such as those defined in AIXM 5.1. Supported output formats vary by query type and are aligned with WFS-TE capabilities. Each request may explicitly define the desired output format (see query type descriptions below). The selected format influences the encoding, schema structure, and level of detail in the response payload, ensuring compliance with applicable OGC and AIXM standards. In general, following output formats are supported
1. text/xml; subtype=aixm. A well-formed and valid AIXM will be returned as text content of an XML element.
2. xml/aixm: The response contains the queried AIXM as XML content.
The service implements core elements of the OGC WFS-TE (Web Feature Service – Temporal Extension) specification, which is designed to enable standardized querying and retrieval of geospatial features with temporal attributes, such as those defined in AIXM 5.1. Supported output formats vary by query type and are aligned with WFS-TE capabilities. Each request may explicitly define the desired output format (see query type descriptions below). The selected format influences the encoding, schema structure, and level of detail in the response payload, ensuring compliance with applicable OGC and AIXM standards. In general, following output formats are supported
1. text/xml; subtype=aixm. A well-formed and valid AIXM will be returned as text content of an XML element.
2. xml/aixm: The response contains the queried AIXM as XML content.