Current Situation / Problem
LT only makes a model-change mid-flight if the level of information changes from „none“ to „some“, ie. If we can replace the default model/car with something.
If at the time of model creation some info is available (e.g. a/c type) but other good info (like operator) comes in only later, then LiveTraffic will not change the not-so-well-matching model with a potentially better matching model that could be derived based on the newer information.
Suggested Solution
Keep track of current model‘s match quality.
When new information arrives that influence model matching, match again, but only change the model if the new quality is better than the previous quality.
Benefits
Better information leads to better model selection, even after model creation.
Additional context
Discussed on Discord based on examples of not well matching models: A A319 AAL was not chosen but a A319 of a different operator. The operator information did not look like it originated from OpenSky...maybe it was an ADSBEx response that came in late.
Current Situation / Problem LT only makes a model-change mid-flight if the level of information changes from „none“ to „some“, ie. If we can replace the default model/car with something.
If at the time of model creation some info is available (e.g. a/c type) but other good info (like operator) comes in only later, then LiveTraffic will not change the not-so-well-matching model with a potentially better matching model that could be derived based on the newer information.
Suggested Solution
Benefits Better information leads to better model selection, even after model creation.
Additional context Discussed on Discord based on examples of not well matching models: A A319 AAL was not chosen but a A319 of a different operator. The operator information did not look like it originated from OpenSky...maybe it was an ADSBEx response that came in late.