Could someone kindly explain what happens with routings updates etc.
This is pure guess work, but this is how I think it works. Firstly, it's important to understand that routes will only be displayed if:
1. The aircraft has a
Flight ID.
2. The Flight ID has a row in the local routes table - in column FN.
3. It's NOT a network flight. Routes on network flights are unreliable, until Airnav fix the bug.
So, when a
local flight appears:
1. Radarbox looks up the Flight ID in the routes table, and displays it.
2. If it's not in the routes table, or the CH date is over 1 month old, then Radarbox tries to find the route by doing a lookup on the Airnav server.
3. If it doesn't exist on the Airnav server, then the Airnav route server will attempt to lookup the route on their routes service provide.
4. After some time (how long?) this new route will get populated onto the Airnav server, so the next time that Flight ID appears in your local flights, it will get the new route.
So, you'll get no route under
any of the following circumstances:
1. The aircraft has appeared in your Networks flight list - the route may be displayed, but it might not.
2. The Flight ID exists in your routes table, but the TO and FROM columns are blank.
3. The Flight ID doesn't exist in your local routes table, and no route is found on the Airnav server. And until the Airnav server get new route data from it's provider, no route will be displayed.
Hope that helps. I find that for aircraft that have a Flight ID, over 90% have routes - see example from my screen now. But I do also
make my own updates to routes as well.
