-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KZJX CRC reliever callsigns lighting up entire ARTCC #825
Comments
I'm now aware that this may not be an issue for this repo but rather for the sites/program that use the data to render their maps. I'll keep this here in case there are any thoughts but feel free to close if not relevant. |
Solution is to use dobble underscore such as JAX_C__CTR |
Excellent. To confirm, change in VatSpy.dat?
|
No - the relief controller has to be logging on with dobble underscore for programs such as VATSPY to display it correctly. So controller taking over for JAX_C_CTR will have to log on as JAX_C__CTR - this way it will be displayed properly. |
Ahh okay. Callsign not user-selectable in CRC in the US. We might be able to hack something into the available positions/callsigns in the CRC backend. Will let ZJX staff experiment. Thanks! |
Perhaps a change should be made to CRC internally to allow for this.
But I believe this would be quite a mess for the dataset eventually. If mapping software would change to see 1 as a relief callsign, it would break in other areas that uses numbers in their logons, such as Norway for example which have a sector Ultimately, having a dataset as vatglasses will allow for any callsigns to be used as it will only focus on ICAO (JAX), type (CTR) and active frequency to determine which sector it is, same way as EuroScope does it. |
JAX_C1_CTR is the default reliever callsign assigned by CRC when taking over from JAX_C_CTR. When JAX_C1_CTR is online, it lights up the whole ARTCC rather than the Central subsector. Is there anything to be done here?
It seems that any reliever callsign is assigned the whole ZJX airspace.
The text was updated successfully, but these errors were encountered: