Until this note is removed the documentation is a work in progress, and revisions to the documentation will not be tracked. |
Date | Description | Author |
|---|---|---|
| yyyy-mm-dd | First complete version of the documentation |
Introduction
Overview
This service description defines one service with a set of operations to request flight oriented data. All flight related data elements are defined by the Airport Data Dictionary.
The service is primarily designed to meet the need of airport partners, but availability is the decision of the service provider.
There are a set of use cases that can be realized using the operations and data available, for example:
Get basic arrival and departure data for display on docking systems (GetBasicFlightDataInbound, GetBasicFlightDataOutbound).
Get turnaround data to enable third party A-CDM clients (GetTurnaroundData).
Get flight leg data to display in a mobile app to passengers (GetFlightLegData).
Get airport oriented data to display on the airports web pages (GetFlightDataInbound, GetFlightDataOutbound).
While the entity definitions stay the same, the data they contain related to one flight will change as time goes by. Initially only schedule data will be available. The data content should then steadily increase as the flight progresses, until it is as complete as the service provider can make it.
Implementation considerations
Any implementation of this service MUST use the WSDL and XSD files provided here: WSDL and XSDs
It is however up to the service provider which data elements to support, and how much data to return for requests spanning a long time period. To enable this most elements are optional. The reason for a service provider to not support all elements might be business rules related to data distribution, that it doesn't have the information, or that it wants to provide information in other (more restricted) ways.
Any service provider should make available documentation about the actual implementation, including:
the address of the service.
any limitations in the implementation.
recommended and allowed polling intervals.
Purpose of this service description
This service description has the following purpose:
Describe of service in enough detail for a service provider to implement it.
Describe the service so that a client (of this service) developer can use it.
Make available the WSDL and XSD files necessary to implement and use the service.
Make it possible for relevant people at airports, airlines, handlers and other aviation partners to understand the available functionality and then to decide if to implement/use it or not.
Intended readership
IT architects
Developers
Business architects
Interested parties in the aviation community
Service overview
The figure below shows the available operations on the FlightDataRequestService. The operations are described in detail in Service operations. All operations, apart from GetAlerts, have a basic and a full version. The "basic" version return a simplified data set and should be used where suitable to save processing power and bandwidth.
The operations can retrieve the following types of data:
Arriving flights
Departing flights
Turnarounds (arriving and departing flights connected)
Flight leg (departure and arrival)
Alerts
XML Usage