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).
Wrong country parse
Wrong country parse
YT9TP, op. Pedja, QTH Uzice, Serbia, http://www.yt9tp.iz.rs
- G4POP
- Log4OM Alpha Team
- Posts: 10815
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Wrong country parse
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 specificyt9tp 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).
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
- IW3HMH
- Site Admin
- Posts: 2927
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: Wrong country parse
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.
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
Re: Wrong country parse
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.
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
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: Wrong country parse
That results when coutrys using non official callsign extensions. Think all other loggers will show the same result ...
73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at SG-211 autotuner, 2 x Xiegu G90 (20W HF TRX) one as portable Radio. Also TS-790E (40 W) for VHF/UHF with X-50 vertical and Duoband 4-Element LPDA.
- IW3HMH
- Site Admin
- Posts: 2927
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: Wrong country parse
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...
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