Gents, how do i 'clean up' my SQB file, to get rid of old / non existant hex codes ? is there a way to purge it ?
There's no app that I'm aware of that can "purge" the sqb. And I'm not sure how it would know what codes are "old" or "non-existant"?
SBS-1 Populate can delete "sessions" or individually selected hex codes.
Or you can use an sql database editor, backing up the file just in case.
ta, would i delete sessions etc, thru Basestation reporter ?
Quote from: YORKIESI on June 23, 2022, 02:32:01 PM
ta, would i delete sessions etc, thru Basestation reporter ?
Sessions are attached to a hex code If you run Reporter you can see what data is held, basically details of the aircraft flights from Basestation.
Removing Sessions doesn't remove any aircraft records.
As I mentioned, SBS-1 Populate can delete Sessions. Not Reporter.
Cheers
@YORKIESI If you're happy to start again I can compile an SQB file for you containing almost 500,000 entries.
The biggest variable is the format of your OperatorFlag codes. If you let me know what naming format you use I can let you know if I can produce something that fits your needs.
If you have a lot of "special" OperatorFlag codes, I can simply take your current SQB and delete/update entries as required. That's assuming you are happy for all of the sessions to be deleted.
Or you can simply use my SQB and associated Operator Flags that are contained in zip files that are available in the Links & Files shortcuts available on the RHS of this page.
Steve
First you need to know what you want to purge. Incomplete entries, codes that you did not see for a long time (and exactly how long would that be) or something else. There's no tool that can do that for you. If you know what to purge then you can delve into SQLite and make your own queries to manipulate the data in the database. You need a program for that but it is possible. If you're not familiar with SQLite queries then I would think that Steve's suggestion is a very good one as it gives you a comprehensive database that is pre-populated and good to go.
Just bear in mind though that the more Ops flags you use the slower the system will run which is why generic flags work best for majority of aircraft then selecting specific flags for those special aircraft of your choice.
I discovered anything exceeding 5500 different ops flags made the system more sluggish so I managed to surgically reduce to just over 4000 and it works ok.
On the purging side, it depends on how much data you feel you want to include. I elected to clear out all old airlines and types no longer in service using either Planespotters site or FR24 airline fleet listing which is reasonably up to date. It took some time (I used the winter season to sort it) but then I'm now able to insert all new deliveries as they are available and when in out "the field" spotting using SBS any new aircraft registered, I update later..
Usually I update files from previous month deliveries about 2-3 days into the new one But again depending on your choice I don't include every aircraft simply because I'm not going to see them and if some unusual one crosses my radar I'll include that henceforth. To illustrate the point I hadn't added ANA Dreamliners into my files simply because from my location I could never have seen them, however sadly due to war in Ukraine ANA elected to fly over UK and recently flying into LHR. So now I add them to database. All the helpful suggestions offered by the members enables us to get the best support available. Well Done members!