Service Description



asrv.aero

Flight Data Request Service v 1.1



Namespace: http://www.asrv.aero/webservices/1.1/flightdatarequestservice


Document revisions 

Date

Description

Author

2021-02-05Spelling of "codeshare" in figures corrected.
2021-01-28

Added the following elements:

GateStatus has replaced GateAction.

2020-12-03

Minor documentation updates. In addition the following changes have been made:

2020-12-01Version 1.1 specific documentation established. FlightLegStatus and ASRT added.
2020-04-17 First complete version of the documentation
2020-04-01Version for final review.
2020-03-30Version 1.0 specific documentation established.


 


Table of content


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:

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.

The operations can retrieve the following types of data:

  • Arriving flights

  • Departing flights

  • Flight leg (departure and arrival)

Service operations

Data entities


XML Usage

WSDL and XSDs