Parameters for the request operations
All parameters are optional except parameter airport.
NB! All the parameters and its values are case-sensitive.
The semantics of each parameter are described in the table below.
| Parameter | Values | Description / Comments | For example |
|---|---|---|---|
| airport | Required max: 3-4 characters value, ex. OSL, BGO, TOS | The operating airport that considers the flight leg orientations. Formatting is given as IATA airport code and must written in uppercase letters. Parameter is required! | airport=OSL, airport=BGO, etc. |
| TimeFrom | Optional defaults to value: 1 if not set Max value: 96 | The number of hours before the current time for which data is wanted. | TimeFrom=1 |
| TimeTo | Optional defaults to value: 7 if not set Max value: 144 | The number of hours after the current time for which data is wanted. | TimeTo=7 |
| direction | Optional Accepted: A or D If not set: both flight-directions | If the parameter direction is set, then the Flights will be filtered by A=Arrivals or D=Departures. If parameter direction is not set then fetch all flight leg data for both orientations. | direction=A or direction=D |
| lastUpdate | Optional Accepted format: yyyy-MM-ddTHH:mm:ssZ ex: 2023-01-20T13:02:37Z | If set, then Flights that are updated after the given timestamp within the period of TimeFrom and TimeTo. Datetime has to be given in UTC/Z zone. Recommended for polling-applications looking for new updates to flights. | lastUpdate=2023-01-03T09:30:00Z |
| codeshare | Optional Accepted: Y | If set then codeshareinfo is added to flight. CodeshareInfo consists of codeshareAirlineDesignators, codeshareAirlineNames, codeshareFlightNumbers and codeshareOperationalSuffixs. | codeshare=Y |
| serviceType | Optional Accepted: E | Possibility to add helicopter flights with servicetype (“E”) parameter. If parameter omitted, schedule flights with servicetype ‘J’ (Schedule passenger) and ‘C’ (Charter passenger) are sent | serviceType=E |
Example where all there parameters are used:
Other useful links:
XML schema file.
The XML schema files for the LETIS based service is obtained from the URL:
Service field mapping (attributes)
The XMLFeed service response has the following required attributes mapped to their corresponding data model elements :
| Service term | ADD | ARDB column | Comment |
|---|---|---|---|
| flight_id | FlightId (Merk! formatert | flight_id | |
| dom_int | FlightDIIndicator | flight_di_indicator | |
| schedule_time | SIBT for ankomster, SOBT for avganger | sobt, sibt | |
| arr_dep | No term, calculated. | "A" - Arrival, "D" - Departure | |
| airport | ArrivalAirportIATA eller DepartureAirportIATA i motsatt ende. | arrival_airport_iata, departure_airport_iata | |
| via_airport | Ikke i datamodell, ikke tilgjengelig ifra RDB | flight_route_iata | |
| check_in | CheckInDeskCode | check_in_display_text | |
| gate | Gate | gate_data | |
| belt | BaggageClaimUnit | baggage_claim_unit | |
| airline | OperatingAirlineIata | operating_airline_iata | |
| status | NextInformationTime, AOBT, ATOT, EOBT, ETOT, ELDT | next_information_time, aobt, atot, eobt, etot, eldt | If status_code = ’’: status_time = ’’ If status_code = ’N’: status_time = ’NEXT_INFO’ If status_code = ’E’: status_time = ’EOBT / ETOT’ - for departures, ’ELDT’ - for arrivals If status_code = ’D’: status_time = ’OFF_BLOCK_TIME’ – for departures If status_code = ’A’: status_time = ’ELDT’ – for arrivals If status_code = ’C’: status_time = ’’ |
| delayed | NA. Avledes: Skal være Y/N | Is derived: calculated (ALDT, ELDT, SIBT) for arrival or (AOBT, ETOT, SOBT) for departure. | |
| est_time | ELDT or ETOT or EOBT. ELDT for Arrival, for departure If EOBT is set uses it, else ETOT | ||
| codeshareAirlineDesignators | NA | code_share | |
| codeshareAirlineNames | CodeshareAirlineIATA | code_share | |
| codeshareFlightNumbers | CodeshareFlightNumber | code_share | |
| codeshareOperationalSuffixs | NA | code_share |
Time specifications:
All times are listed in UTC format and are in the format ISO 8601 (Wikipedia: ISO 8601-format) [YYYY]-[MM]-[DD]T[hh]:[mm]:[ss]Z. Please make sure to adjust for our time zone and summer time as required.
Example: 2009-12-31T16:00:00 corresponds to 31. Descember 2009 17:00 o'clock local time in Norway (CET), while 2009-06-23T16:00:00 correcsponds to 23. June 2009 18:00 o'clock local time in Norway (Summertime).