The Digital NOTAM Subscription and Request Service allows the service consumer to get dynamic aeronautical information in accordance with the Digital NOTAM specification. The aeronautical information conforms to the event scenarios that are supported by Digital NOTAM.
The service consumer may subscribe to the service, specifying the event scenarios of interest. It is also possible to send a direct request to the service to get the aeronautical information.
The information returned is in the form of an AIXM 5.1.1 message ensuring compliance with aeronautical information exchange standards.
The digitalization of CNOTAM is in a transition phase. Expected completion date 2026-06-19.
", "serviceIdentification": { "name": "EANS Digital NOTAM Request and Subscribe", "version": "1.0" }, "serviceProvider": { "name": "Estonian Air Navigation Services", "abbreviation": "EANS", "description": "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.
", "pointOfContact": [ { "name": "AIM Service Desk", "role": "To request information and access to the service", "contactInformation": [ { "type": "EMAIL", "address": "swim@eans.ee" } ] }, { "name": "Registration form", "role": "Registration", "contactInformation": [ { "type": "URL", "address": "https://forms.office.com/e/LCygPFFE4V" } ] } ], "type": [ "AERONAUTICAL_INFORMATION_SERVICE_PROVIDER", "AIR_TRAFFIC_SERVICE_PROVIDER", "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER" ] }, "serviceCategorisation": { "businessActivityType": [ "INFORMATION_MANAGEMENT" ], "intendedConsumer": [ "AERONAUTICAL_INFORMATION_SERVICE_PROVIDER", "AIR_TRAFFIC_SERVICE_PROVIDER", "AIRPORT_OPERATOR", "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER", "CIVIL_AIRSPACE_USER", "COMMUNICATION_NAVIGATION_AND_SURVEILLANCE_SERVICE_PROVIDER", "MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER", "MILITARY_AIRSPACE_USER", "MILITARY_DEFENCE_CENTRE", "PROVIDER_OF_DATA_SERVICES" ], "informationCategory": [ "AERONAUTICAL_INFORMATION_EXCHANGE" ], "applicationMessageExchangePattern": [ { "name": "SYNCHRONOUS_REQUEST_REPLY", "reference": { "url": "http://reference.swim.aero/information-services/service-categories/CodeApplicationMessageExchangePatternType#SYNCHRONOUS_REQUEST_REPLY" } }, { "name": "BROKERED_PUBLISH_SUBSCRIBE_WITH_PUSH_MECHANISM", "reference": { "url": "http://reference.swim.aero/information-services/service-categories/CodeApplicationMessageExchangePatternType#BROKERED_PUBLISH_SUBSCRIBE_WITH_PUSH_MECHANISM" } } ], "geospatialCategorisation": { "aerodrome": [ "EETN" ], "fir": [ "EETT" ], "countryCode": [ "EE" ], "description": "Estonian FIR" }, "lifeCycle": [ { "lifeCycleStage": "OPERATIONAL", "from": "2026-05-15" }, { "lifeCycleStage": "PROSPECTIVE", "from": "2026-01-01", "to": "2026-05-15" }, { "lifeCycleStage": "PROSPECTIVE", "from": "2025-12-18", "to": "2026-12-31" } ] }, "generalDescription": { "operationalEnvironment": { "operationalNeeds": [ { "name": "General Information", "description": "A Digital NOTAM is intended for automatic processing and interpretation. Using dedicated software, it can be formatted into textual and graphical formats for presentation to human operators.
" }, { "name": "Air Traffic Services", "description": "Digital NOTAMs are instantly accsessible to ATS staff, so they can have the latest changes for Air Traffic Control. In Tallinn FIR ATS is provided by ANSP (EANS) and is responsible for providing TWR, APP and ACC traffic control in Estonian Airspace and consume digitalNOTAMs for operational situational awareness purposes.
" }, { "name": "Civil and Military Airspace Users", "description": "Consumer of digitalNOTAM data in the context of pre-flight briefing.
" }, { "name": "Civil and Military Air Navigation Service Providers", "description": "Use digitalNOTAM data to support the provision of air traffic and flow management, CNS services, aeronautical information and SAR services
" }, { "name": "Military Defence Centre", "description": "DigitalNOTAMs enhance operational efficiency and enable defence centers to visualize Prohibited, Restricted and Danger areas for military air- and ground operations. Military defence centre also acts as data originator and provides AISP with airspace limitations information.
" }, { "name": "Airport Operator", "description": "DigitalNOTAMs enhance the ability for airport operators to directly provide data concerning airport events. They provide AISP with aerodrome dynamic data and consume digitalNOTAM data to safely guide flights on airport grounds.
" }, { "name": "Information Exchange Requirements", "description": "A3SG-IER-05 Digital NOTAM Data Exchange as follows:1)Allow civil and military Airspace users, ATS, civil and military ANSP-s to subscribe to digitalNOTAM service. This is achieved by using AMQP standardized messaging protocol which is meant for asynchronous message exchange between systems. Users can specify the digitalNOTAM events they want and receive latest dynamic data on it. 2) Allow airport operators and AISP to exchange dynamic aerodrome data to achieve high efficiency and safe ground operations. 3) Allow military defence center and Military and Civil ANSPs to exchange airspace limitation and reservation data for flexible airspace usage. 4) Allow all users to request digital Pre-Flight Information Bulletins. This is achieved through the use of web-based API.
" } ], "capabilities": [ { "name": "Aeronautical Features", "description": "Service offers high-quality, trusted and regulated digitalNOTAM request and event subscription capability in AIXM 5.1 format. Service offers following capabilities: 1)Direct Requests, users can request specific dynamic aeronautical information as a digitalPIB; 2) Subscription - users can subscribe and specify their event scenarios of interest.
" } ] }, "functionality": [ { "name": "Request digitalPIB", "description": "User retrieves data with all active (digitalNOTAM) events in selected time period.
", "realWorldEffect": "Information about selected effective digital events is received and stored in client database." }, { "name": "Receive AMQP flow", "description": "Subscribe to specific scenario data feed. Also possible to check all or multiple.
", "realWorldEffect": "Message is received and stored in client database." } ], "accessAndUseConditions": [ { "name": "Authentication and Authorisation", "type": "SECURITY_CONSTRAINT", "description": "Only 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.
" }, { "name": "Access", "type": "LEGAL_CONSTRAINT", "description": "In 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 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.
" }, { "name": "Policy", "type": "SERVICE_POLICY", "description": "When 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.
" }, { "name": "Fair Use", "type": "SERVICE_CONSUMPTION_CONSTRAINT", "description": "soon be published
" } ], "qualitiesOfService": { "performance": [ { "name": "Capacity", "description": "The service shall achieve a quality of processing 25 200 requests per hour.
" }, { "name": "Response time", "description": "The service shall achieve a quality 0.955 second delay for 95% of messages.
" } ], "reliability": [ { "name": "Availability", "description": "High 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.
" }, { "name": "Recoverability", "description": "Recovery 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.
" } ], "security": [ { "name": "Confidentiality", "description": "Data 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.
" }, { "name": "Integrity", "description": "Data integrity is maintained, no messages or critical queries are lost.
" } ] }, "dateInOperation": "2026-05-15", "serviceSupport": [ { "name": "AIM Service Desk", "role": "To report incidents about services in operation.", "contactInformation": [ { "type": "EMAIL", "address": "swim@eans.ee" } ] } ], "validation": [ { "type": "SELF_VALIDATION", "description": { "validationSteps": "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.", "validationResults": "For information about the achieved results, please approach the designated point of contact." } } ], "abbreviations": [ { "name": "AIP", "description": "Aeronautical Information Publication
\r\n" }, { "name": "AIM", "description": "Aeronautical Information Management
\r\n" }, { "name": "AIRM", "description": "Aeronautical Information Reference Model
\r\n" }, { "name": "AIRM", "description": "Aeronautical Information Exchange Model
\r\n" }, { "name": "API", "description": "Application Programming Interface
\r\n" }, { "name": "ATM", "description": "Air Traffic Management
\r\n" }, { "name": "ATS", "description": "Air Traffic Services
\r\n" }, { "name": "EANS", "description": "Estonian Air Navigation Services
\r\n" }, { "name": "EU", "description": "European Union
\r\n" }, { "name": "FIR", "description": "Flight Information Region
\r\n" }, { "name": "GAT", "description": "General Air Traffic
\r\n" }, { "name": "HTTP", "description": "Hypertext Transfer Protocol
\r\n" }, { "name": "ICAO", "description": "International Civil Aviation Organization
\r\n" }, { "name": "IER", "description": "Information Exchange Requirement
\r\n" }, { "name": "IPv", "description": "Internet Protocol version
\r\n" }, { "name": "mTLS", "description": "Mutual Transport Layer Security
\r\n" }, { "name": "NOTAM", "description": "NOtice To AirMen
\r\n" }, { "name": "OAT", "description": "Operational Air Traffic
\r\n" }, { "name": "OGC", "description": "Open Geospatial Consortium
\r\n" }, { "name": "PIB", "description": "Preflight Information Bulletin
\r\n" }, { "name": "SASL", "description": "Simple Authentication Security Layer
\r\n" }, { "name": "SESAR", "description": "Single European Sky ATM Research
\r\n" }, { "name": "SWIM", "description": "System Wide Information Management
\r\n" }, { "name": "TI", "description": "Technical Infrastructure
\r\n" }, { "name": "TLS", "description": "Transport Layer Security
\r\n" }, { "name": "WFS", "description": "Web Feature Service
\r\n" }, { "name": "WFS-TE", "description": "Web Feature Service - Temporality Extension
\r\n" }, { "name": "WMS", "description": "Web Map Service
\r\n" }, { "name": "WS", "description": "Web Service
\r\n" }, { "name": "WSDL", "description": "Web Services Description Language
\r\n" }, { "name": "YP", "description": "Yellow Profile
\r\n" } ] }, "informationDescription": { "informationDefinition": { "reference": [ { "url": "https://aixm.aero/schema/5.1.1/AIXM_Features.xsd" }, { "url": "https://aixm.aero/schema/5.1.1/message/AIXM_BasicMessage.xsd" } ] }, "filtering": { "capability": [ { "name": "Event-based filtering for subscription service", "description": "When registering as a client for the subscription service, a registration form allows selecting following events to subscribe to: a) SAA.ACT, b) SAA.NEW, c) AD.CLS, d)AD.LIM, e)RWY.CLS, f)RWY.LIM, g)SFC.CON, h)OBS.NEW. For every scenario, there is also a possibility to subscribe to the full context event scenario. This means, that the filter reacts on BASELINEs of dnotam:Event time slices. The AIXM 5.1 data and digitalNOTAM are returned together with the referencing time slice, which contains the actual feature change (TEMPDELTA or PERMDELTA) and the underlying BASELINE of the feature change. This will allow clients to receive the full scope of the DNOTAM.
" }, { "name": "OGC Filter Encoding 2.0 Encoding Standard for DigitalPIB request service", "description": "Synchronous request/reply service for requesting digitalPIB uses OGC Filter Encoding 2.0 Encoding Standard Spatial Filters: Within, Dwithin, BBOX.
", "reference": { "url": "https://www.ogc.org/standards/filter/" } }, { "name": "OGC Web Feature Service (WFS) Temporality Extension for DigitalPIB request service", "description": "All Temporal operations use cases described in OGC Web Feature Service (WFS) Temporality Extension (Doc nr OGC 12-027r3) are supported.
", "reference": { "url": "https://portal.opengeospatial.org/files/?artifact_id=58922" } } ] }, "sourceOfInformation": "The service will receive information from the data originators that have signed service level agreement with EANS. This includes: AIRPORT_OPERATOR, CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER, MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER, COMMUNICATION_NAVIGATION_AND_SURVEILLANCE_SERVICE_PROVIDER, MILITARY_DEFENCE_CENTER, CIVIL_AVIATION_ADMINISTRATION and Government Agencies. EANS aims at achieving the level of minimal to no modifications made when receiving information from data originators." }, "technicalDescription": { "serviceMonitoring": { "monitoringDescription": "When you sign up to use the service, your IP-address will be logged for analytics and behavioural purposes.
\r\n" }, "behaviour": [ { "name": "Normal Behaviour for a client requesting digitalPIB", "description": "Users can request baseline data through OGC Web Feature Service 2.0. There is no automatic dataset publication, all data is available in the database and users can request digital NOTAM data in the form of a digital PIB.
Client sends a standard SOAP (envelope) request message via HTTP to the API Gateway and authenticates using mTLS and API Gateway validates the clients certification. API GW routes the request to the WFS server that is connected with AIM Database. An AIXM 5.1 data response is generated and the response message is embedded into a SOAP envelope just like the request.
The service behaviour shall be in accordance with the Synchronous Request-Reply pattern detailed in the Message Exchange Patterns: Identification Guidelines. The typical behaviour is as follows Synchronous Request/Reply- The request message is sent from the service consumer to the service - The service consumer remains blocked while awaiting the reply- The service remains blocked while processing the reply - The AIXM Basic Message, the reply message, is sent from the service to the service consumer.
" }, { "name": "Normal behaviour for digitalNOTAM AMQP push service using AMQP 1.0 or 0.9.1", "description": "The client registers to the service by filling a registration form. On the registration form, the client chooses the event scenarios (e.g. subscription channels) of interest. In the AMQP broker the client-subscription queue connection is established, to receive messages from an AMQP message queue. Clients can connect through an API Gateway and authenticate using mTLS and API Gateway validates the clients certification. After authentication, service consumers can access the AMQP delivery channel and receive data by connecting with appropriate credentials, that are made available after registration.
Only preconfigured event scenario based channels are available, no explicit subscribe/unsubscribe API is provided. Whenever new data is available (e.g. a new digitalNOTAM), messages are generated and pushed to AMQP message queues. Clients can only access their selected scenario queues.
The service behaviour is in accordance with the Asynchronous Request-Reply pattern detailed in the Message Exchange Patterns: Identification Guidelines. The typical behaviour is as follows: BROKERED_PUBLISH_SUBSCRIBE_WITH_PUSH_MECHANISM - A Publish/Subscribe pattern with push mechanism introducing a layer of decoupling between the publisher and subscribers by means of a broker.
" }, { "name": "Error Handling ", "description": "For digitalPIB request service: incase of HTTP request failure an XML FaultMessage shall be generated indicating that an error has occurred.
" } ] }, "references": { "serviceDocument": [ { "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION", "title": "Interface WSDL", "description": "Machine processable description of the service interface.
For specific WSDL description, please contact the POC.
", "version": "N/A", "reference": { "url": "https://schemas.xmlsoap.org/wsdl/" } }, { "documentType": "SERVICE_BEHAVIOUR_DESCRIPTION", "title": "Interface Control Document", "version": "2", "description": "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.
" }, { "documentType": "SERVICE_BEHAVIOUR_DESCRIPTION", "title": "Service Categories", "description": "A set of service categorisation schemes for use in artefacts that describe services.
", "version": "N/A", "reference": { "url": "https://reference.swim.aero/information-services/service-categories.html" } }, { "documentType": "SERVICE_SPECIFICATION", "title": "Appendix A: References", "description": "Digital NOTAM Subscription and Request Service - Service Definition - Aeronautical SWIM Services - SWIM Confluence (atlassian.net).
", "version": "01.00.00", "reference": { "url": "https://swim-eurocontrol.atlassian.net/wiki/x/qgGUAw" } }, { "documentType": "SERVICE_SPECIFICATION", "title": "Appendix B: Information Definition for Digital NOTAM Subscription and Request Service", "description": "Digital NOTAM Subscription and Request Service - Service Definition - Aeronautical SWIM Services - SWIM Confluence (atlassian.net).
", "version": "01.00.00", "reference": { "url": "https://swim-eurocontrol.atlassian.net/wiki/x/qgGUAw" } } ], "implementedStandard": [ { "title": "OGC Web Feature Service", "version": "2.0/1.1.0/1.0.0", "description": "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.
", "standardType": "SERVICE_STANDARD", "conformanceStatement": "The service conforms with the standard as per Technical Constraints section of the current service description.", "reference": { "url": "https://www.ogc.org/standards/wfs/" } }, { "title": "OGC Filter Encoding", "version": "2.0", "description": "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.
", "standardType": "SERVICE_STANDARD", "conformanceStatement": "The service conforms with the standard as per Technical Constraints section of the current service description.", "reference": { "url": "https://www.ogc.org/standards/filter/" } }, { "title": "Eurocontrol Specification for SWIM Service Description", "version": "2.0", "description": "This specification contains requirements for service descriptions, describing information services, in the context of System Wide Information Management (SWIM).
", "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_SERVICE_DESCRIPTION", "conformanceStatement": "The service conforms with the standard.", "reference": { "url": "https://www.eurocontrol.int/publication/eurocontrol-specification-swim-service-description-sd" } }, { "title": "Eurocontrol Specification for SWIM Technical Infrastucture (TI)Yellow Profile", "version": "2.0", "description": "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.
", "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE", "conformanceStatement": "The service conforms with the standard as per Technical Constraints section of the current service description.", "reference": { "url": "https://www.eurocontrol.int/publication/eurocontrol-spec-170-eurocontrol-specification-swim-technical-infrastructure-ti-yellow" } }, { "title": "OASIS Advanced Message Queuing Protocol (AMQP) ", "version": "1.0/0.9.1", "description": "The Advanced Message Queuing Protocol (AMQP) is an open internet protocol for business messaging. It defines a binary wire-level protocol that allows for the reliable exchange of business messages between two parties. AMQP has a layered architecture and the specification is organized as a set of parts that reflects that architecture.
", "standardType": "SERVICE_STANDARD", "conformanceStatement": "The service conforms with the standard as per Technical Constraints section of the current service description." }, { "title": "Digital NOTAM Specification", "version": "2.0", "description": "The Digital NOTAM Specification defines the rules for harmonised encoding of NOTAM information as digital AIXM data sets (version 5.1 or later).
", "standardType": "SERVICE_STANDARD", "conformanceStatement": "The service conforms with the standard as per Technical Constraints section of the current service description.", "reference": { "url": "https://ext.eurocontrol.int/aixm_confluence/display/DNOTAM/Digital+NOTAM+Specification" } } ] }, "serviceInterface": [ { "name": "Digital NOTAM Subscription and Request Service AMQP push service", "description": "The interface allows users access to digitalNOTAM event feed to receive any updates. Service uses OASIS Standard AMQP Version 1.0. and 0.9.1. After establishing a TLS connection the client sends a protocol header indicating whether it wants to use AMQP 1.0 or AMQP 0.9.1.
Endpoint is AMQP Queue in AMQP Message Broker. Each subscription is linked to one queue. The necessary details regarding AMQP credentials and queue is contained in the subscription confirmation. The consumer needs to establish a consumer-client confirmation to consume the data from that queue. Queue enables guaranteed messaging, that means message is kept in the queue until message consumer sends acknowledgment. Only then message is removed from the queue.
Http endpoint url will be provided after registering to become a client.
", "provisionSide": "PROVIDER_SIDE", "endpoints": [ { "name": "endpoint", "description": "Not provided yet", "url": "https://" } ], "operations": [ { "name": "Publish", "description": "This operation allows service provider to publish Digital NOTAM messages to AMQP broker queues.
", "messages": [ { "name": "AMQP Message", "direction": "OUT" } ] } ], "messages": [ { "name": "AMQP Message", "description": "The message is an output of the service, containing digitalNOTAM data.
", "isError": false, "schema": { "description": "The service follows ISO/IEC 19464 and OASIS AMQP 1.0 or 0.9.1 standard https://www.amqp.org/node/102
\r\n", "url": "https://www.amqp.org/node/102" } } ], "serviceInterfaceBinding": { "name": "SWIM_TI_YP_2_0_AMQP_MESSAGING", "description": "The service is bound to the AMQP 1.0 and 0.9.1 messaging protocol. The service Interface binding is compliant with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.
\r\n" }, "networkInterfaceBinding": { "name": "IPv4_Secure Unicast ", "description": "The service shall use the network bindings of the SWIM TIYP IPv4 Secure Unicast.
\r\n" }, "messageExchangePattern": "FIRE_AND_FORGET" }, { "name": "DigitalNOTAM Subscription and Request Service DigitalPIB Request", "description": "The interface is used to allow users to request digital PIB-s aka AIXM basic message based on spatial and temporal filters linked to the event feature. The service uses the OGC Web Feature Service 2.0 Interface Standard.
", "provisionSide": "PROVIDER_SIDE", "operations": [ { "name": "GetCapabilities", "description": "Returns XML metadata with information describing a WFS service provided by a server.
", "messages": [ { "name": "GetCapabilitiesRequest", "direction": "IN" }, { "name": "Capabilities", "direction": "OUT" } ] }, { "name": "GetFeature", "description": "The GetFeature operation allows the retrieval of features and time slices. The GetFeature request will result in a GetFeatureResponse answer containing a queryResult in the form of an XML file for every query defined in the request. The default feature version of the query responses is AIXM 5.1.
", "messages": [ { "name": "GetFeatureRequest", "direction": "IN" }, { "name": "GetFeatureResponse", "direction": "OUT" } ] } ], "messages": [ { "name": "Error status code", "description": "The WFS interface uses A Common Fault Message Schema. Any errors and fault messages that can occur are categorized into different fault-message-groups. To communicate such a message an object called FaultMessage is used on the SOAP-level and made up of the properties type, the errorMessageCode, maybe one or more errorMessageParameters and defaultErrorMessage.
", "isError": true, "schema": { "description": "\r\n\r\n
The service Interface binding is compliant with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile. The OGC Web Feature Service 2.0 Interface Standard is used and the mandatory standardised operations for a Basic WFS are implemented.
\r\n" }, "networkInterfaceBinding": { "name": "IPV4_Secure Unicast", "description": "The service uses the network bindings of the SWIM TIYP IPv4.
\r\n" }, "messageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE" } ] } }