Author: AviJake
Subject: Nearest freq: a/p ID bug, and missing a/ports?
Posted: 19 Dec 2014 at 3:40pm
So after a little bit with playing with some changes, here is our current state of affairs for which we're soliciting your input.
![]()
![]()
![]()
![]()
Subject: Nearest freq: a/p ID bug, and missing a/ports?
Posted: 19 Dec 2014 at 3:40pm
So after a little bit with playing with some changes, here is our current state of affairs for which we're soliciting your input.
Specifically note the third example. We think the callsign should just be Genk Radio even though it's an Info frequency. We generate the data in the row by appending the frequency type to thecall sign. We already have some special cases in the code, though. For example, if the call sign is listed as "Albuquerque Approach" andthe frequency type is Approach, we ditch the frequency type so that you don'tget "Albuquerque Approach Approach". So, it may be reasonableto implement a similar rule saying "if the call sign ends with radio andthe frequency type is information, then just don't append the frequencytype".
In this example, do you think the call sign shouldjust be "Genk Radio" or if it should be "Genk RadioInformation"?
