IPV4_UNICAST

All the reverse entity references for this entity
DataDistribution
HeartbeatDistribution
FlightPlanDataManagement
SectorSpecificDataManagement
CorrelationManagement
FlightBrightManagement
SectorisationManagement
SsrCodeManagement
RequestData
Vigiaero
Winter Weather Index for Aircrafts with the de‐icing systems over an area
WinterWeather Precipitation Type over an area interface
WinterWeather Precipitation Type to a Point interface
Winter Weather Index for Aircrafts with the de‐icing systems to a Point interface
Winter Weather Index for General Aviation and Helicopters over an area interface
Winter Weather Index for General Aviation and Helicopters to a Point interface
ArrivalSequenceInformationPublisherREST
SubscriptionManagement
SubscriptionManagement
Convection Forecast API
AUGUR RAIM Prediction Service
SubscriptionManagement
SubscriptionManagement
WeatherProfile API
Contrails Forecast API
MeasuresService
MeasuresService Publish/Subscribe
AIMsService
AIMsService Publish/Subscribe
FlightFilingService
FlightFilingService Publish/Subscribe
FlightManagementService
FlightManagementService Publish/Subscribe
FlightManagementService
FlightManagementService Publish/Subscribe
FlightManagementService
FlightManagementService Publish/Subscribe
FlightManagementService
FlightManagementService Publish/Subscribe
FlightFilingService
FlightFilingService Publish/Subscribe
FlightManagementService
FlightManagementService Publish/Subscribe
FlightFilingService
FlightFilingService Publish/Subscribe
FlightPreparationService
SimulationsService
FlightFilingService
FlightFilingService Publish/Subscribe
SimulationsService
FlightManagementService
FlightManagementService Publish/Subscribe
SimulationsService
FlightPreparationService
Winter Weather Nowcast for Aircraft De-Icing Needs over an area interface
WinterWeather Nowcast for Aircraft De-Icing Needs to a Point interface
Winter Weather Index for General Aviation and Helicopters to a Point interface

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…

Operations
Winter Weather Index for General Aviation and Helicopters to a Point

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.

Idempotent
NON_IDEMPOTENT
Synchronous
SYNCHRONOUS
TI Protocol Methods
HTTP GET
Operation Message
WinterWeatherIndexForGeneralAviationAndHelicoptersToPointRequest
Processing Consideration
Historic time values constraint
Behaviour
nominal behaviour
Interface Binding Description

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.

Interface Provision Side
PROVIDER_SIDE
TI Primitive Message Exchange Pattern
SYNCHRONOUS_REQUEST_RESPONSE
Service Interface Binding
SWIM_TI_YP_1_0_WS_LIGHT
Network Interface Binding
IPV4_UNICAST
Winter Weather Index for General Aviation and Helicopters over an area interface

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…

Operations
Winter Weather Index for General Aviation and Helicopters over an area

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.

Idempotent
NON_IDEMPOTENT
Synchronous
SYNCHRONOUS
TI Protocol Methods
HTTP GET
Operation Message
WinterWeatherIndexForGeneralAviationAndHelicoptersToAreaRequest
Processing Consideration
Historic time values constraint
Behaviour
nominal behaviour
Interface Binding Description

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.

Interface Provision Side
PROVIDER_SIDE
TI Primitive Message Exchange Pattern
SYNCHRONOUS_REQUEST_RESPONSE
Service Interface Binding
SWIM_TI_YP_1_0_WS_LIGHT
Network Interface Binding
IPV4_UNICAST
Winter Weather Index for Aircrafts with the de‐icing systems to a Point interface

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…

Operations
Winter Weather Index for Aircrafts with the de‐icing systems to a Point

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.

Idempotent
NON_IDEMPOTENT
Synchronous
SYNCHRONOUS
TI Protocol Methods
HTTP GET
Operation Message
WinterWeatherIndexForAircraftsWithTheDeIcingSystemsToPointRequest
Processing Consideration
Historic time values constraint
Behaviour
nominal behaviour
Interface Binding Description

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.

Interface Provision Side
PROVIDER_SIDE
TI Primitive Message Exchange Pattern
SYNCHRONOUS_REQUEST_RESPONSE
Service Interface Binding
SWIM_TI_YP_1_0_WS_LIGHT
Network Interface Binding
IPV4_UNICAST
WinterWeather Precipitation Type to a Point interface

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…

Operations
Precipitation Type Ensemble Forecast to a Point

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.

Idempotent
NON_IDEMPOTENT
Synchronous
SYNCHRONOUS
TI Protocol Methods
HTTP GET
Operation Message
PrecipitationTypeForecastToPointRequest
Processing Consideration
Historic time values constraint
Behaviour
nominal behaviour
Interface Binding Description

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.

Interface Provision Side
PROVIDER_SIDE
TI Primitive Message Exchange Pattern
SYNCHRONOUS_REQUEST_RESPONSE
Service Interface Binding
SWIM_TI_YP_1_0_WS_LIGHT
Network Interface Binding
IPV4_UNICAST
WinterWeather Precipitation Type over an area interface

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…

Operations
Behaviour
nominal behaviour
Interface Binding Description

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.

