SYNCHRONOUS_REQUEST_RESPONSE

All the reverse entity references for this entity

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.

Operations

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.

Idempotent
IDEMPOTENT
Operation Message

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}:

  • egrr_wafs_windtempgeo_0p25
  • egrr_wafs_humidity_0p25
  • egrr_wafs_tropjet_0p25
  • egrr_wafs_windtempgeo_1p25
  • egrr_wafs_humidity_1p25
  • egrr_wafs_tropjet_1p25
  • egrr_wafshzds_blended_ice_0p25
  • egrr_wafshzds_blended_turb_0p25
  • egrr_wafshzds_blended_cb_0p25
  • kwbc_wafs_windtempgeo_0p25
  • kwbc_wafs_humidity_0p25
  • kwbc_wafs_tropjet_0p25
  • kwbc_wafs_windtempgeo_1p25
  • kwbc_wafs_humidity_1p25
  • kwbc_wafs_tropjet_1p25
  • kwbc_wafshzds_blended_ice_0p25
  • kwbc_wafshzds_blended_turb_0p25
  • kwbc_wafshzds_blended_cb_0p25
Resource Type
REST_RESOURCE

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.

Resource Type
REST_RESOURCE

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.

Resource Type
REST_RESOURCE

The Service Interface Binding is SWIM Yellow Profile Compliant, using WS Light enabling HTTP GET requests and associated responses.

  • The Service shall return a .json response for metadata requests:
    • OpenAPI:
      • / gets the EDR root data entrypoint
      • /api gets the EDR spec for exposed endpoints
    • /conformance gets the conformance data for the API
    • Collections data:
      • /collections gets the end point that contains information about all the collections available
      • /collections/{collectionId} gets the end point that contains information about an individual collection {collectionId}
    • Item data: /collections/{collectionId}/items gets the end point that contains information about items available in an individual collection {collectionId}
  • Request for meteorological forecast data shall return a response as a 302 URL redirect to the GRIB2 payload:
    • Item data: /collections/{collectionId}/items/{itemsId} gets the end point for forecast data contained in the {itemId} item from an individual collection {collectionId}

The Service implementation conforms with IPV4_SECURE_UNICAST as part of SWIM Yellow Profile requirements.

Interface Provision Side
TI Primitive Message Exchange Pattern

Provides access to Meteorological observation bulletins and information about the operation of the API and the data available.

Operations

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).

Idempotent
IDEMPOTENT
Operation Message

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 a 5 minute or 30 minute step between now (T0) and 36hrs ago (T-36). {time} is 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 is            datetime=2024-01-05T10%3A30Z/PT5M

 

Resource Type
REST_RESOURCE

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.

Interface Provision Side
TI Primitive Message Exchange Pattern

The interface is used to receive the data via WFS.

Operations

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.

Addressable Resource

The necessary layer name will be provided after contacting the DWD aviation customer service together with the credentials for requestung the data.

Behaviour
Interface Binding Description

The user can specify the output format within the request.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

The interface is used to receive the data via WFS.

Operations

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.

Addressable Resource

The necessary layer name will be provided after contacting the DWD aviation customer service together with the credentials for requestung the data.

Behaviour
Interface Binding Description

The user can specify the output format within the request.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

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
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
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

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

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.

Synchronous
SYNCHRONOUS
TI Protocol Methods
HTTP GET
Processing Consideration
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
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

The interface is used to receive the data via WFS.

Operations

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.

Addressable Resource

The necessary layer name will be provided after contacting the DWD aviation customer service together with the credentials for requestung the data.

Behaviour
Interface Binding Description

The user can specify the output format within the request.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

The AFTNCorrectionManagementProvider Service Interface manages the operations performed by the FDO to correct erroneous AFTN messages concerning in-coming flight plan that cannot be processed automatically by the system.
It covers the following cases:
- AFTN Modification messages: CHG, CNL, DLA, ARR, DEP (ICAO format), ICHG, ICNL, IDLA, IARR, IDEP, IACH (ADEXP format). In this case, it may be necessary to associate a FP to these messages to be able to correct them successfully.
- AFTN Creation messages: FPL (ICAO format), IFPL, IAPL (ADEXP format).

Operations

This operation allows the operator to correct the erroneous fields upon the reception of a CHG or ICHG message.
Whenever a change is made to the data contained in a Flight Plan message already sent to the ATSUs concerned with the flight, they must all be notified. It is particularly important to notify changes of Flight Level or Flight Rules, whether the change is made before departure or en-route. Such notification may be done by phone or ATS/DS when possible; otherwise it must be done by means of a modification message sent to AFTN.

The following CHG fields can be corrected through this operation:
CHG content: callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), totalEstimatedElapsedTime (F16b), otherInformation (F18), amendments of other ICAO fields (F22), alternativeDestinationAerodromeDesignator (F16c).
In CHG, F22 should only amend F7b/c, F8, F9, F10, F13b, F14, F15, F16, F18, F19.

The following ICHG fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD),
estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

This operation allows the operator to correct the erroneous fields upon the reception of an FPL or IFPL message.
The FPL message is the flight plan as filed with an ATS unit by the pilot or a designated representative, without any subsequent changes.
The following FPL fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), flightRules (F8a), flightType (F8b), numberOfAircraft (F9a), aircraftTypeICAOIdentifier (F9b), wakeTurbulenceCategory (F9c), NCAEquipment (F10a), surveillance equipment (F10b), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), enRouteCruiseSpeed (TAS or Mach) (F15a), requestedFlightLevel (F15b), icaoRoute (F15c), destinationAerodromeDesignator (F16a), totalEstimatedElapsedTime (F16b), alternativeDestinationAerodromeDesignator (F16c), otherInformation (F18), supplementaryInformation (F19).

