Wrong country parse

Yes, sometimes it happens... Please report any bugs here
Post Reply
User avatar
yt9tp
Old Man
Posts: 147
Joined: 22 Sep 2013, 22:14
Contact:

Wrong country parse

Post by yt9tp » 14 Feb 2016, 03:45

After uploading log to ClubLog I received notification:

Callsign: GB4JPJ
Your log claims ENGLAND. Club Log has a specific exception for GB4JPJ and will use SCOTLAND.
See https://secure.clublog.org/t.php?c=GB4JPJ&t=1404571904 for details.
Note: There are comments about GB4JPJ in the Club Log database, which may provide further details. See https://secure.clublog.org/t.php?c=GB4JPJ&t=1404571904.

Callsign: RA1OW
Your log claims ABU AIL IS. Overriding your choice and using EUROPEAN RUSSIA.


For GB4JPJ I checked and Log4OM really parses country as England, not Scotland (country Database updated).
YT9TP, op. Pedja, QTH Uzice, Serbia, http://www.yt9tp.iz.rs

User avatar
G4POP
Moderator
Posts: 5818
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Wrong country parse

Post by G4POP » 14 Feb 2016, 08:05

yt9tp wrote:After uploading log to ClubLog I received notification:

Callsign: GB4JPJ
Your log claims ENGLAND. Club Log has a specific exception for GB4JPJ and will use SCOTLAND.
See https://secure.clublog.org/t.php?c=GB4JPJ&t=1404571904 for details.
Note: There are comments about GB4JPJ in the Club Log database, which may provide further details. See https://secure.clublog.org/t.php?c=GB4JPJ&t=1404571904.

For GB4JPJ I checked and Log4OM really parses country as England, not Scotland (country Database updated).
All GB4 calls are issued as Special event call signs and can be issued for any area of the UK (England, Scotland, Wales and Northern Ireland.) they are not country specific

See: http://rsgb.org/main/operating/licensin ... -stations/

As is not country specific it is therefore not possible to legistrait for it in the country file because there are hundreds of these calls issued every year and sometimes the same call is re-issued for different areas of the UK.

As an example I ran GB4ASC for All Saints Church at Creaksea England some years ago, the call was re-issued for another event in the UK some time later which was not necessarily in England!

I have held the following special calls which I could use anywhere in the UK had I wished to: GB4ASC & GB4GMF both off which were used in England.

The GB4JPJ call is issued for the commemoration of John Paul Jones birth place which just happens to be in Scotland, I could obtain a call like GB4RBN for Robbie Burns Night (He was a Scott also) but I could use the call in London!

Some manual intervention by the user is sometimes required with the occasional situation like this :(
73 Terry G4POP

User avatar
IW3HMH
Site Admin
Posts: 2378
Joined: 21 Jan 2013, 14:20
Location: Quarto d'Altino - Venezia (ITA)
Contact:

Re: Wrong country parse

Post by IW3HMH » 14 Feb 2016, 11:51

Terry said true. But the exception was enlisted into clublog exceptions, so we're able to read them
There is a very particular case of manual date time in the main user interface that will skip clublog check with date parsing.

The callsign was in Scotland several times, one of them between 5 and 7 july 2014.
This should be recognized by Log4OM when the actual date is between 5-7 july 2014 (no more...) or if you're using manual time mode.

I've fixed the manual time issue, and now the callsign is correctly reported as Scotland.

There is a bit of "confusion" in the code on that part, maily due to the high amount of changes made on this procedure over time. I was able to get the error and, hopefully, fix it for next release.
Daniele Pistollato - IW3HMH

PB4FUN
Advanced Class
Posts: 78
Joined: 27 Feb 2014, 18:20
Location: JO33KC
Contact:

Re: Wrong country parse

Post by PB4FUN » 20 Feb 2016, 09:39

Got another one.

Worked RW3DU/N and Log4OM displays United States.
Somehow the /N is used in Russia for stations with non-licenced people doing the TRX with the licenced person telling them what to say.
PB4FUN Meindert; Rig : Icom IC-9100 / Ant: Falcon OUT-250-B @4m AGL; 144 MHz 16 el @ 4m AGL; 70 cm 23 el @ 5 m AGL

User avatar
DF5WW
Log4OM Alpha Team
Posts: 1063
Joined: 02 May 2013, 09:49
Location: Kraam, Rhineland Palatinate, Germany
Contact:

Re: Wrong country parse

Post by DF5WW » 22 Feb 2016, 15:40

That results when coutrys using non official callsign extensions. Think all other loggers will show the same result ... ;) ;)
73´s .. Juergen ... RedPitaya SDR 5 W, 20 mtr. indoor wireloop feeded with homemade ladderline (600 Ohms) ...

User avatar
IW3HMH
Site Admin
Posts: 2378
Joined: 21 Jan 2013, 14:20
Location: Quarto d'Altino - Venezia (ITA)
Contact:

Re: Wrong country parse

Post by IW3HMH » 29 Feb 2016, 10:34

Callsign is not something you can "edit" as you like... prefixes and suffixes are subject to a standard, where /N is a USA suffix.
There is no way to understand if the /N is a Russian user in USA or a rookie on train in russia...
Daniele Pistollato - IW3HMH

Post Reply