ytryrtytr
Operations
teyrtytr
ytryrtytr
teyrtytr
REST Subscription Interface. This interface is one of the two implementation alternatives of the ArrivalSequenceInformationPublisher interface.
Create a new subscription resource
Remove a subscription from the portfolio.
Report a problem.
Endpoint to be provided by the actual Service Instance.
REST Subscription Interface. This interface is one of the two implementation alternatives of the ArrivalSequenceInformationPublisher interface.
Create a new subscription resource
Remove a subscription from the portfolio.
Report a problem.
Endpoint to be provided by the actual Service Instance.
REST Subscription Interface. This interface is one of the two implementation alternatives of the ArrivalSequenceInformationPublisher interface.
Create a new subscription resource
Endpoint dependent from the Service Instance
Provides tiles of meteorological gridded data in response to tailored API requests submitted by an end user. This data is provided under the remit of the International Civil Aviation Organisation (ICAO) and can be used to support activities related to aviation.
The Service provides meteorological forecasts as GRIB2 response payloads. Within each request, consumers can specify a single 'item' (parameter) either for one global 'tile' (the forecast for the selected parameter for the whole globe per timestep group), or for one of 8 pre-set regional 'tiles'.
The Service also provides end users the ability to request metadata about the meteorological forecast included in the forecasts, returning a response in .json format.
Synchronous: Transactions are synchronous.
TI Protocol Method: HTTP GET
Precondition: Consumers must be authenticated and authorised via the Met Office API Management (APIM) Developer portal.
Processing consideration: The service shall provide only the latest available data.
This endpoint is the root for the Gridded Data API service.
Querying this endpoint returns static metadata in JSON format with this information:
Querying this OpenAPI endpoint returns static metadata in JSON format with this information:
Querying this endpoint returns static metadata in JSON format providing information about the OGC conformance classes implemented by the Service.
This endpoint returns metadata in JSON format about each 'collection' (data set) available to be queried:
URL: https://gateway.api-management.metoffice.cloud/sadis-wafs-gridded-data/…/{collectionId}
Querying this end point returns metadata information in JSON format about one of these specific collections {collectionId}:
URL: https://gateway.api-management.metoffice.cloud/sadis-wafs-gridded-data/…{collectionId}/items
Querying this end point returns metadata information in JSON format listing the available items, each with an 'itemId' and its associated metadata, that can be requested from a specified collection {collectionId}.
The 'itemId' naming standard is described in section 4.1 of the SADIS API - User Guide.
URL: https://gateway.api-management.metoffice.cloud/sadis-wafs-gridded-data/…{collectionId}/items/{itemId}
Querying this end point with the 'itemId' within a specified collection {collectionId} returns forecast data and associated metadata for this parameter e.g. Temperature, Geopotential Height, Relative Humidity, etc.
The success response is a 302 redirect, which directs you to the GRIB2 file payload of the requested item. The item payload contains the forecast data for all pressure levels for the relevant forecast timesteps and parameter(s), as specified by the 'itemId'.
The 'itemId' naming standard is described in section 4.1 of the SADIS API - User Guide.
The Service Interface Binding is SWIM Yellow Profile Compliant, using WS Light enabling HTTP GET requests and associated responses.
The Service implementation conforms with IPV4_SECURE_UNICAST as part of SWIM Yellow Profile requirements.
Provides access to Meteorological observation bulletins and information about the operation of the API and the data available.
The Service provides aeronautical meteorological observations as IWXXM, TAC and .png response payloads.
The Service also provides end users the ability to request metadata about the meteorological observations, returning a response in .json format.
Synchronous: Transactions are synchronous.
TI Protocol Method: HTTP GET
Precondition: Consumers must be authenticated and authorised via the Met Office API Management (APIM) Developer portal.
Processing consideration: The service shall provide a range of observations (Time now - 5 minutes back to Time now - 36hrs).
Url: The landing page provides links to the API definition, the Conformance statements and the metadata about the feature data in this dataset.
Url: The OpenAPI spec for OPMET API
Url: Information about standards that this API conforms to.
List all requirements classes specified in a standard that the server conforms to
Url: List the available collections from the service
Url: List the available collections from the service
{collectionId} - Where {collectionId} could be one of:
Url: List the locations available for the collection, described a co-ordinates of a polygon (geo-spatial)
{collectionId}/locations -Where {collectionId} could be one of:
Url: Query end point for queries of collection {collectionId} defined by a {locationId}
Return data the for the location defined by locationId
.
{collectionId}/locations/{locationId}?datetime={time}/{duration} - Where {collectionId} could be:
tac_opmet_reports
iwxxm_opmet_reports
tac_advisory_reports
iwxxm_advisory_reports
graphical_reports
notices
Where {locationId} could be:
GLOBAL
EUR_NAT
NAM_CAR
SAM
AFI
MID
ASIA_PAC
Where {time} is in 5 minute steps for reports BUT notifications have to be set to either 15 or 45 mins past the hour between. Data can be requested for times between now (T0) and 36hrs ago (T-36). {time} is ordered as year-month-day-Time
Where {duration} is PT5M for all collections except notices which are PT30M
For example:10:30 UTC on 5 Jan 2024 for that last 5 minute timestep for reports is datetime=2024-01-05T10%3A30Z/PT5M
For example:10:15 UTC on 5 Jan 2024 for that last 30 minute timestep for notifications is datetime=2024-01-05T10%3A15Z/PT30M
The Service Interface Binding is SWIM Yellow Profile Compliant, using WS Light enabling HTTP GET requests and associated responses.
The Service implementation conforms with IPV4_SECURE_UNICAST as part of SWIM Yellow Profile requirements.
This request fetches exported AIXM 5.1 files, based on the defined parameter set.
Retrieves a specific download AIXM 5.1 XML file using a notifications process.The steps of the above-mentioned process are as follows: 1. When storing a new parameter set, the system automatically creates a "topic" within AIMSL per user who is specified as "Subscriber" for the download. 2. The specified user may subscribe to the appropriate topic and recurrently poll for new status of an active download job. For subscription, the generated aimsl:id from the previously created pull point must be used.3. The appropriate topic expression should be set as "sdd_download:<user_code_id>". 4. Once the system starts a regarding download job from the stored parameter set, every status change of the active download is notified to the topic. Possible values are QUEUED, PROCESSING, FINISHED, FAILED and CANCELLED. 5. When the status changes to FINISHED, the id of the created file is provided with the notification as the <downloadFileId>. It is needed to request the download result via WS operation downloadAixmMessageFile - see SDD XML Primer, section 2.3.2.2 "Download Operations".
For security reasons, the addresses will be communicated only to customers.
url:withheld
The web service is bound to the SOAP messaging protocol using Document style.
SWIM TI Yellow Profile specification
The Query Service for AIXM 5.1 is based on the Open Geospatial Consortium Web Feature Service Interface Standard (WFS).
The GetCapabilities operation generates a service metadata document describing a WFS service provided by a server.
The DescribeFeatureType operation returns a schema description of feature types offered by a WFS instance.
The GetPropertyValue operation allows the value of a feature property or part of the value of a complex feature property to be retrieved from the data store for a set of features identified using a query expression.
The GetFeature operation returns a selection of features from a data store. Ref WSDL & OGC
The ListStoredQueries operation lists the stored queries available at a server.
The DescribeStoredQueries operation provides detailed metadata about each stored query expression that a server offers.
The WSDL document defines the service-specific properties of a /sdd-wfs/wfs WFS implementation; it specifies available endpoints and alternative bindings.
url:withheld
A WFS-2.0 implementation includes alternative SOAP bindings for WFS interfaces.
SWIM TI Yellow Profile specification
The DescribeFeatureType operation returns a schema description of feature types offered by a WFS instance.
-
This operation allows the service provider to publish information to service consumers based on their subscriptions.
EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile
AMQP 1.0 is used to distribute messages as explained in: https://reference.swim.aero/technical-infrastructure/guidance-for-pub-s…
The interface groups the operations that allows querying metadata and retrieving files.
This operation allows a service consumer to request the subscription to a particular topic of the service.
This operation allows a service consumer to unsubscribe from a particular topic of the service.
This operation allows a service consumer to pause the publishing of messages for a particular topic subscription.
This operation allows a service consumer to resume a subscription that had been paused.
Note: Due to the stateless implementation of the API, this operation is performed in exactly the same way as the pause changing the subscription_status in the body of the message to âACTIVEâ.
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 available for subscription.
This operation allows a service consumer to obtain information on a specific topic.
EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile version 1.1
The service shall use the network bindings of the SWIM TIYP.