Populated SQB file

[s92driver]

This is a fully populated SQB file, generated initially by Planebase SQB Creator using data contained in the Planebase database (www.planebase.biz) .  Particular thanks are due to the Planebase team for allowing their data to be utilised and distributed.  Thanks also to Anmer for hosting the file on Radarspotting.com

The SQB contains close to 500,000 active aircraft. 

The OperatorFlagCode entries in the SQB have been modified to ensure maximum correlation with the sideviews I produce.  Using the latest SQB file and latest set of sideviews will ensure almost every aircraft received will be able to have the most suitable sideview image displayed.

Most sideviews use the standard "Airline ICAO code" + "Aircraft ICAO code" combination e.g. BAWA320.  Full details of the sideview naming standard are available here https://radarspotting.com/forum/index.php/topic,6349.0.html   

The SQB will specifically capture the following, ensuring the correct image is displayed:
•   If the airline+aircraft code combination is not found then the aircraft only code is used.
•   Sharklet and winglet equipped aircraft
•   Sideviews identified by registration e.g. special liveries, Frontier, etc
•   Airliners in a white livery
•   Military and other airline images that don't have an allocated ICAO code
•   Aircraft flying in other airline's livery e.g. US feeder airlines, Fedex, etc
•   Airlines that operate passenger and freighter versions of the same type
•   Airlines that don't have a single livery e.g. JetBlue, Jet2, etc
•   Airlines that fly a combination of new and old liveries

Before proceeding be advised that:
•   Your existing session and flight information will not be available in the new SQB file.  If you wish to retain an historic record then you will need to retain backup copies of your SQBs.
•   Your existing Basestation Location information will not be retained.  Open up the Location Manager in Settings and note down the information you wish to transfer to the new SQB file.
•   Planebase does use non-standard ICAO codes for a number of business jets.  This may cause issues if other sideviews or silhouettes are utilised.
•   The SQB file does not contain aircraft that are stored or "withdrawn from use" when the file was generated.
•   The use of sideviews other than those generated by S92driver will result in incomplete or inaccurate generation of displayed images.  Manual modification of the SQB file will be required.

Finally, please provide feedback via the Radarspotting forum if something isn't displaying correctly.  Ensuring accurate and up to date information regarding aircraft liveries is both time consuming and almost impossible to do.  Airlines remove special decals and repaint aircraft on a frequent basis and your help will be extremely valuable in keeping on top of all the changes.

The SQB currently captures "old" livery data for European and Long-Haul operations only.  Coverage will be expanded when time permits.

I could populate the Location database with major airports around the globe, if users think this will be of value.  At the moment it just contains location data for Heathrow.

Please use this thread to provide feedback, updates and requests relating to the SQB file.

____________________________________________________________________________________________________


The download is available here https://radarspotting.com/forum/index.php?action=tportal;sa=download;dl=item69


_____________________________________________________________________________________________________


Installation is relatively straightforward and described in the "readme" file contained in the zip file.  It is reproduced below for convenience.


SQB file installation

1.   Note down the details of any Locations (Settings, Location Manager) you wish to transfer.
2.   IMPORTANT:  Shut down your aircraft monitoring program e.g. Basestation.
3.   Locate the folder that contains your current active Basestation.sqb file.  To ensure you have the correct file, check the time and date stamp.  It should display the date you last closed down your Basestation software.
4.   Rename the existing SQB file by adding the date in reverse order e.g. rename to 200630_Basestation.sqb if you are updating the file on 30th June 2020
5.   If necessary, create a folder that will contain all of your old SQB files e.g. Kinetic/Basestation/SQBBackups
6.   Move the old renamed SQB file into your backup folder created in step 4.
7.   Unzip and move the new Basestation.sqb file into the folder used in step 2.


If also updating the sideviews (recommended), then:

a.   Download the latest zip file (link in the message footer)
b.   Locate the folder containing the sideviews e.g. Kinetic/Basestation/OperatorFlags
c.   Delete all existing images
d.   Unzip the new images directly into the folder used in step b.



Steve

[Pipo]

Im using this SQB file and it works great, it is loading quick and in basestation reporter it is showing 483.*** plane files, all with good info inthem.

[s92driver]

Thanks for the feedback Pipo, it's good to hear things are running smoothly.

Do let me know if you see anything that needs amending or is missing.



Steve

[s92driver]

I've just noticed that I have transposed the Emirates B777s in the green and orange Expo livery, so green a/c are showing orange and vice versa.

This will be corrected in the SQB published next month.


Steve

[s92driver]

Later this week I intend to produce another SQB.  If any users have anything they would like corrected, or have any suggestions to improve the file, please let me know.

[sterigia]

wonderful . at last a populated sqb and silhouttes
complimenti
frank

[s92driver]

Thanks for the feedback Frank.


Steve

[s92driver]

I will be producing the next monthly update over the coming day or so.  This one will capture all of the livery details for the entire United fleet, so any United mainline or Express aircraft flying in the new livery will display correctly.

If anyone has any amendments or suggestions please let me know.



Steve

[gonzalu]

Thank you sir, that's yuge! ...

Any tips on merging databases? I have tried it with simple dump SQL and import commands but, maybe there are better/more respectful ways to do it lol.

[Anmer]

Any tips on merging databases?

In 15 years I've not found a way.  Hence the "warning":

Please Note:

1. Replacing your current, active BaseStation.sqb file will delete your database history, including Sessions.

[Triple7]

I have a method of merging the 'Aircraft' table using updated / new data. It's what I do on a regular basis.

It's not for the faint-hearted and does require use of a series of SQL commands. I will dig it out and try and post it - or maybe create a guide and let Anmer scrutinise it first.

Tim

[Anmer]

or maybe create a guide and let Anmer scrutinise it first.

Happy to help.

[gonzalu]

Thank you guys... I mean, mine is very well maintained and populated but having an entire fleet done will definitely help 

[Anmer]

I have a method of merging the 'Aircraft' table using updated / new data. It's what I do on a regular basis.

It's not for the faint-hearted and does require use of a series of SQL commands. I will dig it out and try and post it - or maybe create a guide and let Anmer scrutinise it first.

With Tim's invaluable assistance I've created a short Guide on merging two Basestation.sqb files.

With full acknowlwedgement to Charles Cartmel whose instructions underpin the Guide.

Suggestions for improving the Guide will be most welcome.

[gonzalu]

Anmer...

First, thank you for the hard work (I assume it is hard as I am a DB DWEEB... I know nuttin' about databases  )

Anyway, in following your excellent document, I ran into an error where the database claimed to be locked.

SQL Two fails with the error as I believe SQL One is loading the same database we are working on. Currently the documentation has SQL One as:

Code Select Expand

attach database "C:\Basestation_Original\BaseStationOriginal.sqb" as bsnew;


I assumed the actual code for SQL One should be

Code Select Expand

attach database "C:\Basestation_Import\BaseStationImport.sqb" as bsnew;


Sure enough, that worked

Now, the close, does it matter that the TempData table stays in the db? I left it as is and seems to work but, figured it may be good to clean up and leave db back as it was originally?

Thank you!!