The following IFPL fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP),
NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

This operation allows the operator to correct the erroneous fields upon the reception of an IAPL message (ICAO format message APL is not applicable CCS).

The following IAPL fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

This operation allows the operator to correct the erroneous fields in the SFPL upon the reception of an IACH message (ICAO format message ACH is not applicable CCS). It is the modification message type distributed by the IFPS upon receipt and successful processing of an FNM, MFS, and AFP for which a valid associated flight plan exists in the IFPS.

The following IACH fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

This operation allows the operator to correct the erroneous fields upon the reception of an ARR or IARR message. Where an Arrival message is required for an IFR/GAT flight or part thereof operating within the IFPZ, the appropriate air traffic services unit shall submit such to the IFPS for processing

The following ARR fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), destinationAerodromeDesignator and actualLandingTime (F17), date of flight in otherInformation (F18).

The following IARR fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), actualLandingTime (ATA), destinationAerodromeDesignator (ADARR)

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

This operation allows the operator to correct the erroneous fields upon the reception of an CNL or ICNL message. When a schedule flight or a flight for which a Flight Plan Message has been sent, is subsequently cancelled, the ATSU at the point where the flight is cancelled shall send a Cancellation Message.

The following CNL fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), otherInformation (F18).

The following ICNL fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE)

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

This operation allows the operator to correct the erroneous fields upon the reception of an DLA or IDLA message. When a scheduled flight, or a flight for which a FPL was despatched, has not left the loading apron within 30 minutes after the scheduled or estimated time of departure; or where there is reason to believe that such a flight will not be in a position to leave within the 30 minutes due to the late arrival of the aircraft on the previous sector or for any other reason.

The following DLA fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), otherInformation (F18).

The following IDLA fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

This operation allows the operator to correct the erroneous fields upon the reception of a DEP or IDEP message. Departure message shall be sent immediately after take-off in respect of all flights for which a Flight Plan Message has been sent.

The following DEP fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), otherInformation (F18).

The following IDEP fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR), actualTakeOffTime (ATD)

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Interface Binding Description

Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

This Service Interface encompasses the different operations performed by the ATCO and modifying the Flight Plan Data: tactical instructions and system inputs performed to modify the planed route.

Operations

Operation to process the modification of one or several SFPL fields.
The input shall contain the flight identifier, the originator and at least a field to modify.
The fields that can be modified through this operation are related to static SFPL information (information of the SFPL independent of the modifications triggered by tactical instructions) such as: callsign aircraftIdentification (F7a), departureAerodromeDesignator (F13a), destinationAerodromeDesignator (F16a), flightType (F8b), flightRules (F8a), numberOfAircraft (F9a), aircraftTypeICAOIdentifier (F9b), wakeTurbulenceCategory (F9c), NCAEquipment (F10a), surveillance equipment (F10b), equipment status (F81), estimatedOffBlockTime (F13b), requestedFlightLevel (F15b), icaoRoute, enRouteCruiseSpeed (TAS or Mach) (F15a), totalEstimatedElapsedTime (F16b), alternativeDestinationAerodromeDesignator (F16c), ssrCodeData, otherInformation (F18), supplementaryInformation (F19), sidDesignator, starDesignator..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

Allows the operator to make a segment regression.
It turns a controlled segment from live or pending status into monitored status
The system keeps the segment in monitored state until a notification or activation message is received.

The input shall contain the flight identifier, the segment identifier and optionally the segment entry time (estimated time over the segment entry point).
When filled, the segment entry time adjusts the time estimates over the trajectory points.

Caveat: The operation name (coming from SESAR) is misleading in CCS context..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Processing Consideration
Interface Binding Description

Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

This Service Interface encompasses the different operations performed by the ATCO and modifying the Flight Plan Data. These operations can be divided in two sets of operations: the tactical instructions and the system inputs performed to modify the planed route:
- ATC tactical Instructions: Holding, Heading, Speed, Cleared Flight Level (CFL),Rate Of climb/Descend (ROCD), Direct To and Cleared To,
- System inputs: entry FL (EFL), exit FL (XFL), enCruiseFL (ECL) and requested Flight Level (RFL).

Operations

Operation to process the input of a Cleared Flight Level given the flight identifier and the value of the level to be applied.
The input may contain applicationStart data that can be a route point, distance before/after a route point or after current position..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

Operation to process the input of a direct instruction given the flight identifier and the target point of the direct (not overflown point already belonging to the route).
The input may contain application data that can be a route point, distance before/after a route point or after current position..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

Operation to process the input of a heading clearance.
It allows to assign either:
- an absolute heading. To do this:
- routePointId should not be filled
- continueHeading should be either not filled or set to FALSE
- either assignedHeading or application end point shoud be filled. If filled, the application end point should be expressed in the geographical point type
- a relative heading. To do this:
- routePointId should not be filled
- continueHeading should be either not filled or set to FALSE
- directionOfTurn and assignedHeading shoud be filled
- a maintain order. To do this:
- routePointId should not be filled
- continueHeading should be set to TRUE
- a resume own navigation order. To do this, routePointId should be filled..

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer

Operation to process the modification of a route portion for a specified flight.
The input shall contain:
- the flight identifier,
- the new portion of route.
The input may contain either an application end point (routePoint not overflown used to rejoin the old route) or a new destination aerodrome.
The input may also contain application start data that can be a route point, distance after/before a route point, distance after current position.
.

Synchronous
SYNCHRONOUS
TI Protocol Methods
transfer
Behaviour
Interface Binding Description

Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding