Page 1 of 2
HC2.../8 gives wrong DXCC
Posted: 23 Nov 2014, 09:13
by DF5WW
Looks like we need an SCL Database or Country Database update ??? Some Station are at Galapagos (San Christobal SA-004) qrv. I worked HC2RCT/8 but L4O shows Equador instead of Galapagos ... also SA-004 would not be shown in the IOTA references for Equador. The List of the used calls at Galapagos you´ll finf here:
http://www.dx-world.net/galapagos-islands-dxpedition-2/
Re: HC2.../8 gives wrong DXCC
Posted: 23 Nov 2014, 11:14
by K7PT
Here we go again. If they would sign with the proper DXCC entity as the / call all would be OK, i.e. HC2ANT/HC8.

Re: HC2.../8 gives wrong DXCC
Posted: 23 Nov 2014, 11:19
by G4POP
It is impossible to resolve this call to the actual location, the problem is caused by the operator being a complete idiot /8 means nothing to any logging software or look up service
Re: HC2.../8 gives wrong DXCC
Posted: 24 Nov 2014, 09:44
by DF5WW
Will try to contact them over one of their eMail adresses and tell them about the problem. Before we have some problems with an upcoming LotW upload that counts only for Equador instead of Galapagos .....

Re: HC2.../8 gives wrong DXCC
Posted: 24 Nov 2014, 12:07
by K7PT
The real issue is that a /8 defines a district where a /HC8 defines a DXCC entity and this is by convention.
It seems lately, that a number of stations are throwing standards to the wind and it creates problems for everyone.

Re: HC2.../8 gives wrong DXCC
Posted: 24 Nov 2014, 16:55
by dk2lo
1. I am not so sure if HCxxx/8 is so wrong as posted. As described in the callsign directory of Hans Schwarz DK5JI such callsign extensions are allowed. Also in the past such calls were active e. g. HC2IWM/8 in May 2013.
2. Clublog is so smart to recognize the right DXCC HC8 for these calls. I dont know what is meant by SFA but LOG4OM should be able to do the same task as Clublog.
3. This problem is another reason to implement an "Expert Mode" as described in feature requests.
4. This is a public forum. I am concerned about that hams which do perhaps something wrong are titled as "complete idiots." We should be happy that they activate are semirare DXCC.
Please more respect an tolerance!
Re: HC2.../8 gives wrong DXCC
Posted: 24 Nov 2014, 21:13
by G3ZSS
The simple solution is to go into the logging window "Country IOTA SOTA (F2)" and change the country to Galapagos before adding the QSO to your log. Peter G3ZSS
Re: HC2.../8 gives wrong DXCC
Posted: 25 Nov 2014, 16:09
by DF5WW
Hi Peter,
that´s it what i´ve done in the 2nd QSO with Galapagos but former i´ve had no idea that there was a HC2xxx/8 from Galapagos. All the clusters say "Equador" and also the logging software so i think i wkd Equador .... But after the contact i read that there are 5 or 6 HX2xxx/8 calls aktive from Galapagos ...
B.t.w. Elena has not answered yet but at the qrz.com accounts of the HC2xxx calls that involved is a message (only for HC2xxx/8 operation) so i think tey have got those calls from the Equadorian government to use it with /8 from the Islands ....
Another thing, i can change manually but what is with the LotW ... If there is not stored that those calls are good for Galapagos they will not count it

Re: HC2.../8 gives wrong DXCC
Posted: 01 Dec 2014, 10:48
by dk2lo
Hi Juergen,
LOTW semms to know HC2xx/8 at the right place. I just received LOTW confirmation for HC2AO/8 counted for Galapagos Island. So dont worry about LOTW.
Good DX!
Re: HC2.../8 gives wrong DXCC
Posted: 01 Dec 2014, 12:49
by DF5WW
Hi Olaf,
nice news ..... Thank you
