KZJX CRC reliever callsigns lighting up entire ARTCC

vatsimnetwork / vatspy-data-project

A home for VATSPY Data updates.

Creative Commons Attribution Share Alike 4.0 International

96 stars 130 forks source link

KZJX CRC reliever callsigns lighting up entire ARTCC #825

Open jivebiscuit opened 1 month ago

jivebiscuit commented 1 month ago

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.

jivebiscuit commented 1 month ago

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.

Adrian2k commented 1 month ago

Solution is to use dobble underscore such as JAX_C__CTR

jivebiscuit commented 1 month ago

Excellent. To confirm, change in VatSpy.dat?

KZJX|Jacksonville|JAX|KZJX
KZJX-P|Jacksonville (Panhandle)|JAX_P__CTR|KZJX-P
KZJX-C|Jacksonville (Central)|JAX_C__CTR|KZJX-C
KZJX-A|Jacksonville (Atlantic)|JAX_A__CTR|KZJX-A

Adrian2k commented 1 month ago

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.

jivebiscuit commented 1 month ago

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!

Adrian2k commented 1 month ago

Perhaps a change should be made to CRC internally to allow for this. Alternative 2 is to define all relief callsigns in the database such as:

KZJX|Jacksonville|JAX|KZJX
KZJX-P|Jacksonville (Panhandle)|JAX_P1|KZJX-P
KZJX-C|Jacksonville (Central)|JAX_C1|KZJX-C
KZJX-A|Jacksonville (Atlantic)|JAX_A1|KZJX-A

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 ENOS_1_CTR or Spain with LECM_R1_CTR.

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.