Fetaure request: Make aircratt route lookup possible to individually disable per ICAO

[marcus-aa]

Route lookup is normally a very nice thing but some special flights use callsigns that are used by airlines in another part of the world, and gets a totally incorrect route attached to them. See picture for an example of "Buffer31, BR31". Some rescue helicopters have the same issue.

It would be a great addition to be able to set a "no-route-lookup" flag in the Basestation.sqb file, so we could block this for those ICAOs that never use routes anyway.

For example, one of the "UserBool" fields could be set to 1 for this.

[rikgale]

I think this is 100% a great idea!
My only addition to this was - could it not be UserBool1. I am using this field to highlight if an a/c aircraft is military or not from within the database and this information will then be used in some report outputting for the docker container https://github.com/sdr-enthusiasts/docker-virtualradarserver.

[vradarserver]

The issue is that hard-coding a UserBool field to store that information is going to conflict with someone somewhere, and it doesn't work for people who use pre-built copies of BaseStation.sqb and regularly overwrite them.

That said I could have something that stores its own list of things that should be excluded from route lookups. If it's just a text file somewhere then 3rd parties could also edit it.

But in this case it might be better if VRS excluded military aircraft from route lookups if:

1. The military operator has no ICAO code or
2. If the callsign isn't prefixed with the operator's ICAO code.

That would exclude the aircraft in your example without the need to flag fleets of aircraft individually. It would exclude most military aircraft from route lookups.

The other rule that would exclude a lot of accidental lookups would be:

3. If the aircraft's operator has no ICAO code and the callsign is the same as the registration minus punctuation.

That would exclude general aviation traffic that has filed flight plans under their registration.

The last set of accidental lookups that comes to mind would be aircraft using callsigns that are not ICAO compliant, e.g. Australian national flights using their national operator codes that conflict with ICAO operator codes. I think those would be addressed as a natural part of solving the problem of identifying those aircraft in the first place.

[ua4wiy]

Maybe create a file like LocalAircraft.txt to override for custom routes LocalRoute .txt ?

[jimsy3]

can you add a feature where i could download the actual installer, instead of the visual studio bs?

[rikgale]

@jimsy3 not sure how your comment is approriate for this thread or even why anyone should bother posting a link to help you out when you quite clearly did not bother looking anywhere on the link on the front page of this repo or even a simple google search, but hey ho!

https://www.virtualradarserver.co.uk/Download.aspx