AirNav Systems Forum
AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: mighty3507 on June 19, 2009, 07:28:58 PM
-
I noticed this issue as I started to take a closer look for increased flight ID's when running 3.0 beta. It appears that only Airbus and Boeing aircraft types are shown with silhouettes in 'my flights'. I did check a screen shot I saved when running 2.0 and the same issue was there. I guess I really did not notice the issue prior to running 3.0.
I realize that not every aircraft in 'My Flights' may be displayed with a silhouette. However, I would think I would see the MD-80 and MD-90 series.
Does anyone have any suggestions on how to correct the problem?
Thanks,
--Steve
Chino Hills, CA
OS: XP Pro SP3
-
Looks like an auto-populate problem. I guess many US aircraft aren't fully populated in the GAS database.
You could use Database Explorer to update the ICAO Aircraft type field (AT). That will then ensure the correct silhouette appears.
Instructional video at http://www.airnavsystems.com/radarbox/video/Edit_Type.wmv
-
Tarbat,
Thanks for info. I did follow the instructions on the linked video and it did work. I tested using A7F02D. This is a Cessna 560XL Citation Excel. I checked with the GAS db and found the ICAO a/c type listed (C56X). I also checked one of my missing American Airlines MD-80s. The a/c type was also listed in GAS.
I know this is not a large sample. However, seems like something else may be going on.
--Steve
-
Hi all,
I thought this was a known problem that was being looked at as I have to spend a lot of time every day manually updating these. There is also the issue of BC-A, BKC3, BKC5 shortcodes populating from somewhere.
John
-
Part of the problem may be that once your database has got "..." in the AT field, it will never get corrected from the Airnav servers (derived from GAS).
You could delete the record from database explorer, and that should force Radarbox to get more recent data from the Airnav servers.
-
Hi Tarbat,
Most new contacts populate as "..." in the AT field, its only boeing,Airbus that populate correctly. Along with BC-A for Boeing C-17's. McDonald Douglas C-17's populate "..." K35R's populate as BKC3 or 5, FF-1 for F16's FF-2 for F27's.
I've manually updated my Navdata so its only the last 3 new contacts that now req updating. I'll post another screenshot when there are a few more to show.
John
Edit - Sorry McDonnell Douglas C-17A Globemaster III (Unless you want fries with it) ;-)
-
I run a weekly SQL report on my database looking for "..." and blank in the AT field (among other things), and then populate these from GAS. I actually enjoy the weekly task of reviewing new aircraft, checking the data, etc. But I realise not everyone enjoys it!!
-
tarbet are you manually populating these entries?
-
No, I've got a process (documented in an earlier thread) that exports the ModeS codes from RB, imports that into an empty Basestation database, and then use SBS-Populate to get the data. Then I export from the Basestation database, and import back into Radarbox.
I've added an extra field in the aircraft table to indicate when I've completed this process for each aircraft.
Well, you did ask!!
-
any chance of a point to the thread, pretty please
-
any chance of a point to the thread, pretty please
http://www.airnavsystems.com/forum/index.php?topic=1489.msg11716#msg11716
-
tarbat you are a star, many thanks
-
quick search found this about the ... / BKC3 in the AT field.
http://www.airnavsystems.com/forum/index.php?topic=2673
-
I run a weekly SQL report on my database looking for "..." and blank in the AT field (among other things), and then populate these from GAS. I actually enjoy the weekly task of reviewing new aircraft, checking the data, etc. But I realise not everyone enjoys it!!
Its good you can use SQL. I've only just started dabbling with it.
But should the short type not autopopulate anyway?
I don't mind some manual updating, I expect it, but this is tedious to do every day.
Has this feature always not worked or is it something with my set up? (vista/XP)?
The whole point of me buying a Radarbox as opposed to an SBS-1 was not to have to mess about with additional programs. I want to look at the screen not the software behind it.
John
-
But should the short type not autopopulate anyway?
Yes, it should. But sometimes when you FIRST see an aircraft, the GAS details aren't complete. So it populates with "...". What's needed is a way to force an update at a later date, and that's what Airnav need to develop, in my opinion.
-
It seems as though it is not just the aircraft table that needs more update capability.
The routes table is also being talked about, and that will not be updated by the mylogs, autopopulate routine!!!
-
The routes table is also being talked about, and that will not be updated by the mylogs, autopopulate routine!!!
Routes in the route table have a date against them, and they auto-expire after a month (I think).
-
The aircraft type has been discussed at length recently as well. Please have a search of the forum.
Routes are updated as they have timestamp, and once a specfic time has passed they are rechecked with our servers.
-
That did NOT happen during the last changeover in March.
I was still seeing routes, without the intermediate routing, as the aircraft regularly landed at EGNT.
Most were to or from AGPF and heading to the med!!!
-
That did NOT happen during the last changeover in March.
I was still seeing routes, without the intermediate routing, as the aircraft regularly landed at EGNT.
Most were to or from AGPF and heading to the med!!!
Remember it can take uo to a month before the current route in the database reaches its expiry date. So the routes can be wrong for up to a month.
-
Yes, it should. But sometimes when you FIRST see an aircraft, the GAS details aren't complete. So it populates with "...". What's needed is a way to force an update at a later date, and that's what Airnav need to develop, in my opinion.
I agree, and when the dust settles on V3.0 beta it will be very high on my wish list for V3.1
So I'll keep manually updating while I get my head around SQL. (Every days a school day)
The aircraft type has been discussed at length recently as well. Please have a search of the forum.
Airnav, the link to this thread is in an earlier reply. The outcome of the thread is open ended as there seems no definate answer to where the wrong short types are coming from or what is going to be done about it from your end?
Its one for the wish list for after V3.0 beta is all sorted. But we will cross that bridge later, I appreciate you have enough on with snagging the Beta.
Cheers John
-
But sometimes when you FIRST see an aircraft, the GAS details aren't complete. So it populates with "..."
I'm confused - are we saying that GAS has "..." in the type field, which RadarBox reproduces, or that RadarBox itself populates the type with "..." when GAS doesn't have any details?
Although the end result would be the same, we're talking about a different fix in each case.
-
I'm confused - are we saying that GAS has "..." in the type field, which RadarBox reproduces, or that RadarBox itself populates the type with "..." when GAS doesn't have any details?
Although the end result would be the same, we're talking about a different fix in each case.
Dave, A quick scroll through network traffic produced this in Database Explorer.
OO-TAE was the last new aircraft my box picked up localy, the rest are from Network traffic. Note the BMD0 which on network shows DC10 N373FE and the differance with the screen shot of what shows in myflights. VERY STRANGE!
John
-
I'm confused - are we saying that GAS has "..." in the type field, which RadarBox reproduces, or that RadarBox itself populates the type with "..." when GAS doesn't have any details?
Although the end result would be the same, we're talking about a different fix in each case.
This is the issue I am seeing. I see the correct ICAO aircraft type for an aircraft in GAS. However, that value never gets populated into the AT column of my Aircraft database. I get '...' instead. This appears to be occurring for all aircraft that are not Boeing or Airbus.
For example, AC9AAE. This is an Delta Airlines MD 90. GAS shows an ICAO Type of ‘MD90’. I saw this aircraft in my flights with the ‘…’ for AT. I used the DB explorer to delete the aircraft. I then closed RB and reopened. The ‘…’ value for AT was brought back in.
I know there have been issues with incorrect values getting into GAS and then brought in to RB. I am just wondering why values I see in GAS do not come into my DB.
--Steve
-
I'm confused - are we saying that GAS has "..." in the type field, which RadarBox reproduces, or that RadarBox itself populates the type with "..." when GAS doesn't have any details?
Don't know - only Airnav can answer that. My guess is that, when first seen, the ICAO type is probably empty in GAS, and the Airnav server inserts the "..." in ICAO Type. At some later date someone updates GAS with the ICAO Type, but that never gets to the Airnav servers.
But that is all guesswork.
-
Which I assume goes back to what tarbat said before about once the ... is in the short column it is not updated?
-
Which I assume goes back to what tarbat said before about once the ... is in the short column it is not updated?
Correct - unless you correct it manually.
-
Don't know - only Airnav can answer that. My guess is that, when first seen, the ICAO type is probably empty in GAS, and the Airnav server inserts the "..." in ICAO Type. At some later date someone updates GAS with the ICAO Type, but that never gets to the Airnav servers.
But that is all guesswork.
Fair enough.
Anyway, the good news is that, once V3.0 has settled down, I've been told that evaluating various options for getting the aircraft and photo details right is a priority from AirNav's point of view.
So expect to see a distinct improvement in the not-too-distant future.
-
And so say all of us