ADU & Operator Logos

[Anmer]

Thanks for sharing Steve's input.

With reference to the user that Mike contacted me about yesterday, for some reason Mike had removed the vast majority of the add logo references and left a load of blank values in there.

Correction, Mike didn't remove anything.  The member may have done.

I was not insulting Mike's intelligence at any time by not continuing with the email thread but it was far quicker and easier for me to deal directly with the ADU user.

I have no problem with anyone insulting my intelligence or lack of it.  Just ask my wife.

But, in all seriousness, it would be more beneficial to ADU and its customers if this issue could have been shared, including the solution.

Having said that, I still don't get the logic employed.

I'm assuming, intelligence taken into account, that the ADU central database has the OperatorFlag code populated.  Let's assume for an RAF aircraft it has RRR, which is what it repopulated in the members database.

For the civilian aircraft I assume it uses an allocated ICAO code, such as BAW for British Airways.

With no logos added to the table, why does it not replace a non-ICAO code, such as BAW788 assigned to a civilian aircraft but does for a military one?

The callsign should be irrelevant.

Adding logos is a chore which the option to "Not overwrite" should make redundant.

[How 225]

After further dialogue with Steve Bruce, I think I now understand how the ADU SBS Utility software is implemented so I'll try to explain it.
For civil aircraft, you don't need to do anything unless there is a specific entry for a particular airline in the Add Logos table in which case it would need to be renamed (and for example there isn't an entry in the Add Logos section for British Airways, so that will not be overwritten).  For military aircraft, you need to change the entry in the Add Logo section in addition to ticking the "Do overwrite box" as was explained in Steve's previous advice provided in my last post.
However, one other way of addressing this issue is to do what I have done and just delete all the lines in the Add Logos Operator and Logo table.  You can't just delete the ICAO Name and leave a blank entry - you have to delete each full line.  Once you have done this, there will be no overwriting of logos as long as the "Do not overwrite box" is ticked.

Once this initial setup is sorted, the software works really well and users have the benefit of an accurate and up to date aircraft database.

[Faramir]

My Operator and Logo's table is pre-populated and I've added some entries to it, ie for the local police, air-ambulances and the coastguard.
I have to agree with Steve from ADU that the logo's are problematic in standardizing as there are more than one scheme's in use.

To start with a major problem regarding the OperatorFlagCode, they are not included in the temp.xml files. A SQLite trigger now copies the OperatorFlagCode to the MTOW field, every time the record is accessed. That way I can have more than one logo in use while keeping the Aircraft List in Basestation as generic as possible.

So, with Do not overwrite operator logo's unchecked, the Aircraft List in Basestation shows the OperatorFlagCode that the ADU program fills in based on ICAO code or the Operator and Logos table or no logo if no ICAO code applies and no entry exists in the Operator and Logo's table

With the Do not overwrite operator logo's checked OperatorFlagCode is left blank (which I prefer as that's a part of my daily Basestation routine). All other data is filled in by ADUSBS.

Additional Logo's
The PopularName field I update myself so a sub-carrier can be shown, a third field holds the Callsign from which the first 3 characters define the logo for the flight-operator if that differs from the RegisteredOwners. Military aircraft use a different CSS file so another Aircraft Details window is shown with an altered layout.

Using the SQLite trigger method and the extra fields more than one logo can be used to show lot more information in the Aircraft Details windows.

My experience with Steve is quite good, he's quick in answering e-mails and when it get's complicated he's willing to help hands-on via Teamviewer. His 'chilly' response to Mike I recognise as 'this get's complicated, let me do it or it will take hours to explain'. Well meant I'm sure but I understand Mike's reaction too.

All in all the ADUSBS tool works for me and after my getting used to it I'm happy with it. It lacks the 'Populate unknowns' from SBSPopulate but it focusses on the current aircraft in the Basestation session.