IataPtmData
| The figure shows the elements and structure of an Airport Data Dictionary (ADD) based entity representing an IATA Passenger Transfer Message (PTM) as defined in the Passenger Services Conference Resolutions Manual (PSCRM) RP 1718. |
| Entity / ADD element | Comments |
|---|---|
| IataPtmData | Identifies the flight leg passengers transfer from and to other light legs. The transfers will be on the arrival airport. |
For IATA messages with multiple "parts". If part '1' comes again all transfer data previously received for this flight leg should be discarded, as it will be resent. | |
IATA based identifier for this flight, usually issued long before the flight actually takes place. FlightId is normally the concatenation of OperatingAirlineIATA, FlightNumber and OperationalSuffix. FlightId typically identifies a flight to the majority of systems, but it is not unique across time. It's unique only in conjunction with FlightDepartureDate. Exception: Some airlines use their ICAO code (OperatingAirlineICAO) instead of OperatingAirlineIATA. This might be because they aren't an IATA member or because they just prefer the ICAO code. Regardless, this means that it is allowed to use OperatingAirlineICAO as part of FlightId. FlightId is then defined as the concatenation of AirlineIATAorICAO, FlightNumber and OperationalSuffix. | |
NB! IKKE FlightDepartureDate da det er datoen for lokaltiden som sendes. | |
Departure airport IATA code (see AirportIATA for description of term). | |
Arrival airport IATA code (see AirportIATA for description of term). | |
| IataPtmTransferToData 1..* | This is the flight leg passengers on the flight leg identified above transfer to. |
FlightDepartureDateLocal???? NB! IKKE FlightDepartureDate da det er datoen for lokaltiden som sendes. | |