Versions Compared

Old Version 6

changes.mady.by.user Ole Nymoen

Saved on

compared with

New Version 16

changes.mady.by.user Ole Nymoen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Service Description



asrv.aero

Flight Data

Set

Submit Service v 2.0



Namespace: http://www.asrv.aero/webservices/2.0/FlightDataSetService/

NoteThe service description is a work in progress, and without version control, as long as this note is here.

FlightDataSubmitService


Table of Contents
excludeService Description|asrv.aero|Flight Data.*|Namespace.*|Previous.*

Previous versions

Document revisions

Date

Description

Author

2022-05-22First complete version of the documentation.

Ole Nymoen

2024-10-04SubmitRmsData has been added. 

Ole Nymoen 

2024-10-04AtmData has been changed. TouchAndGoData added.

Ole Nymoen 




Numbered Headings

Service facts

  • Name:

FlightDataSetServicepage
Children Display
  • Service is accessed using HTTPS POST
  • Service security: Decided by implementation

  • Standard return codes are described here:

Service

Introduction

Overview

This service description defines one service with a set of operations to

request

submit flight leg oriented data. All flight related data elements are defined by the ADD.

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:

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

FDSS is

meant to be

implemented as a REST service. Previous versions were SOAP based.

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.

to prioritize between data sources. The reason for a service provider to not support all elements might be business rules related to updating data

distribution

, that it doesn't

have

use the information, or that it wants

to provide

the information updated 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 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

Include Page
Service overview
Service overview

Service operations

Include Page
Service operations
Service operations

Data entities

Include Page
Data entities
Data entities

XSDs

Include Page
XSDs
XSDs