Open dirkhh opened 1 year ago
instead of opening another issue, it seems that SWA999 is of a similar special type. Also seems to designate ferrying a plane. Every day the route is different.
Not sure what the best thing to do is;
1) remove it. 2) have some kind of key to denote that it's not a static route? 3) update the data every week. 4) do nothing.
Not sure what my preference is, probably 1 or 4
I think it would be nice to have a way to add a flag that says "this flight doesn't have a predictable route". That could then apply to all the Net Jets, to these special airline codes, etc. (I know, that was not one of your two preferred solutions...)
Would mean adding a key to every flightroute/callsign response, which if we introduced, I think I would use a boolean - fixed
or static
, not sure, as in fixed: true
means that this is a predicable route.
Don't know if this is a good approach to the issue though
Url of request https://api.adsbdb.com/v0/callsign/SKW9799
Why was the data wrong this callsign is 'special'. SkyWest appears to use it for test flights and when shuttling aircrafts. Right now, as I type it, it's a plane transfer flight from Palm Springs to Seattle, yesterday they used it to move a plane from Spokane to Portland.
Additional context This isn't a flight with a 'regular' route at all - so giving one of the past values for it might not be the right thing to do.