Forum Replies Created
Per the TQSL release notes as of version 2.5.3 (April 2020):
Ignore leading and trailing whitespace in ADIF values.
Ignore callsign fields (OPERATOR, STATION_CALLSIGN, OPERATOR_CALLSIGN) in ADIF files to work around defective logging programs.
When a Station Location has empty values, use the QTH details from the log being signed.December 22, 2017 at 13:56 in reply to: K0BAK incorrect refrence/P2P, incorrectly attributed activation #7316
Thank you Manfred. The first archived spots I see on DXFuncluster for NPOTA RS01 (KFF-0664) are from March 2016 and after, which sounds reasonable for snowy Idaho. I worked 8 unique NPOTAs that day so figuring out the correct reference from spots is not likely. The only way to solve this mystery may be to contact one of the ops in the log and ask who they worked. 🙂
Correction, QSO time for W0ZAP is 1828z. Mode should still be SSB.
Perhaps I am not asking the right questions. Let’s try this a different way.
Please check the database for QSOs made by activator K0ATZ on Sept. 30 2016 between the times of 15:20z and 16:57z (90 QSOs).
And also Dec. 31 2016 between the times of 01:19z and 17:03z (202 QSOs).
If these QSOs exist in the database and are listed as activation of any reference other than KFF-4009 then there is an error.
Complete logs can be provided on request.
Log uploaded successfully, no errors. Thanks!
Thank you Andrew. NPOTA Qs have been uploaded without issue.
Thank you for taking time to look at this Andrew,
As I understand the situation NPOTA RV05 was assigned as KFF-4009 only recently. K0ATZ sent me the above NPOTA log files for RV05 when he noticed that it had been assigned a KFF number (May 22) but when I tried to upload them the system informed me that logs with those names had already been uploaded.
The thinking was that perhaps these got uploaded earlier with a batch of NPOTA logs and assigned to another reference for whatever reason. K0ATZ has related that he believes he has way too many QSOs listed at KFF-3674 and of course none at KFF-4009.
Either someone coincidentally uploaded two unrelated logs with the same file names or there are some Qs somewhere on the wrong reference. I do not have the access level to figure out which is the case, I can only report. 🙂
These logs were submitted by a top tier NPOTA activator in good faith. Please rectify this situation.
It has been requested by activator Pete Kobak K0BAK to verify that all band strings specified in the ADIF specification are supported by Logsearch:
I don’t see a sense of urgency here. Perhaps I will just upload under different file names and let the chips fall where they may.
Fixed. Thank you gentlemen.