AirNav Systems Forum
AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: Marinus on March 25, 2008, 11:41:03 AM
-
Hello,
Autopopulate works fine, but now I get following errors:
(http://i274.photobucket.com/albums/jj263/liamer_photos/PopulateErrors.jpg)
as you can see information gets shifted to the wrong field, I now get Airline information
in c/n field etc. This doesn't seem to happen for all aircraft....
Anyone else getting this also ?
Marinus.
-
Definately a bug - I've got loads of these in my database as well, with serial and company switched:
(http://img258.imageshack.us/img258/7909/pphw7.th.jpg) (http://img258.imageshack.us/my.php?image=pphw7.jpg)
Airnav Support, can we get this fixed, and we'll also need something that lets us correct the previous errors.
-
Not a nice error but good find, investigation under way.
-
While talking about switches - can we get the switch that shows First Time and Last Time data in Mylog from imported .sqb files back to front sorted as well please :-]
-
I'm getting exactly the same error with the swopped fields.
-
Please send us examples (mode-s codes) of aircraft where those errors appear.
-
Please send us examples (mode-s codes) of aircraft where those errors appear.
Here's just a few of the dozens that I've got in error:
503C59, 506C13, 4783A0, ABA79C, 400AAB, 400E3F, E480C5, E480C9, AA26CE, 868DFC, 89402B, 89402C, 401122, 3D1869, A16EC2, AA8315, 7C6D2C, 868039, 3DB615, 8410AE, A894F2, A8A3CE, 394C0E, 398C44, 4010EB, 84B466, 84B488, A84706, 4CC2CC, AC0B61, 4010ED, A24B06
MS AR AC CN
503C59 LY-AQV 25069/2053 FlyLAL - Lithuanian Airlines
506C13 S5-AAM 25236 Adria Airways
4783A0 LN-OHI 2582 CHC Helikopter Service
ABA79C N850CT 258677 Emerson Climate Technologies Inc
400AAB G-REDK 2610 International Aviation Leasing Ltd
400E3F G-ZZSE 2660 Bristow Helicopters
E480C5 PR-VAC 27048 VRG Linhas Aereas
E480C9 PR-VAN 27427/579 Varig
AA26CE N753SR 2759 Cirrus Design Corp
868DFC JA773J 27653/635 Japan Air Lines - JAL
89402B A9C-KC 286 Gulf Air
89402C A9C-KD 287 Gulf Air
401122 G-TOYK 28870/2899 Bmibaby
3D1869 D-EHMN 28R-7931158 Untitled
A16EC2 N19136 29285/856 Continental Airlines
AA8315 N777AN 29585/218 American Airlines
7C6D2C VH-VUM 29675/2414 Pacific Blue Airlines
868039 JA737P 29681 Skymark Airlines
3DB615 D-GPEZ 30-1871 Untitled
8410AE JA04MC 3025 Star Flyer
A894F2 N652JB 3029 JetBlue Airways
A8A3CE N656JB 3091 JetBlue Airways
394C0E F-GTAO 3098 Air France
398C44 F-HDCE 311 XL Airways
4010EB G-EZBW 3134 EasyJet Airline
84B466 JA206A 3147 All Nippon Airways
84B488 JA207A 3148 All Nippon Airways - ANA
A84706 N632VA 3155 Virgin America
4CC2CC TF-NPB 3161 IceJet
AC0B61 N87507 31637/2487 Continental Airlines
4010ED G-EZBY 3176 EasyJet Airline
A24B06 N247LM 31T-8104043 Mystair Inc
-
Please send us examples (mode-s codes) of aircraft where those errors appear.
Here are a few from me, aircraft serial number and operator reversed in NavData.db3. I'm assuming that these have been GAS autopopulated, but I don't really know if this is the case. On the other hand, these could have happened during BaseStation sqb import.
4CA628
401274
43E72F
4CA645
4CA648
4CA646
-
No, they're not GAS populate errors. I've just checked one (503C59) against GAS, and the fields are NOT switched in GAS - in fact, the details are slightly different in GAS suggesting these did NOT come from GAS.
-
But do we know that the data source for the GAS populate is the same as what we can see in the "public" GAS search area? It probably is, but I presume that the AirNav Server is getting the data via a different access route? I wonder why it's only some aircraft and not all of them with the errors?
Edit: Good point tarbet
4CA628 EI-DSI A320
is in thesearchable GAS database but only has the callsign, no other details. The record is in NavData.db3 with the AC and CN fields reversed - maybe this came with the original database - or it could still be a sql import error
Also, I've got 503C59 too - AC and CN reversed
-
Here's some of mine :
A96F74
40126A
A3352A
A715BB
ACC98C
C0640D
4CA60A
43E719
They seem to occur in batches and from what I can see they are only from Network aircraft, not My Flights. I have noticed when traffic is heavy that the program is pulling down maybe 20 requests at a time. Maybe it's too much for my PC to process ?
-
One common factor is that many of these aircraft with switched details only have ONE photograph, or no photograph at all.
Maybe the processing that was introduced to handle single photos got the fields the wrong way round?
And I've got at least 1 aircraft that was only LOCAL aircraft, not network (400E3E) - it's not ADS/B equiped.
[attachment deleted by admin]
-
EINN-07
How do you know they are from Network traffic? Is this because they don't appear in MyLog - you could be right, but how do we know they didn't come like that in the original database?
-
One common factor is that many of these aircraft with switched details only have ONE photograph, or no photograph at all.
tarbat, that is a significant observation!
I went to DataBase Explorer, viewed the aircraft table and sorted by PT - and sure enough, almost all of those without a photograph have the AC and CN fields swapped.
-
One common factor is that many of these aircraft with switched details only have ONE photograph, or no photograph at all.
I think Tarbat has a point here, most of the aircraft that has autopopulated
the last few days, have no photo's or just the one in the airliners.net database
I've noticed that some of the entries that didn't populate good with Tarbat
filled in just fine with me, this can propably be explained by the growing
database of airliners, that is when I logged the aircraft there were more than
2 photo's in their database....
Regards,
Marinus.
-
It's going to be a nightmare to clean up the polluted data in the aicraft table :(
-
It's going to be a nightmare to clean up the polluted data in the aicraft table :(
You must be able to come up with an SQL query that can tell the difference between numbers and letters - is there an ascii type filter?
Do that a couple of times, export, import etc - piece of cake :-0
Except for the companies that start with numbers, and the serial numbers that start with letters - agghhhhhhh..........
Maybe I'll just leave it as it is!
-
Could try doing them manually - that is if you have a year or so spare ? ? ? :-(
-
My first corrupted record dates to March 7th !
-
My first corrupted record dates to March 7th !
You mean that this was the first time that you detected that aircraft? But was it already in the NavData.db3 database? MyLog is populated from NavData if the record is present, then from Autopopulate if it isn't. so the date doesn't necessarily mean a great deal.
-
True,
The date of first detection was March 7th but I could count on the fingers of one hand the number of times I have populated in the past three weeks and would be pretty certain that the dates match ie the date the data was downloaded was March 7th
-
Hello Airnav,
Any progress regarding this bug ?? as I'm still getting
these and my Database get's more and more corrupted,
alsmost impossible now to correct things manually....
Regards,
Marinus.
.
-
It should be fixed for 1.6. Its not a easy to bug to rectify.
-
Ok,
Roger that..... thanks for the swift reply regarding my question
Marinus.