Re: [Trustedqsl-testing] TQSL 2.5.2 and /MM log

[Rick M. <k1...@ar...>]

I've looked at Frank's log. The issue here is that this is a very large
number of station locations, more than what LoTW is expecting.

>From the 3285 QSOs there's 1230 different station locations (from 1117
different Gridsquares).

LoTW allows up to 999 different station locations, and the one that hit the
limit is the EA7ALL QSO. Once you hit 999, then the rest of the QSOs are
using the same station location setup.
I need to work with the HQ staff to get this limit increased.

As far as the duplicate QSOs being discovered, they're interesting. For
example, you have a QSO on 2018/02/27 at 1457 with a station from ML01ox
then another QSO at the same time from ML02oa. Since the time is the same,
TQSL considers this to be a dupe with an unexpected change of QTH. This is
of course incorrect, as this QSO happened across adjacent grids.
It would be better if the log emitted this as a single QSO with
"MY_GRIDSQUARE" set to "ML01ox,ML02oa", but they're counted as "already
uploaded" assuming they're the same QSO.

This probably should be something that TQSL allows - another setting that
indicates that the station roams across gridsquares and therefore grid
changes are to be ignored.

So this ran into a limit and I'll work to get that lifted. Cutting the log
into two pieces will get past that limit.

This has been really helpful in testing this new feature - it's going to
make operations like yours so much easier to handle for LoTW uploads.
73,
    -Rick

On Fri, Feb 28, 2020 at 3:22 PM Rick Murphy <k1...@ar...> wrote:

> Frank,
> The first thing you should look at is the log on the LoTW page that
> describes what actions LoTW took when these logs were uploaded.
> On the LoTW site, choose "Your Account", then "Your Activity".
> Look at the "Result" link for one of your logs; you may see that LoTW was
> rejecting some of these gridsquares. For example, LoTW has rules that
> verify that grids are within the borders of various entities, and it may
> have rejected some of your input.
> 73,
>     -Rick
>
> On Fri, Feb 28, 2020 at 2:52 PM qsl F5MYK <qsl...@or...> wrote:
>
>> Hi Rick & All
>>
>> AA/ My mistake !
>> Thanks a lot for the message with the image.png.
>> I am using a very old version of VQLog and the ADIF exporter writes
>> own_gridsq instead of my_gridsquare.
>> Much better now and very sorry for the inconvenience.
>>
>> May I suggest that if the user chooses "Override Station Location with
>> QTH from the log", TQSL could ensure that the field MY_GRIDSQUARE is used
>> at least for a few records ?
>>
>>
>> BB/ New uploads :
>> For years 2013 up to 2017, logs are less than 2000 QSO and it is OK.
>> It seems that above 2500 lines (2018 & 2019) the upload is more difficult
>> ?
>> I searched in both logs without finding why my_gridsquare is not imported
>> for all ADIF records.
>> 2018 log:
>> Line 1-5 are the ADIF header.
>> Line 6 - 3290 are ADIF records.
>>
>> Line 2671 - EA7ALL - my locator is detailed  NJ35BW
>> Line 2672 - UA3QUP - my locator is missing NJ35CW ?
>> I did not check for all QSO but the DB is populated with the next ~600
>> QSO except for my_gridsquare field ?
>>
>> I tried to find some difference between those lines but saw nothing
>> special but the fact that the GL contains the string 'CW'?
>> In case you need it, I will send this file to your private address. Hope
>> it won't bother you...
>>
>> 2019 log:
>> After a few tries I uploaded the first 5000 lines (only) and the same
>> problem appears around line 2450.
>>
>>
>> 73, Frank
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Trustedqsl-testing mailing list
>> Tru...@li...
>> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing
>>
>
>
> --
> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
>


-- 
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA