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.
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.
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.
The interface is used to receive the data via WFS.
Pleas see the WFS documentation for detailed information
https://docs.geoserver.org/latest/en/user/services/wfs/index.html
This is the connection between the service provider and the customer via WFS. You need to contact the DWD aviation customer service for getting the credentials to retreive the specific layer which is described in this sevice description.
The necessary layer name will be provided after contacting the DWD aviation customer service together with the credentials for requestung the data.
The user can specify the output format within the request.
The interface is used to receive the data via WFS.
Pleas see the WFS documentation for detailed information
https://docs.geoserver.org/latest/en/user/services/wfs/index.html
This is the connection between the service provider and the customer via WFS. You need to contact the DWD aviation customer service for getting the credentials to retreive the specific layer which is described in this sevice description.
The necessary layer name will be provided after contacting the DWD aviation customer service together with the credentials for requestung the data.
The user can specify the output format within the request.
The interface for the service is provide via HTTP API and it is described fully in Github: https://github.com/fmidev/smartmet-plugin-timeseries/wiki/Using-the-Tim…
The interface for the service is provided via HTTP API. Message exchange pattern is request-response type. Typically the user makes a request to the server and in response gets the time series file to a single desired point.
The service is available for consumption for operational usage at this endpoint. Note that the user must set the apikey into the url at place APIKEY and latitude longitude information at place XX,YY
The user interface of the service is provided as a time series download service via HTTP. Message exchange pattern is request-response type. Typically the user makes a request to the server and in response gets the time series file to a single desired point.
The interface for the service is provided as a GRIB2 download service via HTTP and it is described fully in Github: https://github.com/fmidev/smartmet-plugin-download/wiki/SmartMet-plugin…
The interface for the service is provided as a GRIB download service via HTTP. Message exchange pattern is request-response type. Typically the user makes a request to the server and in response gets a GRIB file.
The service is available for consumption for operational usage at this endpoint. Note that the user must set the apikey into the url at place APIKEY
The interface for the service is provided as a GRIB download service via HTTP. Message exchange pattern is request-response type. Typically the user makes a request to the server and in response gets a GRIB file.
The interface is used to receive the data via WFS.
Pleas see the WFS documentation for detailed information
https://docs.geoserver.org/latest/en/user/services/wfs/index.html
This is the connection between the service provider and the customer via WFS. You need to contact the DWD aviation customer service for getting the credentials to retreive the specific layer which is described in this sevice description.
The necessary layer name will be provided after contacting the DWD aviation customer service together with the credentials for requestung the data.
The user can specify the output format within the request.