Interface Provision Side
PROVIDER_SIDE
TI Primitive Message Exchange Pattern
SYNCHRONOUS_REQUEST_RESPONSE
Service Interface Binding
SWIM_TI_YP_1_0_WS_LIGHT
Network Interface Binding
IPV4_UNICAST
Winter Weather Index for Aircrafts with the de‐icing systems over an area

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…

Operations
Winter Weather Index for Aircrafts with the de‐icing systems over an area

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.

Idempotent
NON_IDEMPOTENT
Synchronous
SYNCHRONOUS
TI Protocol Methods
HTTP GET
Operation Message
WinterWeatherIndexForAircraftsWithTheDeIcingSystemsAreaRequest
Processing Consideration
Historic time values constraint
Behaviour
nominal behaviour
Interface Binding Description

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.

Interface Provision Side
PROVIDER_SIDE
TI Primitive Message Exchange Pattern
SYNCHRONOUS_REQUEST_RESPONSE
Service Interface Binding
SWIM_TI_YP_1_0_WS_LIGHT
Network Interface Binding
IPV4_UNICAST
Vigiaero

The complete API description is available on MetSafe user portal accessible through a Token. 

Operations
Production

Main production endpoint.

{base_url_prod} is kept confidential for security reason.

Url

{base_url_prod}/expert/vigiaero/

Addressable Resource
Integration

Integration is for test purpose.

{base_url_int} is kept confidential for security reason.

Url

{base_url_int}/expert/vigiaero/

Addressable Resource
Behaviour
vigiaero
Interface Binding Description

Https Request Replay with token authentication

Interface Provision Side
PROVIDER_SIDE
Service Interface Binding
SWIM_TI_YP_1_0_WS_LIGHT
Network Interface Binding
IPV4_UNICAST
RequestData

The RequestData interface is used by the consumer to finally retrieve the data.

Operations
dataRetrieval

Make a WFS2.0 request to retrieve data.

Idempotent
IDEMPOTENT
Synchronous
ASYNCHRONOUS
Precondition
For making the request the user has to build the WFS request-link from baseUrl and relPath in the notification message. Furthermore the user needs credential for access.
TI Protocol Methods
http(s) get
Operation Message
requestDataWFS
Processing Consideration
processingWFS
GeoServerDWD

This is where the consumer finally requests the data.

Url

maps.dwd.de

Behaviour
requestWFS
Interface Binding Description

TI Yellow Profile (?)

Interface Provision Side
PROVIDER_SIDE
TI Primitive Message Exchange Pattern
SYNCHRONOUS_REQUEST_RESPONSE
Service Interface Binding
SWIM_TI_YP_1_0_WS_LIGHT
Network Interface Binding
IPV4_UNICAST
SsrCodeManagement

The SSR code management service allows a client to reserve an SSR code for manual assignment later on (i.e. manual assignment by using the Operation setSsr service call), and to clear such code from display in the whole OPS sector.An SSR code reserved for manual assignment is not available for automatic assignment. The SSR code will be reserved during a design parameter time and then released if not manually assigned to any flight plan or released according to the standard release rules if manually assigned to a flight plan during this design parameter time. When an input is made and successfully processed the response to the request is delivered in two parts: • Each input is first replied with the AcknowledgementMessage to indicate the acceptance or rejection of the request. The client is expected to start an internal timer in order to capture those cases where there would be no reply. In case of the latter, the client is expected to trigger a new input. • Secondly, provided the input was accepted, the updated information (as delivered by the SsrCode Distribution service) is sent. As such, subscription to the SsrCode distribution service is mandatory prior the user requesting modifications.

Operations
No_Operation

No operation defined

Idempotent
NON_IDEMPOTENT
Synchronous
ASYNCHRONOUS
Behaviour
service behaviour
Interface Binding Description

AMQP 1.0 content-type header used to specify media type values

Interface Provision Side
PROVIDER_SIDE
TI Primitive Message Exchange Pattern
SYNCHRONOUS_REQUEST_RESPONSE
Service Interface Binding
SWIM_TI_YP_1_0_AMQP_MESSAGING
Network Interface Binding
IPV4_UNICAST
SectorisationManagement

The sectorisation management service provides any connecting client with the means to perform a re-sectorisation change. Two kind of requests can be made, being: • A request to verify a new sectorisation change (i.e. would the request once executed be valid for the server?), • A request to perform a sectorisation change. When an input is made and successfully processed the response to the request is delivered in two parts: • Each input is first replied with the AcknowledgementMessage to indicate the acceptance or rejection of the request. The client is expected to start an internal timer in order to capture those cases where there would be no reply. In case of the latter, the client is expected to trigger a new input. • Secondly, provided the input was accepted, the updated information (as delivered by the Sectorisation Distribution service) is sent. As such, subscription to the Sectorisation distribution service is mandatory prior the user requesting sectorisation modifications.

Operations
No_Operation

No operation defined

Idempotent
NON_IDEMPOTENT
Synchronous
ASYNCHRONOUS
Behaviour
service behaviour
Interface Binding Description

AMQP 1.0 content-type header used to specify media type values

Interface Provision Side
PROVIDER_SIDE
TI Primitive Message Exchange Pattern
SYNCHRONOUS_REQUEST_RESPONSE
Service Interface Binding
SWIM_TI_YP_1_0_AMQP_MESSAGING
Network Interface Binding
IPV4_UNICAST
Subscribe to IPV4_UNICAST