dbpop for RadarBox
 |
UnPop |
-deletes non-current records, keeping your database size down. It deletes:
- write offs
- sold-on aircraft
- broken up / permanently withdrawn from use
- defunct airlines - since RadarBox was first released, over 200 airlines
have ceased operations
- older aircraft that have been in storage for more than a year will be deleted
in turn
- there are an estimated 8-10,000 aircraft that could be 'unpopulated'
|
RePop |
- adds / updates info in current records
- refreshes all basic info - registration
- type
- construction number
- owner / operator
- ICAO type
- updates information for - aircraft mods (eg winglets)
- aircraft that have carried the same registration and hex
code on different frames
(N704CK, N740CK and N741CK have all been
used by 2 different frames each)
- aircraft that have used the same hex code with multiple
registrations
(hex code 401009 on a Legacy that has been
G-RUBN, G-RRAZ and is now G-THFC)
(hex code 400A71 on a BAe125/800 has been
G-OSPG, G-DCTA, G-GRGA and is now G-OGFS)
- all major changes will have a NEW flag placed in the Country Flag column
for alerting (major changes defined as change to registration / hex code / frame)
The 'new' logo is also used for PrePops - see example screen shot below)
|
PrePop |
- adds new entries to database, no need to go searching for details of aircraft when first picked up
up, hex code and details will already be in your database for:
- factory new aircraft prior to delivery where hex code already known
- imminent re-registrations with new hex code known
- entries will have a NEW flag placed in the Country Flag column
for alerting on first reception of a new entry.
NavData.db3 backup
A simple one-click button has been included, and copies your database file to a separate folder within the Data folder
dbpop
a subscribers-only group has been set up for discussion / feedback / ideas
an invite to join will be sent upon subscribing
dbpop for RadarBox Features
Please Note: due to the way the RadarBox AutoPopulate works, the RePop information supplied by dbpop may be overwritten. For this reason, dbpop is only completely suitable for users who have disabled and do not use the AutoPopulate at all
(File\Preferences\RadarBox\Photo and Aircraft Populate\(uncheck)AutoPopulate Aircraft Data)
If you do use the AutoPopulate, the PrePop and UnPop features are still fully functional and beneficial but you will subscribe on the agreement that the RePop information is subject to possibly being overwritten and out of the control of dbpop (solutions for this problem welcome!)
*NOTE*
PrePop will be done by region (see map below) You will select which
region(s) you would like to receive PrePop updates for, so if for
example if you live in Europe your database won't be pre-popped with
new American B738's if you didn't select region 2. There is a region10
called Worldwide fleet which is all aicraft over B767 / A330 size, all
smaller ETOPS aircraft (eg B757's to Europe), all large bizjets, and
aircraft from several countries of convenient register (eg Bermuda,
Cayman Islands) which everyone will get in their PrePop updates due
to the complexity of splitting this fleet. This means the choice is yours
whether to run the PrePop feature and is the reason why the dbpop
updates were split into three separate features. A full regions
list and map are also included with the download.
dbpop will add a line to the DAT.008 file for each new aircraft PrePopped into the database, causing the 'new' flag to be temporarily shown instead of the country flag, as an alert. Once the new aircraft has been seen and the 'new' flag is no longer needed, clicking on the Amend DAT file button will bring up a new window. There is a field where the hex code can be entered, and then deleted from the dat file, and the country flag will show again the next time that aircraft is received (but not until after the next time RadarBox is started). This window can be kept open separate from the main window, for easy editing, and there is also a button for quick access viewing of the dat file.
