Closed dirtyformal closed 3 years ago
Changes have been made to Radars.xml
, adding the definitions for WP, WB, HN, AP, and OH.
WP, WB and OH have tested satisfactory, however, the other airports show no traffic until about 500ft above terrain.
The WP, WB and OH aerodromes are all near ADS-B receivers, so this could be the reason why they're being picked up on the ground. I think additional testing and understanding of the Radar types might be necessary.
After some help from @sawbe, it was found that the Lat/Longs were in the wrong format, and being parsed incorrectly or not at all. This was an easy fix - head into Google Earth, drop a pin on the apron at the airport and grab the decimal degrees readout from the Properties window.
AP, WP, OH, HN, PM, and NV have all been updated and tested satisfactorily.
Pull request coming shortly.
Closing this issue as it has been fixed in the above PR.
With the adding of additional ASMGCS positions (ground views) an additional entry must be made to the
Radars.xml
file, adding a Surface Movement RADAR (SMR). This enables aircraft on the ground to be seen.<Radar Name="[Location] SMC" Type="SMR" Elevation="[Airport Elevation]" MaxRange="4">
<Lat>[Lat, as found in AIRPORTS.xml]</Lat>
<Long>[Long, as found in AIRPORTS.xml]</Long>
</Radar>
At the moment, it looks like only WN, AA, CH, and QN have entries - which means that WP, WB, HN, and AP have to be added.