Ground Radar plugin 1.6 beta 4

Juha Holopainen (839337)

Changes from beta 3:

Added unit settings (and updated level/speed related label item extraData settings)
Bug fixes

Should the plugin fail to load properly, update your Microsoft Visual C++ Redistributable package

For users of the Finnish setup, the below package contains plugin data files compatible with the beta version. Overwrite the existing files with the ones in this package to get the intended behavior (must be repeated every time the sector package is updated as it contains the files compatible with plugin version 1.5).

Jonas Kuster (1158939)

Had my ES 3.2.3.2 causing an unhandled exception from that plugin version when specifically opening a dedicated ASR for LSZG. No similar issue for other airports/ASRs. I wasn't able to determine the issue any closer.
Here is an extract of the plugin data files and the ASR I used.
https://1drv.ms/u/c/84901747c9d7093f/IQDItym-yXoNQ6QVN53DhDi9AbrJNnIq2ec_S3K9y6QVtO4?e=J0JwZ8

Juha Holopainen (839337)

Sorry to hear that. After some research, I've noticed that your sector file has TWO runway 06R/24L's at LSZG. The plugin apparently doesn't like having non-unique runway identifiers at all and gets its internal variables mixed up which later causes the crash. The fast solution is obviously making sure all runway identifiers at ground radar plugin airports are unique, but when using automated tools such as GNG this may be difficult to ensure so I'll get that fixed somehow - most likely will be done by just disregarding all runway definitions with already existing identifiers.

Jonas Kuster (1158939)

Juha Holopainen (839337) Thanks for your investigations. This is most likely a result of the change of the navigation data provider at Aeronav, which simply went unnoticed since there are no errors raised for this when the sector file package is created. The runway causing the issue was not part of the data package from the previous provider LIDO and was therefore defined manually. With new data from NG, an additional entry was created, not verifying unique identifiers, which would be the case if it was the other way round (you cannot manually add a runway with a designator that already exists). So I'll be able to resolve this by changing the sector file accordingly. This issue was introduced though with the latest b4 plugin version. Prior versions didn't have an issue with it.
Fun fact: The coordinates provided by NG reflect actually runway 06L/24R rather than 06R/24L. Looks like I have to report an issue there as well.

Ricardo Sousa (1110850)

Could I request a feature to activate a map based on the ground status of an aircraft at a certain stand? I'd like to activate a map that draws an indicator behind a stand that has an aircraft that has been cleared to push back, so something similar to ACTIVE:STAND:Type:FoundList, where it then checks the ground status of the aircraft that is occupying the stand.

Marius Linge (1621930)

Thanks for the update, Juha!

Added unit settings (and updated level/speed related label item extraData settings)

Is it possible in any way to define the unit per label type?
For GND we would like to display GS in Metric, but for APP it should be Nautical.