1. Service facts

• Name: FlightDataRequestService

• Operations: 

  • GetBasicFlightLegData 

  • GetBasicFlightDataOutbound
  • GetBasicFlightDataInbound
  • GetFlightLegData

• Service is accessed using HTTPS GET

• Service security: Decided by implementation

• Standard return codes are described here: Service Return Codes

2. Introduction

2.1. Overview

This service description defines one service with a set of operations to request flight leg 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 flight leg data for arriving or departing flights for display on docking systems (GetBasicFlightDataInbound, GetBasicFlightDataOutbound).
  • Get basic flight leg data to display in a mobile app to passengers (GetBasicFlightLegData).
  • Get detailed flight leg data display on an operational web page (GetFlightLegData).

All operations use the same set of parameters to select the relevant flight legs. See Standard parameters for the request operations for a description. The data return is specific for the operations.

While the return data definition for one operation stay the same, the data returned related to one flight leg 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.

Version 2.n of FDRS is meant to be implemented as a REST service. Previous versions were SOAP based.

2.2. Implementation considerations

Any implementation of this service MUST use the XSD files provided here: 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.

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

2.4. Intended readership

• • IT architects
  • Developers
  • Business architects
  • Interested parties in the aviation community

3. Service overview

4. Service operations

5. Data entities

6. XSDs