Military -> Civil or Civil -> Military = LocalAircraft.txt

[rikgale]

When using Virtual Radar Server many people seem to find issue with some aircraft incorrectly being listed as Military Aircraft when then are not. For example nearly every aircraft with a 2-XXXX registration. The inverse also applies - aircraft listed as Civil Aircraft when they are Military.

To resolve this issue, and aid some of my friends, I have created a LocalAircraft.txt file to use with Virtual Radar Server. I have hosted it on Github (with a readme on the repo for how to use this file) for quick and easy updating. The repo can be found here: https://github.com/rikgale/LocalAircraft and a direct link to the .txt file here https://raw.githubusercontent.com/rikgale/LocalAircraft/main/LocalAircraft.txt

If you use this and/or want additions/changes made please open an issue on Github or reply to this post and I will add them to the file ASAP.




[attachment deleted reduce file load]

[DaveReid]

Out of interest, how does VRS hold the demarcation between the various allocation blocks?

Granted the UK's block (400000-43FFFF) is a bit fragmented (notably the VP-Bxx and VP-Cxx range), but I'd have thought it would still be possible to define ranges without having to identify on an aircraft-by-aircraft basis.

[DaveReid]

If it helps, here's the validation table that I use when attempting to identify where a Mode S code doesn't belong to the same country as an aircraft's registration (similar concept to the old Kinetic Countries.dat):

Code Select Expand


Cayman Islands 1       400001-40007F VP-C   
Bermuda 5              4000D9-4001BF VP-B   
Cayman Islands 2       4001C8-4001FF VP-C   
Turks & Caicos         400380-4003FF VQ-T   
United Kingdom         400400-41FFFF G-     
Bermuda 4              424045-424131 VP-B   
Cayman Islands 4       424135-4241F2 VP-C   
Falkland Islands       4241F4-4241FF VP-F   
Bermuda 3              424234-4243BA VP-B   
Bermuda 1              4243BC-4244FF VP-B   
Anguilla               424520-42452F VP-A   
Bermuda 7              424530-4246FF VP-B   
Cayman Islands 3       424749-42485F VP-C   
Bermuda 2              4248DB-424A04 VP-B   
Isle of Man 2          424B03-424BFF M-     
Bermuda 6              43BBE0-43BFFF VP-B   
United Kingdom mil     43C009-43CF3A       
Isle of Man            43E71D-43EAFB M-     
Guernsey               43EAFE-43EEC7 2-     
Jersey                 43F2CE-43F2FF ZJ-   

[rikgale]

Out of interest, how does VRS hold the demarcation between the various allocation blocks?

Granted the UK's block (400000-43FFFF) is a bit fragmented (notably the VP-Bxx and VP-Cxx range), but I'd have thought it would still be possible to define ranges without having to identify on an aircraft-by-aircraft basis.

I believe that it defines those ranges in the StandingData.sqb (located in the configuration folder), which is updated from the VRS servers each night. The LocalAircraft.txt overrides what is in that database, if present. I do not think it is possible to override entire ranges.

Poking about in that database, ranges could be changed but I would suspect that any changes would be overwritten each night. I believe that these updates could be turned off, but then you lose out on up to date route data. Swings and round-a-abouts. At least there is a way of changing MILITARY to CIVIL even if a tad clunky.

Thanks for your validation table