This is a fully populated SQB file (https://radarspotting.com/forum/index.php?action=tpmod;dl=item365), 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
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.
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
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
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.
wonderful . at last a populated sqb and silhouttes
complimenti
frank
Thanks for the feedback Frank.
Steve
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
Thank you sir, that's yuge! :D ...
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.
Quote from: gonzalu on October 29, 2020, 12:58:30 PM
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.
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
Quote from: Triple7 on October 29, 2020, 01:41:58 PM
or maybe create a guide and let Anmer scrutinise it first.
Happy to help.
Thank you guys... I mean, mine is very well maintained and populated but having an entire fleet done will definitely help ;D
Quote from: Triple7 on October 29, 2020, 01:41:58 PM
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 (https://radarspotting.com/forum/index.php?action=tpmod;dl=item30) 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.
Anmer...
First, thank you for the hard work (I assume it is hard as I am a DB DWEEB... I know nuttin' about databases :P )
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:
attach database "C:\Basestation_Original\BaseStationOriginal.sqb" as bsnew;
I assumed the actual code for SQL One should be
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!!
Another update... after running the new DB for a while, I have noticed that a few airplanes have what seems to be the MODELICAO in the OPERATOR ICAO field. Could this be due to the merge process?
Edit: It may be that's how S92Driver has his file purposely :P
So, does the process in the document and the SQL respect existing entries and either not overwrite them or add a duplicate? Just curious as to what is actually happening. I assumed (perhaps naively) that the process checks for existing ICAO HEX and then if exists, and fields are populated, leave as is on original, and if not found, it adds the record from the NEW imported db?
Hi Gonzalu,
Quote from: gonzalu on November 07, 2020, 04:44:20 AM
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:
attach database "C:\Basestation_Original\BaseStationOriginal.sqb" as bsnew;
I assumed the actual code for SQL One should be
attach database "C:\Basestation_Import\BaseStationImport.sqb" as bsnew;
Yes, despite all the proof reading, you are correct, the SQL 1 should load the new 'Import' sqb file - thank you for testing and reporting it. I am sure Anmer will amend the file and re-publish
Quote
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?
It doesn't matter - your choice - but if you choose to run the SQL again in the future, you won't need to re-create the TempData table. It won't make any difference to the functioning of your database if you leave it in place – it is emptied of any data at the end of the merge process.
Quote
Another update... after running the new DB for a while, I have noticed that a few airplanes have what seems to be the MODELICAO in the OPERATOR ICAO field. Could this be due to the merge process?
That would indicate either an error in the SQL - which has been tested and works, or your db is not in the same order as the original Kinetic one! I assume by MODELICAO you mean ICAOTypeCode as the column header and by OPERATORICAO you mean OperatorFlagCode? In the original layout, ICAOTypeCode was in column 14 and OperatorFlagCode was in column 50. Are your 2 columns in those precise positions? Open the db in SQLite Personal and click on the aircraft tab then (if not already selected) the Columns tab. Check where those columns are in your own db. If they are not in columns 14 and 50 respectively, then you will need to follow the instructions in the Appendix to sort it out.
[/quote]
Quote
So, does the process in the document and the SQL respect existing entries and either not overwrite them or add a duplicate? Just curious as to what is actually happening. I assumed (perhaps naively) that the process checks for existing ICAO HEX and then if exists, and fields are populated, leave as is on original, and if not found, it adds the record from the NEW imported db?
Yes, the idea is that any existing records are retained and all you are doing here is adding anything that is new and not currently listed in your db.
Tim
Hi Manny
You mention:
QuoteOne is loading the same database we are working on.
If, as advised, you've taken a copy of your current Basestation.dqb file, nothing, other than SQLite, should have access to the copy?
See Page 5.
QuoteI have noticed that a few airplanes have what seems to be the MODELICAO in the OPERATOR ICAO field
As far as I can ascertain, s92driver's populated sqb file doesn't have an OPERATOR ICAO field.
What field do you mean?
QuoteSo, does the process in the document and the SQL respect existing entries and either not overwrite them or add a duplicate?
See Page 4:
This Guide shows how to merge two files, typically one's existing file (original) and one with new aircraft data (import). The original file will include aircraft data, flights, sessions and the local receiver's "Home" .location. The import will typically only have aircraft data. This Guide shows how to merge aircraft data from an import file.
Following a merge, the updated original file will hold flights and sessions from the original, aircraft from the import and any aircraft from the original not in the import.
Merging databases is not without risk which is why the Guide advises working with copies of sqb files. If the resultant merged database isn't what one expected or has errors, it's possible to revert back.
The merging is not a selective "compare and replace" process for individual data fields.
If an aircraft record doesn't exist in the original sqb it will add all the the available data from the imported sqb. If an aircraft record already exists it will ignore it and leave "as is".
Be warned![attachment deleted reduce file load]
Quote from: Triple7 on November 07, 2020, 08:09:59 AM
Yes, despite all the proof reading, you are correct, the SQL 1 should load the new 'Import' sqb file - thank you for testing and reporting it. I am sure Anmer will amend the file and re-publish
Thanks Manny and Tim.
Even repeated proof-reading missed that. :(
The Guide has been amended and the new version uploaded.
You guys are absolutely superb. Legend as my Aussie friends say :D
Thank you so much for the work done and the confirmation and clarification for my dumb ass questions. With this in mind, I will once again do a fresh merge and confirm as Triple7 said, that my db and the import db are exactly the same column order. Since my db was a freshly created one via VRS, I assumed it was a legit layout.
Thank you guys ...
Quote from: Triple7 on November 07, 2020, 08:09:59 AM
Hi Gonzalu,
...snip...
Quote
That would indicate either an error in the SQL - which has been tested and works, or your db is not in the same order as the original Kinetic one! I assume by MODELICAO you mean ICAOTypeCode as the column header and by OPERATORICAO you mean OperatorFlagCode? In the original layout, ICAOTypeCode was in column 14 and OperatorFlagCode was in column 50. Are your 2 columns in those precise positions? Open the db in SQLite Personal and click on the aircraft tab then (if not already selected) the Columns tab. Check where those columns are in your own db. If they are not in columns 14 and 50 respectively, then you will need to follow the instructions in the Appendix to sort it out.
---snip...
Tim
Tim, you honestly believe I proofread that or verified the column headers? LOL. I told you I am a dweeb. So sorry. I should have used the actual column headers to describe the situation :P
Let me look at this again "carefully" and report back.
Cheers!
While an absolute nightmare coder, I'm trying to find out if I can automate the process within a Python script.
Actual work is being done by SQLite but I want to read the fieldnames from the original aircraft table and alter the queries with the order found.
It requires slicing lists, tuples and dictionaries and that is a tough task for me.
Furthermore it could be helpful in avoiding typing error's etc. and perhaps even some logging.
Just at the concept stage, but trying nevertheless.
The query to read the original Aircraft table fieldnames in order is working.
Now the tricky stuff begins :)
OK, round two of doing a merge :D
I now have done the merge but, I noticed the imported records all have the interesting flag set? Is this factually correct or is it something I am doing wrong on my end?
IS there a way to clear that flag before merging?
Here is an example...
(https://i.imgur.com/AsrPDmJ.png)
Thank you!
Oh well, I hacked around and think I figured a way to do it...
Open S92driver's database. In the SQL tab, entered the following SQL:
UPDATE Aircraft
SET `Interested` = NOT `Interested`;
This flipped the bit from checked to unchecked (true to false)
Seems to have worked fine :)
While working on a python script to automate the database merging process I find that more often than I like the database gets corrupted. It doesn't produce an error but when working with the databse at some point it crashes with the 'SQLite database disk image is malformed' message. The the database is no longer usable!
If you want to try merging, please use a copy of your database and check it's integrity before you start the merging process.
This can be done by entering the following command in the SQLite Expert Personal program:
PRAGMA integrity_check. If the result is anything else than 'ok', don't go any further and use the BasestationReporter program to pack the database first!
The latest sqb file is now available here https://radarspotting.com/forum/index.php?action=tportal;sa=download;dl=item64
Other than containing the latest aircraft data, it also now captures any Alaska Airlines aircraft still carrying the old livery.
Next month 'may' include a bigger change!
Steve
This months sqb will be generated later today.
Further to Gonzalu's recent posts, the Interested flag is something I deliberately set. Would users prefer it to be set On or Off for all records?
Finally, if anyone finds that an aircraft flying with a miscoded Transponder is constantly showing something very odd please let me know. For example an Emirates A380 is using the code allocated to a Cirrus. This next amendment will remove the Cirrus and only show the A380.
Steve
Thank you, Steve... your hard work does not go unnoticed or used ;)
I have my INTERESTING flag set only on such aircraft that I want to pop to the top of the VRS airplane list ... so I don;t mind whichever way you set your db as I now know how to unset it via SQL commands prior to merge.
Cheers!
Quote from: s92driver on December 30, 2020, 10:16:51 AM
This months sqb will be generated later today.
Latest
SQB file (https://radarspotting.com/forum/index.php?action=tpmod;dl=item69) now available.
This latest version of the sqb now includes almost 3000 ground based vehicles and radar heads that are fitted with ModeS transponders. These are all set as "not interested", so filters can be utilised so these don't show.
As usual any feedback or updates are very, very welcome.
Here's to a better 2021,
Steve
Quote from: Anmer on December 31, 2020, 11:42:37 AM
Quote from: s92driver on December 31, 2020, 11:03:42 AM
Here's to a better 2021,
What was the last one like? :)
:P
I've been told 2021 BC was pretty crap. No planes or internet for starters 8)
ROTFL :P
The latest SQB should be posted very soon. I've added about 50 airport "Locations" in Europe and N America. Any more can be added by request, just drop me a PM. These are used by Basestation to display aircraft on the ground, so are of more value if you use Basestation on the road.
I've also captured all N American "new" vs "old" livery info.
Next month will see a bigger announcement, with some more testing taking place before the launch 8)
Steve
Hi Anmer
"With Tim's invaluable assistance I've created a short Guide on merging two Basestation.sqb files".
The Guide link is taking me to the Dominican Republic VOR outline, any chance of getting back as I wish to combine two SQB file?
greg
Quote from: gregstu6910 on May 22, 2021, 08:18:44 AM
The Guide link is taking me to the Dominican Republic VOR outline, any chance of getting back as I wish to combine two SQB file?
Apologies, the post was prior to the Forum upgrade at the end of the year and that's why the link was invalid. Thanks for pointing this out. I've corrected the link in the post and you will find it here:
https://radarspotting.com/forum/index.php?action=tportal&sa=download;dl=item30
All Guides can be found in this section of the forum:
https://radarspotting.com/forum/index.php?action=tportal;sa=download;dl=cat5
And Welcome to the forum ;D
I somehow managed to update an existing post with this message. I'll post a new message so please ignore the duplication!
Anmer has just posted my monthly SQB update, along with the corrresponding Zip file of my images. These do go together as a pair.
If anyone would like to keep their sqb from month to month, rather than download a new one every month, I am in a position to run updates on existing sqb's. This will have the advantage that your "logs" will be retained.
I don't have a huge amount of time to update exisiting files, so depending on demand I may have to eventually say "not yet".
Send me a PM is you'd be interested in me updating your sqb rather than having a new file every month. Note that I will continue posting the new file as well.
Steve
Anmer has just posted my monthly SQB update, along with the corrresponding Zip file of my images. These do go together as a pair.
If anyone would like to keep their sqb from month to month, rather than download a new one every month, I am in a position to run updates on existing sqb's. This will have the advantage that your "logs" will be retained.
I don't have a huge amount of time to update exisiting files, so depending on demand I may have to eventually say "not yet".
Send me a PM is you'd be interested in me updating your sqb rather than having a new file every month. Note that I will continue posting the new file as well.
Steve
This month's updated SQB will be a few days late, as I've been away doing some actual spotting 8)
This months update will contain about 1800 "miscodes" for the first time.
I hope to get the update out tomorrow.
Steve
Dear Steve,
First of all, thank you very much for keeping us supplied with an updated Basestion file.
I mainly use it to correct the data from my Radarcape receiver during and after logging.
In the latest file (December 2021) I noticed that some entries in the 'OperatorFlagCode' field are unusual and are breaking my software.
For these the OperatorFlagCode is shown as either the Type (e.g.E295) or a combination of Type and Operator ICAO (e.g. KLCE295 or HZmofB788)
Most entries are as I would expect - the three letter ICAO code for the airline e.g. BAW, DLH, etc.
Is this a bug or are you changing the format ?
All the best for 2022 !!
mezoo
P.S. You can check by running the following SQL Query : select * from Aircraft where ICAOTypeCode = 'E295'
Quote from: mezoo on December 29, 2021, 05:09:32 PM
Dear Steve,
First of all, thank you very much for keeping us supplied with an updated Basestion file.
I mainly use it to correct the data from my Radarcape receiver during and after logging.
In the latest file (December 2021) I noticed that some entries in the 'OperatorFlagCode' field are unusual and are breaking my software.
For these the OperatorFlagCode is shown as either the Type (e.g.E295) or a combination of Type and Operator ICAO (e.g. KLCE295 or HZmofB788)
Most entries are as I would expect - the three letter ICAO code for the airline e.g. BAW, DLH, etc.
Is this a bug or are you changing the format ?
All the best for 2022 !!
mezoo
P.S. You can check by running the following SQL Query : select * from Aircraft where ICAOTypeCode = 'E295'
Hi mezzo,
The program crashing does sound odd, and shouldn't be caused by an an entry in the OperatorFlagCode field as long as no special characters are used (!, *, &, etc). The E295 type code is correct, as it's the allocated ICAO code for the Embraer 195 E2s.
Could the crash be caused by an OperatorFlagCode that doesn't have a corresponding Image in the OperatorFlag folder?
Steve
Quote from: mezoo on December 29, 2021, 05:09:32 PM
In the latest file (December 2021) I noticed that some entries in the 'OperatorFlagCode' field are unusual and are breaking my software.
For these the OperatorFlagCode is shown as either the Type (e.g.E295) or a combination of Type and Operator ICAO (e.g. KLCE295 or HZmofB788)
Steve's Basestation.sqb file has many OperatorFlagCode entries that do not use the official ICAO Type Code. This is to match the file names used for his Side View logos.
For example in his sqb file from August 2020, therre are many such entries for OperatorFlagCode, see attached. This is not new.
How is this "breaking your software"? What are you experiencing?
[attachment deleted reduce file load]
Quote from: s92driver on December 29, 2021, 05:33:25 PM
Could the crash be caused by an OperatorFlagCode that doesn't have a corresponding Image in the OperatorFlag folder?
This shouldn't cause a "crash". It would just leave an empty logo placeholder.
Thanks for the quick reply and explanation.
Crash is maybe too dramatic.
The Basestation SQB file is just used to look-up of airplane data (registration, type, operator, operator name) for new or unknown aircraft.
I used the OperatorFlagCode field to obtain the ICAO operator code for aircraft.
So for the previously unknown KLC aircraft PH-NXB (486258) my software would expect the entry 'KLC' and not 'KLCE295'.
Looking at the entries in the 'OperatorFlagCode' field there seem to be various data formats used : operator, type, registration, operator+type.
Which makes things a bit more interesting ;-)
So I am not sure how to modify my program :
reject all entries longer than 3 characters,
or grab the operator name and use it to look up the operator code elsewhere,
e.g. by adding an additional column to the Basestation sqb.
This is my project for the long winter nights and I havn't worked on it since March 2021.
Think of it as VRS light with a longterm database and statistics all the way back to 2013.
I can easily generate an up to date SQB that just contains the ICAO Operator code in the OperatorFlagCode field. PM me your email address and I'll send you a link to download it. 8)
Steve
Quote from: mezoo on December 29, 2021, 06:09:58 PM
So I am not sure how to modify my program :
reject all entries longer than 3 characters,
or grab the operator name and use it to look up the operator code elsewhere,
e.g. by adding an additional column to the Basestation sqb.
I think your easiest option would be to use SQL statements. For example:
Update Aircraft set OperatorFlagCode = 'UPS' Where OperatorFlagCode LIKE 'UPS%';
But Steve may have a better recommendation.
Quote from: s92driver on December 29, 2021, 06:24:45 PM
I can easily generate an up to date SQB that just contains the ICAO Operator code in the OperatorFlagCode field. PM me your email address and I'll send you a link to download it. 8)
I knew Steve would have a better solution. ;D
That would be fantastic. PM is on its way. 8) 8)
The latest monthly update should be available at some point this week. It will capture the huge shift towards Russian registrations for the Russian operators that has happened over the last few weeks.
It also now contains lat/long info for pretty much every large and medium sized airport around the globe in the Locations list - 3400 of them! If, like me, you use Basestation when on your travels this will allow centering of the Radar display easy by using the "Centre on Waypoint" menu option.
Just a reminder, I can update your existing SQB files on a monthly basis if required. There's no need to start with a fresh database if you'd like to keep your existing "logs". I tend to start with a fresh database on an annual basis so that my SQB doesn't get too large.
Steve
Quote from: s92driver on March 30, 2022, 09:14:18 AM
The latest monthly update should be available at some point this week. It will capture the huge shift towards Russian registrations for the Russian operators that has happened over the last few weeks.
It also now contains lat/long info for pretty much every large and medium sized airport around the globe in the Locations list - 3400 of them! If, like me, you use Basestation when on your travels this will allow centering of the Radar display easy by using the "Centre on Waypoint" menu option.
Just a reminder, I can update your existing SQB files on a monthly basis if required. There's no need to start with a fresh database if you'd like to keep your existing "logs". I tend to start with a fresh database on an annual basis so that my SQB doesn't get too large.
Steve
Hi Steve, your upgrades are great, you doing them now for my sqb a couple of moths and no issue what so ever. My sqb is now 238mb and have 529628 modes inside my SQB. So compliments for Steve with his upgrade support.
Cheers
Danny
Quote from: s92driver on March 30, 2022, 09:14:18 AM
The latest monthly update should be available at some point this week. It will capture the huge shift towards Russian registrations for the Russian operators that has happened over the last few weeks.
It also now contains lat/long info for pretty much every large and medium sized airport around the globe in the Locations list - 3400 of them! If, like me, you use Basestation when on your travels this will allow centering of the Radar display easy by using the "Centre on Waypoint" menu option.
Steve
Hi Steve,
I think there's been a mix up in the upload of this month's SQB file to the download areas. When I try to download that file, I get another copy of your latest OperatorsFlags archive and not the SQB zip file.
-Terry
Quote from: terryy on March 31, 2022, 10:42:30 PM
Quote from: s92driver on March 30, 2022, 09:14:18 AM
The latest monthly update should be available at some point this week. It will capture the huge shift towards Russian registrations for the Russian operators that has happened over the last few weeks.
It also now contains lat/long info for pretty much every large and medium sized airport around the globe in the Locations list - 3400 of them! If, like me, you use Basestation when on your travels this will allow centering of the Radar display easy by using the "Centre on Waypoint" menu option.
Steve
Hi Steve,
I think there's been a mix up in the upload of this month's SQB file to the download areas. When I try to download that file, I get another copy of your latest OperatorsFlags archive and not the SQB zip file.
-Terry
Thanks Terry, I'm sure Anmer will see this and sort things out.
Quote from: s92driver on March 31, 2022, 10:44:09 PM
Thanks Terry, I'm sure Anmer will see this and sort things out.
Oops ???
Please try now Terry. Sorry Steve,
For those of you that use my SQB with Basestation, you will have noticed the long time this now takes to load. It is all down to the 3400+ airfields I recently added into the Locations database. At the time I didn't realise the impact such a large list would have.
I have now trimmed this list to just under 400 major airports around the globe. This should make a dramatic difference to the load time of Basestation.
As the current file is causing issues I will produce an updated SQB very soon, hopefully later today.
Steve
That's this months SQB is ready now and should be available for download very soon.
After trimming the number of locations, the SQB on my laptop now loads in 13 seconds whereas the old one took 1 minute and 8 seconds. I am hoping everyone that found it took a long time to load Basestation with the old SQB will see a dramatic difference with this new one. Let me know how you get on!
Steve
Quote from: s92driver on May 28, 2022, 12:29:49 PM
That's this months SQB is ready now and should be available for download very soon.
After trimming the number of locations, the SQB on my laptop now loads in 13 seconds whereas the old one took 1 minute and 8 seconds. I am hoping everyone that found it took a long time to load Basestation with the old SQB will see a dramatic difference with this new one. Let me know how you get on!
Steve
An excellent resource which I've only just become aware of and look forward to trying out.
Running it through SQLite, I noted a handful of malformed hex codes which could usefully be tweaked for next month's file:
JU-1789/6823CO should be 6823C0
HL5240/A6BCF should be 71AA40 (formerly A64BCF)
N754CX/AA4CEO should be AA292D (formerly AA4CE0)
61-0020/AE58AP should be AE58AA
ZK-PBC/C81EDO should be C81ED0
HTH
Dave
Quote from: DaveReid on May 30, 2022, 05:05:39 PM
Quote from: s92driver on May 28, 2022, 12:29:49 PM
That's this months SQB is ready now and should be available for download very soon.
After trimming the number of locations, the SQB on my laptop now loads in 13 seconds whereas the old one took 1 minute and 8 seconds. I am hoping everyone that found it took a long time to load Basestation with the old SQB will see a dramatic difference with this new one. Let me know how you get on!
Steve
An excellent resource which I've only just become aware of and look forward to trying out.
Running it through SQLite, I noted a handful of malformed hex codes which could usefully be tweaked for next month's file:
JU-1789/6823CO should be 6823C0
HL5240/A6BCF should be 71AA40 (formerly A64BCF)
N754CX/AA4CEO should be AA292D (formerly AA4CE0)
61-0020/AE58AP should be AE58AA
ZK-PBC/C81EDO should be C81ED0
HTH
Dave
Hi Dave,
Some excellent sleuthing there, I will make sure that the corrections are put in place for next months update. I'll also try and construct an error checking script, as no doubt the odd incorrectly formatted code will emerge from time to time. Mr "QWERTY" didn't do a good job when putting the 0 and O so close together ;)
Steve
Quote from: s92driver on May 31, 2022, 10:17:13 AM
I'll also try and construct an error checking script, as no doubt the odd incorrectly formatted code will emerge from time to time.
Maybe DaveReid already has such a tool?
Quote from: Anmer on May 31, 2022, 10:21:24 AM
Quote from: s92driver on May 31, 2022, 10:17:13 AM
I'll also try and construct an error checking script, as no doubt the odd incorrectly formatted code will emerge from time to time.
Maybe DaveReid already has such a tool?
This is the script I use on my own Basestation.sqb to check that Mode S codes are properly formed:
select modes from aircraft where
substr(modes,1,1) < "0" or
substr(modes,1,1) > "F" or
substr(modes,2,1) < "0" or
substr(modes,2,1) > "F" or
substr(modes,3,1) < "0" or
substr(modes,3,1) > "F" or
substr(modes,4,1) < "0" or
substr(modes,4,1) > "F" or
substr(modes,5,1) < "0" or
substr(modes,5,1) > "F" or
substr(modes,6,1) < "0" or
substr(modes,6,1) > "F";
Thanks Dave, that's exactly what I have come up with. Great minds and all that 8)
Steve
The latest SQB file and associated "Silhouettes" will be posted by Anmer tomorrow. This latest version introduces a couple of subtle changes.
Firstly it will remove the non-standard ICAO codes that have been present up to now, for example all Canadair Challengers will show CL60 whereas previously you would also find CL61, CL64 and CL65.
There's also a simplification of ATR42 and ATR72 images and associated OperatorFlagCodes. Previously you may have seen a FlagCode containing AT72, AT73, AT75, AT76 whereas now they will have an image and OperatorFlagCode of AT7x. Similarly MD81, MD82, MD83 & MD88 are now MD8x. Note that this change does not affect the ICAO code, just the OperatorFlagCode field. This is simply to reduce the number of images supplied, as the more images that are loaded the slower the boot up is. Some users have reported issues when the total number of images being loaded is in excess of 8000.
I would recommend anyone that uses the SQB and associated images to download both every month. I do update images without posting the updates in the Gallery, however more importantly every month I do remove images that are no longer used as well as rename images when aircraft change registrations (eg bizjets).
Steve
The lastest update will probably be available tomorrow. A quick message to highlight that there's been a large "clean out" of special OperatorFlags, so the overall number of images will probably drop in the Zip file compared to last month.
Steve
Thanks you for maintaining an SQB file. Just uploaded and it covers almost everything. If a donation continues support this, then I am in.
It's been a year since my last message - yikes! The updated SQB and associated OperatorFlags zip files have been updated and posted on a monthly basis since I started publishing the SQB in 2020. I've no intentions of changing that.
The SQB and OperatorFlags can be used with VRS, Basestation, or any other software that uses the SQB format as a source database.
This message is to highlight a few headlines:
The database now contains more that 500,000 hex codes, where applicable associated with current registrations only.
There are more than 2500 miscodes.
There are more than 7250 "ground based" hex codes, usually with details of where they are located.
If the SQB is used with the OperatorFlags zip file, then each code received will result in the applicable image for that aircraft being displayed. No more constant manual adjustments of the SQB is needed!
I have also been updating a number of SQB files for various users every month. This has been happening without issue for at least 3 years. This has the benefit of keeping your existing SQB in use, maintaining all of the receiver history. If you'd like to give this a try or have any questions leave a message here or send me a dm.
Steve
id just like to express my heartfelt thanks and massive appreciation for this file and also the outlines. I had been suffering from lots of blank entries with my reg codes and it was looking awful and it was also affecting my PP display too.
downloaded your up to date sqb file and outlines to go with it and it looks absolutely amazing now so much better and up to date.
again many thanks for keeping the up dates going
Quote from: webmonkeyuk on June 25, 2025, 12:18:06 PMid just like to express my heartfelt thanks and massive appreciation for this file and also the outlines. I had been suffering from lots of blank entries with my reg codes and it was looking awful and it was also affecting my PP display too.
downloaded your up to date sqb file and outlines to go with it and it looks absolutely amazing now so much better and up to date.
again many thanks for keeping the up dates going
Thanks for the feedback. I'm glad you find it useful.
Steve