1. Dataset facts

• Name: AvinorFlightLegState

• Availability: Services and data push

• Security: Depends on availability option

• Content: Depends on client authorization. 

2. Introduction

2.1. Overview

This dataset represents the maximum information Avinor has available regarding a flight leg. The actual content depend on the information Avinor has received. For flight legs more than a few days into the future it will mostly be schedule data. As actual flight time nears, and as the flight leg progresses, it will be more and more data. 

The data elements actually available for a given client will depend on the client's authorization.

All data elements are defined by the Airport Data Dictionary.

The dataset is primarily designed to meet the need of airport partners.

2.2. Implementation considerations

If Avinor doesn't have the data element, or the client doesn't have the authorization to see it the element will be missing from the returned data. No empty elements will be provided. This applies for single data elements and entities.

2.3. Purpose of the dataset description

This dataset description has the following purpose:

• • • Make it possible for relevant people at airports, airlines, handlers and other aviation partners to understand the available data and then to decide if to use it or not.
    • Describe the dataset so that a developer can use it.
    • Make available the XSD files necessary.

2.4. Intended readership

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

3. Data entities

4. XSDs