Latvijas gaisa satiksme (LGS)
Latvian air navigation service provider
LGS Digital NOTAM Subscription and Request Service allows the service consumer to get aeronuatical information in accordance with the Digital NOTAM specification. The aeronautical information conforms to the event scenarios that are supported by Digital NOTAMsuch as runway closures. 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. This supports the integration of the latest information into an existing aeronautical information store in the various ATM systems.
Latvijas gaisa satiksme (LGS)
Latvian air navigation service provider
Air traffic management is defined by ICAO as the "dynamic, integrated management of air traffic and airspace including air traffic services, airspace management and air traffic flow management - safely, economically and efficiently - through the provision of facilities and seamless services in collaboration with all parties and involving airborne and ground-based functions". Stakeholders involved in air traffic management need aeronautical data concerning the establishment, condition or change in any aeronautical facility, service, procedure or hazard, the timely knowledge of which is essential for flight operations. This service satisfies this need by allowing clients to subscribe to event scenarios and to be notified when the aeronautical data described in the event scenario is affected. The aeronautical data can be used, e.g., in pre-flight information bulletins. It can also be used to improve decision making thus positively impacting the efficiency of their planning and flight executions, enabled through automatic data verification and graphical visualisation. The aeronautical data is also used in other systems such as those used for airspace reservations (ARES). A list of these is available in Appendix C. This service satisfies this need by offering the aeronautical data (in the form of event features) as regulated by ICAO Annex 15 - Aeronautical Information Services. The scope covers the event encodings outlined in the Digital NOTAM Specification.
IER 1 - Digital NOTAM Exchange (A3SG-IER-05) (A3SG-IER-05 Digital NOTAM Data Exchange - Aeronautical SWIM Services - SWIM Confluence (atlassian.net))
The service offers subscription and request capabilities to distribute aeronautical data based on event scenarios.
The system provides Publish-Subscribe functionality for service consumers to subscribe/unsubscribe to receive Digital NOTAMs using filtering criteria:- event scenario(s)- series- Digital NOTAM publisher(s)- event scenario provider(s)- aeronautical feature(s)-- aerodrome(s)-- airspace(s)
When new Digital NOTAM is generated, the system distributes the message containing Digital NOTAM in AIXM 5.1.1 format to subscribed service consumers according to the stored subscription filters.
The service consumer is able to request aeronautical information in the form of a Digital NOTAM through WFS GetFeature query.
To access and use SWIM service, consumers must: 1.Register as a client in the LGS SWIM Client Portal https://swim-ais.lgs.lv. 2. Accept the Terms and Conditions as part of the registration process. 3. Generate an API password via the portal, which will be used for authentication and authorization when requesting the service.
LGS Digital NOTAM Subscription and Request Service 1.0.0 consumers may use data in order to integrate it in data products or facilitate their operations. Reselling data is prohibited.
Customers can be negatively impacted when data usage is disproportionate and for extended periods. As protection mechanism, Digital NOTAM Subscription and Request Service will restrict excessive requests originated from the same client.
The authentication mechanism follows WS-Light binding principles. The server is authenticated using an X.509 certificate over TLS. Clients authenticate using either HTTP Basic authentication methods over HTTPS. This ensures secure communication and client identity verification.
In order to consume the LGS Aeronautical Information Request Service 1.0.0, the Data Consumer must have the appropriate user roles granted via the SWIM Client Portal. Access to specific service operations is determined by these roles and the associated permissions.
Response Time of Digital NOTAM Subscription and Request Service Subscription Interface is less or equal to 1 second. Response Time of Digital NOTAM Subscription and Request Service Request Interface is designed in function of the operation complexity.- Low Complexity filter criteria in an AIS Data Query, the average response time is less or equal to 4 seconds- Medium Complexity filter criteria in an AIS Data Query, the average response time is less or equal to 5 seconds- High Complexity filter criteria in an AIS Data Query, the average response time is less or equal to 6 seconds- Very High Complexity filter criteria in an AIS Data Query, the average response time is less or equal to 8 seconds- Low complexity query parameters:-- (Dynamic) Feature Filter--- Validity - validTime--- Identifier--- Interpretation-- Time slice Projection--- relevantTime--- Interpretation- Medium complexity query parameters:-- Any combination of Low complexity filter conditions and-- (Dynamic) Feature Filter--- By Feature time slice Simple Properties-- Time slice Projection--- By Feature time slice Simple Properties- High complexity query parameters:-- Any combination of filter conditions with:--- Low complexity--- Medium complexity and-- (Dynamic)Feature Filter--- By Feature time slice complex properties--- One Spatial Filter Condition-- Time slice Projection--- By Feature time slice complex properties- Very high complexity query parameters:-- Any combination of filter conditions with:--- Low complexity--- Medium complexity--- High complexity and-- (Dynamic)Feature Filter--- multiple Spatial Filter Condition
The service is designed to support at least 1 WFS request per second and at least 10 subscription request per second under normal operating conditions.
The availability of the service is at least 99,975%.
The unplanned unavailability of the services shall not exceed 30 minutes (RTO = 30 minutes). In case of incidents the service ensures that no data is lost (RPO = 15) followed by operational procedures to recover potential data losses.
The service ensures confidentiality by using SWIM Technical Infrastructure (TI) Yellow Profile bindings.
The service ensures integrity by using SWIM Technical Infrastructure (TI) Yellow Profile bindings. Data integrity is ensured by the mTLS (which is based on TLS v1.2).
AIS Data Maintenance
Aeronautical Information Service
Aeronautical Information Service Provider
Aeronautical Information Exchange Model
Advanced Message Queuing Protocol
Airspace Reservation
Air Traffic Management
Business to Business
Create, Read, Update, Delete
Factory Acceptance Testing
Filter Encoding Standard
Hypertext Transport Protocol
Secure HTTP
International Civil Aviation Organization
Interface Control Document
Information Exchange Requirements
Latvijas Gaisa Satiksme
Message Exchange Pattern
Mutual TLS
Notice To Air Missions
Open Geospatial Consortium
Representational State Transfer
Simple Authentication and Security Layer
Site Acceptance Testing
System Quality Testing
System-Wide Information Management
Technical Infrastructure
Transport Layer Security
Uniform Resource Locator
Web Feature Service
Web Feature Service - Temporality Extension
Web Service
Extensible Markup Language
The service shall expose the event scenarios found in Appendix B. These reflect the Digital NOTAM Specification.
The event scenarios use features that are in the Aeronautical Information Exchange Model (AIXM) 5.1.1 and the AIXM Event Extension.
The AIXMBasicMessage that is returned by the service shall contain an event feature and the related AIXM features and time slices.
The Digital NOTAM Subscription and Request Service Subscription Interface allows for the selection of event scenarios of interest based on these filtering criteria:- event scenario(s)- series- Digital NOTAM publisher(s)- event scenario provider(s)- aeronautical feature(s)-- aerodrome(s)-- airspace(s)The considerations given in the General Principles for the Digital NOTAM will help AISP organise the event scenarios.The Digital NOTAM Subscription and Request Service Request Interface shall support filtering based on the operators defined in the OGC Filter Encoding 2.0 Encoding Standard. The temporal extension (WFS-TE) shall be used to support advanced temporal filtering.
Temporal filters based on WFS-TE supporting the following temporality use cases: 3,4,6,7,8.
Service consumer is responsible for building correct subscription filters within subscription request messages. The system allows service consumer to create multiple subscription with same filter.
Not available to consumer.
The Digital NOTAM Subscription and Request Service provides two interfaces: (1) a REST-based WFS interface supporting spatial and temporal queries compliant with WFS and WFS-TE standards, returning AIXM 5.1.1 encoded data; and (2) a subscription-distribution interface combining RESTful subscription management and AMQP 1.0-based message distribution. Consumers create subscriptions via REST, receive AMQP queue details in response. Upon data changes, messages are generated and pushed to AMQP queues according to subscription filters. Consumers retrieve and acknowledge messages from their queues. The Data Consumer sends requests compliant with the OGC Web Feature Service (WFS) and WFS Temporality Extension (WFS-TE) standards to the REST-based WFS Service. The service processes spatial and temporal queries and responds with aeronautical information encoded in AIXM 5.1.1 format. Clients are expected to construct requests using supported operators as defined in the applicable standards.
Implementation of PUBLISH_SUBSCRIBE using AMQP 1.0 protocol uses technical messages to inform the service consumer about:- creation, update or deletion of subscription
The service provides error responses according to the OGC OWS ExceptionReport standard for the WFS interface. Clients can expect structured and consistent error reporting indicating the outcome of each WFS request. For the Subscription interface, the service returns standard HTTP status codes along with error messages in the response body to indicate issues such as invalid requests, unauthorized access, or subscription conflicts.
Allows the service consumer to select and subscribe to event scenarios of interest. It allows the service consumer to manage the subscriptions e.g. to pause a subscription, or to unsubscribe.
This operation allows a service consumer to subscribe to event scenarios of interest.
This operation allows a service consumer to unsubscribe from event scenarios of interest.
This operation allows a service consumer to pause the subscription for a particular topic subscription.
This operation allows a service consumer to resume a subscription that had been paused.
This operation allows a service consumer to obtain the list of subscriptions.
This operation allows a service consumer to obtain information on a specific subscription.
This operation allows a service consumer to request the list of topics (which represent type of data, i.e. SWIM services) available for subscription
This operation allows a service consumer to obtain information on a specific topic (filter criteria).
Endpoint is used to get the list of existing subscriptions.
Endpoint is used to get detailed information about an existing subscription.
Endpoint is used for creating a new subscription.
Endpoint is used for deleting an existing subscription.
Endpoint is used for suspending an existing subscription.
Endpoint is used for resuming an existing subscription.
In a SWIM-compliant implementation of the Publish-Subscribe message exchange pattern using the AMQP 1.0 protocol, the term 'topic' is used to define a service (i.e., type of data) that a future service consumer is allowed to subscribe to. The 'topics' endpoint is used to get a list of all topics.
Endpoint is used to get detailed information about a topic.
The web service is bound to the REST architectural style.
SWIM TI Yellow Profile specification
Allows the service provider to distributes Digital NOTAM Messages based on the event scenario that has triggered the need for the service consumer to be updated.
This operation allows the service provider to publish Digital NOTAM messages to service consumers based on their subscriptions. Implementation is handled through AMQP 1.0 protocol and the published message is distributed to service consumers through AMQP Queues.
Endpoint is AMQP 1.0 Queue in AMQP Message Broker. Each subscription is linked to one queue, and queue name is returned in subscription response. 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.Service consumer shall be able to connect to AMQP Message Broker.
amqps://swim-ais.lgs.lv/
The web service is bound to the AMQP 1.0 messaging protocol.
SWIM TI Yellow Profile specification
Allows the service consumer to request an AIXM Basic Message based on filters which are linked to the event feature.
The GetCapabilities operation generates a service metadata document describing a WFS service provided by a server.
The GetFeature operation returns a selection of features from a data store.
The REST service endpoint exposes the Web Feature Service (WFS) interface version 5.1.1 with AIXM 5.1.1 data format, implementing the WFS Temporality Extension (WFS-TE) standard.
The REST endpoint returns the service metadata document describing the WFS capabilities as defined by the OGC WFS standard.
EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile
SWIM TI Yellow Profile specification
The information scope offered by the service supports the requirements of the Digital NOTAM Specification.
This International Standard specifies the behaviour of a service that provides transactions on and access to geographic features in a manner independent of the underlying data store. It specifies discovery operations, query operations, locking operations, transaction operations and operations to manage stored parameterized query expressions.
The temporality extension has been developed in order to align the OGC WFS 2.0 and FES 2.0 standards with the AIXM 5.1.1 Temporality Concept. It allows retrieving data in AIXM 5.1.1 format via OGC WFS 2.0 requests.
Extensible Markup Language (XML) is a markup language and file format for storing, transmitting, and reconstructing arbitrary data. It defines a set of rules for encoding documents in a format that is both human-readable and machine-readable.