Dev:LHG DAS-Interface Technical description: Difference between revisions
Jump to navigation
Jump to search
Stefanseiler (talk | contribs) Created page with " == Contained data in DAS == We interested from DAS system with this information stream, for each planned flight: * status (on plan / delayed / cancelled ) * delay time * Operating craft ** type (e.g. Boing 747-8) ** tail code == Planned interface approach == KORDEUS is building a KAFKA interface, which subscribes to a '''"MOC/SARA" KAFKA Topic'''. Through this it which recieves messages of this type: ====== Operations updates ====== This information containing all op..." |
Stefanseiler (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
The DAS interface is residing on a bridge server, residing in the LH-intranet. It subscribes to a '''"MOC/SARA" KAFKA Topic'''. | |||
== Inbound information stream from DAS == | |||
Through this it which recieves [[LHG:DAS-Update messages|DAS-Update messages]] bearing these information: | |||
*Flight plan departure date | |||
*New departure date | |||
*Flight number | |||
* Planned craft | |||
** manufacturer (e.g. Boing) | |||
** type (e.g. 747-800) | |||
** Tail-Code (Registration Number) | |||
* Status (on plan / delayed / cancelled ) | |||
* Optional: | |||
** Status (on plan / delayed / cancelled ) | |||
**Delay time | |||
**Delay reason | |||
The updates can occur in a random time, but the closer the flight event comes, the more changes typically occur. | |||
== Local storage == | |||
After one or more [[LHG:DAS-Update messages|DAS-Update messages]] have been received, a local cache is built, which bears <u>one file per departure date</u> (from initial flight plan date, not new departure date). | |||
Each file holds a list of these elements<pre> | |||
OperatingCarrier (string, e.g. LH) | |||
* | Flightnumber (string, e.g. LH410) | ||
OriginPort (string, e.g. FRA) | |||
DestinationPort (string, e.g. JFK) | |||
Schedule | |||
> ScheduledDepartureDateTime_UTC (datetime) | |||
> ScheduledArrivalTime_UTC (datetime) | |||
ScheduleUpdate | |||
> UpdatedDepartureDateTime_UTC (datetime) | |||
> UpdatedArrivalTime_UTC (datetime) | |||
> UpdatedCraftmanufacturer (string, e.g. Airbus) | |||
> UpdatedCraftType (string, e.g. 747-800) | |||
> UpdatedTailCode (string, e.g. DLHZR) | |||
Status | |||
> OnPlan / Delayed / Cancelled (int-enum, e.g. 0,1,2) | |||
> DelayTimeInMinutes (int, 0) | |||
> DelayReason (string, "Drunken Pilot") | |||
</pre> | |||
== See also == | |||
* [[LHG:DAS Interface]] | |||
Revision as of 12:58, 23 December 2025
The DAS interface is residing on a bridge server, residing in the LH-intranet. It subscribes to a "MOC/SARA" KAFKA Topic.
Inbound information stream from DAS
Through this it which recieves DAS-Update messages bearing these information:
- Flight plan departure date
- New departure date
- Flight number
- Planned craft
- manufacturer (e.g. Boing)
- type (e.g. 747-800)
- Tail-Code (Registration Number)
- Status (on plan / delayed / cancelled )
- Optional:
- Status (on plan / delayed / cancelled )
- Delay time
- Delay reason
The updates can occur in a random time, but the closer the flight event comes, the more changes typically occur.
Local storage
After one or more DAS-Update messages have been received, a local cache is built, which bears one file per departure date (from initial flight plan date, not new departure date).
Each file holds a list of these elements
OperatingCarrier (string, e.g. LH) Flightnumber (string, e.g. LH410) OriginPort (string, e.g. FRA) DestinationPort (string, e.g. JFK) Schedule > ScheduledDepartureDateTime_UTC (datetime) > ScheduledArrivalTime_UTC (datetime) ScheduleUpdate > UpdatedDepartureDateTime_UTC (datetime) > UpdatedArrivalTime_UTC (datetime) > UpdatedCraftmanufacturer (string, e.g. Airbus) > UpdatedCraftType (string, e.g. 747-800) > UpdatedTailCode (string, e.g. DLHZR) Status > OnPlan / Delayed / Cancelled (int-enum, e.g. 0,1,2) > DelayTimeInMinutes (int, 0) > DelayReason (string, "Drunken Pilot")