This endpoint will return a payload of Turbulence in Grib2 format that covers the entire Pan European domain. Note that the user must set the api key into the url at place Token
This endpoint will return a Grib2 payload of Turbulence severity for a pre-defined spatial sub set of the Pan European area.
The end user will replace (id) with the name of the sub set: uk-ireland-fab, fab-ec, dk-se-ne-fab, danube-fab, fab-ce, baltic-fab, blue-med-fab, sw-fab, manchester-tma, scotland-tma
This end point will return a payload of Turbulence Polygons in .geojson format. The requester will specify in their request which severity level they need (1,2 or 3). The payload file will contain polygons for every vertical level for that severity level in 1 file
End point to request and collect a compressed file of 2km resolution at 15 minute intervals (low resolution) 3D Radar for the entire Pan European domain in HDF5 format
This endpoint will return High resolution 1km Radar at 5 minute intervals in Grib2 format in feet. Note that the user must set the API key into the url at place Token. It is deemed a candidate service as the Grib2 output has not been fully quality assured by any parties outside the Met Office.
The necessary details regarding AMQP credentials and queue is contained in the subscription confirmation. The consumer needs to establish a consumer-client to consume the data from that queue.
The necessary details regarding AMQP credentials and queue is contained in the subscription confirmation. The consumer needs to establish a consumer-client to consume the data from that queue.
The ADT DNES is compliant to the Open Geospatial Consortium (OGC) Web Feature Service Temporality Extension (WFS-TE) specification, OGC 12-027r3 and the corresponding Web Feature Service (WFS) version 2.0.0 specification. For a machine- and human-readable interface description, please refer to the GetCapabilities.
Both HTTP GET requests with key-value pairs as query parameters and HTTP POST requests with XML encoding of the requests, following the provisions in the WFS specification are supported.
The necessary details regarding AMQP credentials and queue is contained in the subscription confirmation. The consumer needs to establish a consumer-client to consume the data from that queue.
The necessary details regarding AMQP credentials and queue is contained in the subscription confirmation. The consumer needs to establish a consumer-client to consume the data from that queue.
The Airspace Status interface enables External Users (service consumers) to retrieve activation data on the status of airspace in the ASM system in real time.
An activation refers to the specific state of an airspace structure at the current time and until a specified end time. The end time of an activation is subject to change, it may be shortened or extended.
This interface allows consumers to see in real time the status of the airspace managed by the ASM Support System. The activation data provided contains the information known by the ASM system including the start time of the current activation state and the expected end time. Within the ASM system, the actual end time may be changed during the tactical phase. The changes to the current activation state are communicated immediately. The current activation state can be supplemented with the planned airspace usage information available from the Booking Interface in section 2.4.6, thus allowing visibility of the latest planned upcoming activations and deactivations within the ASM system.
This interface is treated as safety critical when used via the publish-subscribe mechanism detailed in the Publication Interface section 2.4.3. Under such use it requires that the External User acknowledges receipt and understanding of the activation data allowing the ASM system to detect in cases that a change in status is not received and processed by the External User. In contrast to the other interfaces defined in this service, subscribing to activation data will cause the current activation state to be automatically fully published to the subscriber. This ensures the initial state is always transmitted to External Users subscribing to activation data and also ensures that the initial state is acknowledged.
Figure 32 in Section 2.4.10.1 provides an overview of the Airspace status interface.
Information Exchange Flow
Figure 33 in Section 2.4.10.3 depicts the Airspace status interface information exchange flow.
Interface Functions
The interface performs the following function:
- Requesting Activations - Allows access to the activation data held within the ASM Support System by External Users.
ASM-INTF-STAT-010: ASM Service shall be supported by the Airspace Status interface to manage the retrieval of activation data held within the ASM Support System by external users.
ASM-INTF-STAT-020: The AirspaceStatus interface shall support the following operation:
ASM-INTF-STAT-030: The queryActivationList operation shall receive and process the FilteredRequest message from an External User.
ASM-INTF-STAT-040: If the activation list request is valid, the queryActivationList operation shall transmit the matching activation data in the ActivationListReply message to the requesting External User.
ASM-INTF-STAT-050: If for any reason the request is not valid, the queryActivationList operation shall transmit an appropriate error in the ActivationListReply message to the requesting External User.
ASM-INTF-STAT-055: The queryActivationList operation shall accept any combination of the
following filters in the FilteredRequest message:
ActivityIDFilter
AirspaceIDFilter
ChangePeriodFilter
InterestedIntervalFilter
AndFilter
ASM-INTF-STAT-060: The External User shall only make use of data returned in an ActivationListReply for non-safety critical information purposes.
ASM-INTF-STAT-070: The External User shall make use of the AMQP service for safety-relevant purposes.
ASM-INTF-STAT-080: The External User should acknowledge receipt of any valid ActivationNotification published onto an AMQP queue, by publishing an AcknowledgementReceiptRequest message onto the AMQP queue referenced in the ActivationNotification message.
ASM-INTF-STAT-090: The ASM Support System shall select an appropriate value for Activation acknowledgement-time and ensure that this value is appropriately documented for use by service consumers.
Note: The definition of these messages can be found in section 2.7.3Interface Messages.