The Aeronautical Aerodrome Map Request Service provides a capability for on-request aeronautical aerodrome related geospatial data and charts through a SWIM-compliant interface. The service generates aeronautical aerodrome maps from current or next AIRAC cycle aerodrome mapping data available. The service encodes aeronautical aerodrome maps in a graphical format. The consumer of the service can specify in the aerodrome map request: the aerodrome map layers to be included, charts to be included, the geographical area of interest. Currently the service provides only Tallinn Airport (EETN) data. The provided aeronautical aerodrome map is used in visualization contexts as a backdrop map. Service users such as ANSP, airport operators, airline operators, and airspace users can use various service capabilities (e.g. Digital NOTAM overlay in ePIB applications). All data is sourced from EANS AIM database and encoded using AIXM 5.1, ensuring compliance with aeronautical information exchange standards.
Categorisation
SERVICE_DESCRIPTION
OPERATIONAL
- INFORMATION_MANAGEMENT
- AIR_TRAFFIC_SERVICE_PROVIDER
- AIRPORT_OPERATOR
- CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER
- CIVIL_AIRSPACE_USER
- MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER
- MILITARY_AIRSPACE_USER
- MILITARY_DEFENCE_CENTRE
- PROVIDER_OF_DATA_SERVICES
- AERONAUTICAL_INFORMATION_EXCHANGE
- SYNCHRONOUS_REQUEST_REPLY
Estonian FIR
Provider
Estonian Air Navigation Services
Estonian Air Navigation Services (EANS, Lennuliiklusteeninduse Aktsiaselts) is a next generation air navigation services provider, headquartered in Tallinn, Estonia. We are state-owned public limited company under the jurisdiction Ministry of Economic Affairs and Communication of Republic of Estonia.
- AERONAUTICAL_INFORMATION_SERVICE_PROVIDER
- AIR_TRAFFIC_SERVICE_PROVIDER
- CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER
EANS
- AIM Service Desk
- Registration form
-
EMAIL
General Information
Aeronautical Aerodrome Map Request Service provides access to the aeronautical data in graphic format stored in EANS AIM database. Aeronautical Aerodrome Map Request Service in Tallinn (EETT) FIR is provided by EANS AIM unit in accordance with EU Comission Implementing Regulation 373/2017, EU Comission Implementing Regulation 2021/116 - Common Project One, ICAO Annex 15, ICAO Doc 10066 and SESAR Deployment Program.
Civil Airspace users
Consume aerodrome map data in preparation for GAT flight operations.
Military Airspace users
Consume aerodrome map data in preparation for OAT flight operations.
Airport Operator
Provide efficient and safe airport management. Airport operator can use aerodrome map data for various airports operations, but they also act as a data originator for AISP (EANS) with aerodrome data.
Air Traffic Services
their main targets are to ensure safe and efficient ATC, safety compliance and flight information availability. In Tallinn FIR ATS is provided by ANSP (EANS) and is responsible for providing TWR, APP and ACC traffic control in Estonian Airspace.
Civil and Military Air Navigation service providers
Ensure safe and efficient ATM and seamless integration of en-route and airport operations.
Information Exchange Requirements
A3SG-IER-02 Aerodrome Mapping Data Exchange as follows: Allow airport operators to exchange aerodrome data to achieve high efficiency and safe ground operations.
A3SG-IER-03 Aerodrome Maps Exchange as follows: Allow civil and military Airspace users, ATS, civil and military ANSP-s and military defence centre to request aerodrome map data. This is achieved through the use of web-based API. Users can choose the aerodrome they have access to and choose which the aerodrome map layers and charts to be included.
-
https://swim-eurocontrol.atlassian.net/wiki/x/XgCUAw
Information Exchange Requirements
Aeronautical Aerodrome Maps and mapping data
Service offers high-quality, latest, trusted and regulated aeronautical aerodrome map data retrieval capability. Users can request service-level and dataset-level metadata describing available map layers, data formats, temporal validity and service operations. The service provides access to aeronautical geospatial layers and thematic charts, including docking and parking charts (APDC), landing chart, aerodrome chart (ADC) and obstacle chart. Charts can be rendered dynamically through WMS. Data is made available in GeoJSON for vector-based map features and GeoTiff for faster chart products. All aeronautical features are encoded in AIXM 5.1.
Request metadata about the service
User can request parameters for available layers.
Data about map layers has been shared.
Request aerodrome map layers
User can request all aerodrome map layers by feature type.
Requested layer has been received and stored in client database.
Request aerodrome map data
User can request all aerodrome data by feature type.
Requested information about aerodrome has been received and stored in client database.
Request charts
User can request all aerodrome-related charts (docking/parking chart (APDC), landing chart, aerodrome chart (ADC), obstacle chart) in GeoJSON/Geotiff format.
Requested charts have been received and stored in client database.
-
CapacityThe service shall achieve a quality of processing 25 200 requests per hour.
-
Response timeThe service shall achieve a quality 0.955 second delay for 95% of messages.
-
AvailabilityHigh Availability, 95%: Service disruption is minimal, support for cluster or multiple instances. Autoscaling: Ability to scale according to load. If one instance goes down, traffic is automatically redirected to another.
-
RecoverabilityRecovery is performed automatically or in a managed manner according to policy. Loss of configuration and authentication data is not allowed. Configuration and queue metadata are backed up regularly. API Gateway configuration is backed up automatically. In case of system failure, the service must be restored the next business day. In case of force major this may not be guaranteed.
-
ConfidentialityData confidentiality is ensured by the implemented security mechanisms: mTLS ensures mutual authentication between client and server (client and server certificates) and all connections are secured with TLS 1.2/1.3 encryption.
-
IntegrityData integrity is maintained, no messages or critical queries are lost.
-
Authentication and AuthorisationOnly authenticated users are authorised to use the service. The service shall ensure consumer authentication in accordance with the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of a X.509 certificate over mTLS and the use of a username/password (SASL). In order to use the service and have access to appropriate service functions and operations, the client must have user roles granted in service provider authentication system.
-
AccessIn order to be able to access and use the EANS Aeronautical Information Feature Request service, users need to become certified clients. The authentication to the service is performed as basic authentication: 1. Register as a service user via web-form (registration form will soon be accessible from our aim webpage), you will be provided with username and password 2.Authenticate with x.509 via mTLS. 3. Username and password will later be used for authentication and authorization for using the service. 4. By sending us a request for signing up as a client, you agree with our terms and conditions.
-
PolicyWhen signing up as a service user, we ask for your personal information: full name, organization name, organizational e-mail address, organizational mobile phone number. When you fill the contact form, you do so voluntarily. We only use the information provided by you for our own business purposes, such as providing access to the service.
-
Fair Usesoon to be published
-
AIM Service DeskTo report incidents about services in operation.
SELF_VALIDATION
Before allowed access to live API, the client must test that their API endpoint is compliant with service configurations. The verification process is performed in service provider test environment. Client must run validation checks to ensure proper functionality, security and data format compliance. Once the clients endpoint is confirmed as compliant, the live service full access is activated enabling seamless system integration.
For information about the achieved results, please approach the designated point of contact.
-
AIPAeronautical Information Publication
-
AIMAeronautical Information Management
-
AIRMAeronautical Information Reference Model
-
AIXMAeronautical Information Exchange Model
-
ATMAir Traffic Management
-
ATSAir Traffic Services
-
EANSEstonian Air Navigation Services
-
EUEuropean Union
-
GATGeneral Air Traffic
-
HTTPHypertext Transfer Protocol
-
ICAOInternational Civil Aviation Organization
-
IERInformation Exchange Requirement
-
OATOperational Air Traffic
-
OGCOpen Geospatial Consortium
-
SASLSimple Authentication Security Layer
-
SESARSingle European Sky ATM Research
-
SWIMSystem Wide Information Management
-
TITechnical Infrastructure
-
TLSTransport Layer Security
-
WFSWeb Feature Service
-
WFS-TEWeb Feature Service - Temporality Extension
-
WMSWeb Map Service
-
WSWeb Service
-
YPYellow Profile
-
OGC Filter Encoding 2.0 Encoding Standard
The Service implements OGC Filter Encoding 2.0 Encoding Standard with a set of comparison operators to facilitate the querying of geospatial features.
Service supports following operators: Logical operators: AND, OR, NOT.
Spatial operators: Within, DWithin, BBox, Intersects, Equals, Disjoint, Touches, Contains, Overlaps, Crosses, Beyond.
Value comparison operators: PropertyIsLike, PropertyIsNull, PropertyIsBetween, Property IsNil, PropertyIsEqualTo, PropertyIsNotEqualTo, PropertyIsLessThan, PropertyIsGreaterThan, PropertyIsLessThanOrEqualTo, PropertyIsGreaterThanOrEqualTo.
-
OGC Web Feature Service (WFS) Temporality Extension
The Service implements GC Filter Encoding 2.0 Encoding Standard for Temporal Extension. The service supports following operators: After, Before, Begins, BegunBy, TContains, During, TEquals, TOverlaps, Meets, OverlappedBy, Metby, EndedBy.
-
The service receives information from the data originators that have signed service level agreement with EANS. This includes: AIRPORT_OPERATOR and CIVIL_AVIATION_ADMINISTRATION. EANS aims at achieving the level of minimal to no modifications made when receiving information from data originators.
Aeronautical Aerodrome Map Request
The service offers Aeronautical Aerodrome Map data, map layers and charts. The service implements OGC Web MAP Service 1.3.0 and 1.1.1 Standard and Web Feature Service 1.0.0, 1.1.0 and 2.0 with parts of WFS-TE standard, specified explicitly for querying and retrieving geospatial data with temporal extensions like AIXM 5.1.1. For WMS client must first request the capabilities of the service to get information about available features and layers. WMS can be used to output images, style map rendering and good display, WFS can be used for geoJSON, GML and GIS software base.
True
The default feature version of the query responses is AIXMâ¯5.1. The service supports AIXM 5.1.1 features described in Aeronautical Information Request Service Information Definition Appendix B.
-
Normal behaviour
Service offers both WMS and WFS Geoserver capabilities. All data requests are processed through a single entry point API Gateway, providing unified access to both WMS and WFS endpoints. API GW validates the request and routes it to Geoserver , which processes and retrieves necessary data layers, renders maps or extracts feature sets and sends response back through the API GW. The service behavior is in accordance with the synchronous_request_reply message exchange patterns detailed in the Message Exchange Patterns: Identification Guidelines. Client must issue WMF GetCapabilities/GetMap or WFS GetFeature requests through the gateway and receives images (WMS) or structured geospatial data such as GML/GeoJSON (WFS) in return.
-
Error Handling
Incase of erroneous or invalid request , client will receive standardized error message with HTTP statuscode.
-
<p>When you sign up to use the service, your IP-address will be logged for analytics and behavioural purposes.</p>
-
Aeronautical Aerodrome Map Request Service Interface
The interface is used to group the operations offered by the OGC Web Map Service 1.3.0 Interface Standard.
PROVIDER_SIDESYNCHRONOUS_REQUEST_RESPONSE-
GetCapabilitiesgit
Returns XML metadata with information about the server e.g. parameters about the WMS and available layers.
Messages-
GetCapabilitiesRequestIN
-
CapabilitiesOUT
-
-
GetMapgit
Returns a map image considering width and height of the map, coordinate reference system, rendering style and image format.
Messages-
GetMapRequestIN
-
AeronauticalAerodromeMapOUT
-
-
GetFeatureInfogit
Retrieves data (geometry and values) for a pixel location
Messages-
GetFeatureInfoRequestIN
-
FeatureCollectionOUT
-
-
GetLegendGraphicgit
The GetLegendGraphic operation provides a mechanism for generating legend graphics as images, beyond the LegendURL reference of WMS Capabilities. It generates a legend based on the style defined on the server, or alternatively based on a user-supplied SLD.
Messages-
GetLegendGraphicRequestIN
-
LegendOUT
-
-
AIM API Geoserver WMShttps://aimapi.eans.ee/cadas-aimdb-geoserver/wms
-
SWIM_TI_YP_1_1_WS_LIGHT
The service Interface binding is compliant with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.
-
IPV4_Secure Unicast
The service shall use the network bindings of the SWIM TIYP IPv4 Secure Unicast.
-
Geoserver messages
GeoServer provides a RESTful interface and simple HTTP calls. The service follows a synchronous request–response message exchange pattern over HTTPS using HTTP GET and POST methods. Service metadata is accessible via standard GetCapabilities operations, while geospatial content is retrieved using GetMap, GetFeature, and related OGC-defined operations. In case of processing or validation errors, the service returns appropriate HTTP status codes and OGC-compliant XML exception reports (e.g. ServiceExceptionReport or ExceptionReport).
-
WMS output formats
WMS returns images in a number of possible formats. The list of output formats supported by a GeoServer instance can be found by a WMS GetCapabilities request.
-
-
Aeronautical Aerodrome Map Feature Request Service Interface
The interface implements WFS 2.0, WFS 1.1.0 and WFS 1.0.0 Standard and supports all WFS operations including Transaction.
PROVIDER_SIDESYNCHRONOUS_REQUEST_RESPONSE-
GetCapabilitiesgit
The GetCapabilities operation is a request to a WFS server for a list of the operations and services, or capabilities, supported by that server.
Messages-
GetCapabilties requestIN
-
CapabilitiesOUT
-
-
DescribeFeatureTypegit
DescribeFeatureType requests information about an individual feature type before requesting the actual data. Specifically, the operation will request a list of features and attributes for the given feature type, or list the feature types available.
Messages-
DescribeFeatureTypeRequestIN
-
FeatureTypesOUT
-
-
GetFeaturegit
The GetFeature operation returns a selection of features from the data source.
Messages-
GetFeatureRequestIN
-
FeaturesOUT
-
-
Transactiongit
The Transaction operation can create, modify, and delete features published by a WFS. Each transaction will consist of zero or more Insert, Update, and Delete elements, with each transaction element performed in order
Messages-
TransactionInsertIN
-
TransactionResultOUT
-
-
AIM API Geoserver WFShttps://aimapi.eans.ee/cadas-aimdb-geoserver/wfs
-
SWIM_TI_YP_1_1_WS_LIGHT
The service Interface binding is compliant with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile
-
IPV4_Secure Unicast
The service shall use the network bindings of the SWIM TIYP IPv4 Secure Unicast
-
Geoserver messages
GeoServer provides a RESTful interface and simple HTTP calls. The service follows a synchronous request–response message exchange pattern over HTTPS using HTTP GET and POST methods. Service metadata is accessible via standard GetCapabilities operations, while geospatial content is retrieved using GetMap, GetFeature, and related OGC-defined operations. In case of processing or validation errors, the service returns appropriate HTTP status codes and OGC-compliant XML exception reports (e.g. ServiceExceptionReport or ExceptionReport).
-
-
MACHINE_READABLE_SERVICE_DESCRIPTION
Interface WSDL
MACHINE_READABLE_SERVICE_DESCRIPTIONN/A -
Interface Control Document
The CADAS-AIMDB Interface Control Document (ICD) contains a description of all interfaces provided by CADAS-AIMDB for the exchange of information with external systems
SERVICE_SPECIFICATION21.6.1 -
Appendix A: References
Aeronautical Aerodrome Map Request Service - Service Definition - Aeronautical SWIM Services - SWIM Confluence (atlassian.net)
SERVICE_SPECIFICATION01.00.00Reference-
https://swim-eurocontrol.atlassian.net/wiki/x/sgGUAw
-
-
Appendix B: Information Definition for Aeronautical Aerodrome Map Request Service
Aeronautical Aerodrome Map Request Service - Service Definition - Aeronautical SWIM Services - SWIM Confluence (atlassian.net)
SERVICE_SPECIFICATION01.00.00Reference-
https://swim-eurocontrol.atlassian.net/wiki/x/sgGUAw
-
OGC Web Map Service
SERVICE_STANDARD
The service conforms with the standard as per Technical Constraints section of the current service description.
1.3.0
This International Standard specifies the behaviour of a service that produces spatially referenced maps dynamically from geographic information. It specifies operations to retrieve a description of the maps offered by a server to retrieve a map, and to query a server about features displayed on a map. This International Standard is applicable to pictorial renderings of maps in a graphical format.
-
https://portal.ogc.org/files/?artifact_id=14416
OGC Web Feature Service
SERVICE_STANDARD
The service conforms with the standard as per Technical Constraints section of the current service description.
2.0/1.1.0/1.0.0
This standard defines direct fine-grained access to geographic information at the feature and feature property level by specifying discovery, query, locking and transaction operations and operations to manage stored, parameterized query expressions. This standard covers 11 operations e.g. GetCapabilities (discovery operation).This Standard continues to be a reliable means to provide geospatial data to the web. However, the functional capabilities are now available in a more modern web API, OGC API – Features, and implementers are encouraged to use the newer Standard.
-
https://www.ogc.org/standards/wfs/
OGC Filter Encoding
SERVICE_STANDARD
The service conforms with the standard as per Technical Constraints section of the current service description.
2.0
This standard is a jointly developed OGC and ISO TC/211 International Standard that describes an XML and Key Value Pairs (KVP ) encoding of a system neutral syntax for expressing projections, selection and sorting clauses collectively called a query expression.
-
https://www.ogc.org/standards/filter/
Eurocontrol Specification for SWIM Service Description
EUROCONTROL_SPECIFICATION_FOR_SWIM_SERVICE_DESCRIPTION
The service conforms with the standard.
2.0
This specification contains requirements for service descriptions, describing information services, in the context of System Wide Information Management (SWIM).
-
https://www.eurocontrol.int/publication/eurocontrol-specification-swim-service-description-sd
Eurocontrol Specification for SWIM Technical Infrastucture (TI)Yellow Profile
EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE
The service conforms with the standard as per Technical Constraints section of the current service description.
2.0
This specification contains requirements for the implementation of technical infrastructure supporting information exchanges in System Wide Information Management (SWIM). It enables technical interoperability by specifying standardised technical interfaces (e.g. protocols) and the capabilities required to enable a reliable, secure and efficient exchange of information.
-
https://www.eurocontrol.int/publication/eurocontrol-spec-170-eurocontrol-specification-swim-technical-infrastructure-ti-yellow