Aircraft taxiing out still shown with their EOBT

[droesen]

This is observed with v3.0.0-rc.3:

Those two aircraft are already moving ("taxiing out"), but still shown with their SOBT (which is really EOBT).
Suggest to show distance from ARP instead.

And while we're at it, this screenshot was taken at 1837 UTC while taxiing to the runway holding point. The "delay 0:07" indication is flat out wrong as there was no delay at all - I went off-block exactly at 1830 UTC, so SOBT=EOBT=AOBT, with a TTOT of 1815 (15 minutes taxi time, but that's not contained in the FPL so QS can't know). If QS has that timing tracking data, "Delay" while taxi-out should only refer to AOBT (actual off-block time) vs. EOBT.

[jonaseberle]

QuteScoop assumes 6 min taxi-out time (that value was derived as median from "1st movement" to ">50 knots" 10 years ago by crunching numbers of 3 months of VATSIM data).

It is taken into account when in the air but it seems that it was forgotten for the "taxiing out" state. So correctamente it should display --:-- until 6min. Also mind that we do not really know if the aircraft has already pushed back - we only know if it is currently moving or not. Thus, while holding at the holding point, the state will be "boarding" again...
It is a lot of guess work - I look at it like "oh, most of the planes with > 20 min delay... I'll have to expect startup delays!".

I see that bug (missing taxi-out time) and it can be fixed.

For more involved changes we would need the Whazzup data from that time to be able to gauge advancements without regressions. You might have it in the downloaded folder.

It is good practice to share it, then we can all look at exactly the same situation.