AMC5249 - listed as EGNM -LMNL Leeds to Malta seen flying South from direction of EGPH - Edinburgh or points North.
Any ideas if this route has changed?
Will RB update routes Automatically or is this another one for manual editting on each users Box?
Thanks.
Quote from: jgrloit on March 17, 2009, 11:43:52 AMAMC5249 - listed as EGNM -LMNL Leeds to Malta seen flying South from direction of EGPH - Edinburgh or points North.
Any ideas if this route has changed?
AMC5249 is a Glasgow-Newcastle-Malta flight.
Route lookup at http://www.flightroutelookup.com/FlightRoute/ gives EGNT (Newcastle) - LMML (Malta)
AirNav software and route server retrieves new route data each 6 months.
Is the route data shown on the virtual radar screen coming from the aircraft or the flight number / route data held within the RB database.
MTIA
Nigel
Database. The aircraft do not broadcast there routes, the software derives the route from the Flight ID.
Quote from: AirNav Development on March 17, 2009, 11:57:32 AM
AirNav software and route server retrieves new route data each 6 months.
Is this six months from last update of that flight, or from the date of software being used?
Is there any way to prompt the system to update a "bad route" - one seen way off track like this?
Quote from: jgrloit on March 17, 2009, 12:56:23 PMIs there any way to prompt the system to update a "bad route" - one seen way off track like this?
Yes, one way is to use the aircraft's current position to do a sanity check on the returned routeing.
For example if you use the web service in the link that Tarbat posted above, the server will ask for the ADS-B coordinates of the aircraft, and will only return a route segment if it's consistent with the aircraft's position. That also helps to establish, if it's a multi-segment route like that Air Malta flight, which leg the aircraft is currently flying.
I don't see any reason why RadarBox couldn't do something similar - better to display no route at all rather than the wrong one, IMHO.
On the subject of routes - I've had a number of flights in the last fortnight where the database table holds all the data for the route but the date in the attribute CH is greater than 6 months. The route has been missing from the display.
When I look at the table via Database Explorer and change the date to current day then uncheck and check Process Hardware Flights then the route displays.
Is this how it should work or is this something we are waiting to have fixed ?
Wayne
AirNav - any comment on this ?
Aplogies must have been missed this post.
The date should not affect whether its dislpayed or not. More likely whats happened is the flight has come from being on the network and then transitioned to local flights. There is a bug where by it then does not force to check the database for the route.
Turning hardware flights on and off is a temp fix for it to force that. This will be fixed in the next version.
The route query that started this thread, was Local Box ONLY, with the Network available.
As stated the Aircraft was seen travelling South, towards EGNT.
Date in the Routes table - when checked today was 17 Feb 2009...
If routes are known to change around certain dates, could they be checked around those dates, rather than on the set 6 month period?
I agree with jgrloit on this one.
My network was switched off so I personally didn't see any transition from network to local. It was always a local flight to me, not showing a route but all the information needed to display a route was present.
If changing the date doesn't affect the display it's a bit suspicious that the route displays when you do change the date to one that is within 6 months of today's date.
Re Flight Routes. I see the odd ''back to front'' route creep in from time to time.
Quote from: AirNav Support on March 18, 2009, 09:20:00 AM
Aplogies must have been missed this post.
The date should not affect whether its dislpayed or not. More likely whats happened is the flight has come from being on the network and then transitioned to local flights. There is a bug where by it then does not force to check the database for the route.
Turning hardware flights on and off is a temp fix for it to force that. This will be fixed in the next version.
Is this bug fixed in v3.0?
Yes.