Aircraft type in MyLog / MyFlights

Jollygreen · November 20, 2009, 12:37:13 PM

I am seeing several aircraft types as either blank, null or '...' in MyLog / MyFlights even though the aircraft is correctly identified in the picture section of MyFlights. Is there a way I can update the Aircrft Type table in the Database Explorer to have all types, mine is currently only showing 1036 records. Can anyone supply me with a list of the valid aircraft types so that I can update the actype table by hopefully importing the data.

Many thanks

Nigel

tarbat · November 20, 2009, 12:40:04 PM

You need to select the Aircraft table in database explorer. You can then update any aircraft types (the AT field) with the correct values. Sorting the table on the AT field is a good way of finding those with blanks or "...".

Jollygreen · November 20, 2009, 01:00:14 PM

Tarbat, trouble I have is that there are none of these values are in the Aircraft Type table. I only see them in the Aircraft table. Does the Aircraft table get the aircraft type designator from the Aircraft Table? If so, is it a case of checking what is missing from the Aircraft table and adding it to the Aircraft Type table. If so, do you know where can I get a list of valid aircraft types

tarbat · November 20, 2009, 01:26:32 PM

You should never need to update the actype table. I don't think that table is used.

There are lists around of ICAO aircraft types - eg. http://www.icao.int/anb/ais/8643/index.cfm
Put "*" in Manufacturer to get a list of all 9021 ICAO type codes.

I'm sure someone has posted a better link that that, so try a search on the forum for ICAO. However, what I tend to do is:

1. Look in the data\silhouettes folder. There you will find the silhouettes of all ICAO aircraft types that Radarbox recognises.

2. Find a similar aircraft in the aircraft table.

Do you have an example of what you're looking for?

Jollygreen · November 20, 2009, 01:47:13 PM

Some examples from today are ....
CS-DSA ...
CS-DXZ ...
D-ABQJ ...
N137WA ...
ZJ170 ...

Nigel

DaveReid · November 20, 2009, 01:49:15 PM

Quote from: tarbat on November 20, 2009, 01:26:32 PMThere are lists around of ICAO aircraft types - eg. http://www.icao.int/anb/ais/8643/index.cfm
Put "*" in Manufacturer to get a list of all 9021 ICAO type codes.

It's not quite as bad as that !

There are 2354 ICAO type designator codes - the 9021 count refers to the type descriptors, which contain a lot of aliases to aid searching.

tarbat · November 20, 2009, 02:08:16 PM

Quote from: Jollygreen on November 20, 2009, 01:47:13 PMSome examples from today are ....
CS-DSA ...
CS-DXZ ...
D-ABQJ ...
N137WA ...
ZJ170 ...

I'd use GAS lookup for those. For example, the first one (CS-DSA) is FA7X

YXUphoto · November 20, 2009, 04:50:03 PM

Just wondering....lets say RB gets a Mode-S code from an aircraft, what is the next step? Does it look in the NavData and if the info is there, then uses only that info? Or does it download more info from the network (if available) and replaces your entries in the NavData? I have been updating 100s of outdated entries in NavData and wouldn't want RB to overwrite my good info with outdated info (like Aircraft type)

tarbat · November 20, 2009, 04:56:03 PM

If you want to prevent Radarbox updating your aircraft, then best to turn off populate in Preferences.

DaveReid · November 20, 2009, 04:59:44 PM

Quote from: YXUphoto on November 20, 2009, 04:50:03 PMJust wondering....lets say RB gets a Mode-S code from an aircraft, what is the next step? Does it look in the NavData and if the info is there, then uses only that info? Or does it download more info from the network (if available) and replaces your entries in the NavData? I have been updating 100s of outdated entries in NavData and wouldn't want RB to overwrite my good info with outdated info (like Aircraft type)

The way it should work, IMHO, is that when you pick up a Mode S code RadarBox checks the current details for that code on the server, and if those are different (i.e. more up-to-date) than the details in your local database then the latter should be automatically updated.

But what has been happening to some users is that out-of-date (or blank) data coming from the server has been overwriting good data in their local databases - hence AirNav's advice to disable the downloading of photos/details as a precaution until the problem is fixed.

YXUphoto · November 20, 2009, 05:59:47 PM

I had a suspicion that was happening. I have noticed that I have updated several entries over and over. Problem is, most of the info I get is good and I wouldn't want RB to stop receiving updates. Sometimes partial updates are better than no updates. Once my DB is fairly full, I can turn off the info and just concentrate on fixing errors.

YXUphoto · November 20, 2009, 06:01:07 PM

I know lots of the info comes from the G.A.S. server, but when I tried to update their info, it wouldn't accept it.

Pinza · November 20, 2009, 07:39:29 PM

Have been busy manually updating my AirNav databases - mainly with a/c type - probably self-inflicted grief for ignoring this forum's advice to turn off auto-populate during network problems...

Finally worked out how to add or amend aircraft details, but still have one question:

Before I open Database Explorer (to play around), I am unchecking 'Process Hardware Flights' and 'Process Network Flights'.

Do I need to do this? - or can I leave them 'ticked' to receive live data while I update?

Am just a bit paranoid about corrupting my databases if AirNav tries to write to them while I have them open for editing!

DaveReid · November 20, 2009, 08:03:05 PM

The SQLite database engine is certainly capable of managing simultaneous access from multiple programs, or multiple threads within a single program.

A properly-written application should be able to take advantage of this.

Pinza · November 20, 2009, 08:09:26 PM

Gosh Dave - if that's a reply to me, then you've just blinded me with science!

Am I using a 'properly-written application' or not?

Basically, do I need to close 'processing' tick boxes or not before messing with Database Explorer.

Cheers
Chris ;)