[Fourlanders] Fourlanders Digest, Vol 199, Issue 1

[John Ackermann N8UR]

Hi Bob --

Yes, you can.  The problem is when you're trying to see what grids
you've worked, but not confirmed.  From the LoTW data you can't tell the
grid of an unconfirmed station, even if you logged it during the QSO.

My cunning plan is to pull out the data for all unconfirmed 6M QSOs,
sort by call and delete duplicate records, then run a match of the call
vs. QRZ which will tell me at least the home grid for the station.  If
it's one I haven't confirmed, I can then send them a QSL and hope for
the best.  It's possible this could miss some rovers or portable
operations, but it's a start.

73,
John
----

On 10/7/19 12:13 PM, P.T. Corners (Bob) wrote:
> Hi John,
> 
> I believe if the other party has confirmed your QSO on LoTW, then you
> can get the other party's grid square.
> 
> Login to LoTW.  Access the 'Your QSOs' tab.
> Click on 'Most Recent QSLs' link.
> For a particular QSO, click on the 'Details' link.
> 
> Example:
> 
> 
> *Station*
> *Call Sign* 	  	K4VBM
> *DXCC* 	  	UNITED STATES OF AMERICA (291)
> *CQ Zone* 	  	05
> *ITU Zone* 	  	08
> *Grid* 	  	EM73VX
> *State* 	  	Georgia (GA)
> *County* 	  	Gwinnett
> *Worked Station*
> *Worked* 	  	CR3DX
> *DXCC* 	  	MADEIRA ISLANDS (256)
> *CQ Zone* 	  	33
> *ITU Zone* 	  	36
> *IOTA* 	  	AF-014
> *Grid* 	  	IM12JU
> *Date/Time* 	  	2019-09-28 20:33:05
> *Mode* 	  	RTTY (DATA)
> *Band* 	  	20M
> *Frequency* 	  	14.08000
> *QSL* 	  	2019-10-07 14:24:16
> <https://lotw.arrl.org/lotwuser/qsodetail?qso=1086160642>
> 
> 
> Bob
> K4VBM (Very Bad Memory)
> 
> 
> On 10/7/2019 12:00 PM, fourlanders-request at contesting.com wrote:
>> Send Fourlanders mailing list submissions to
>> 	fourlanders at contesting.com
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> 	http://lists.contesting.com/mailman/listinfo/fourlanders
>> or, via email, send a message with subject or body 'help' to
>> 	fourlanders-request at contesting.com
>>
>> You can reach the person managing the list at
>> 	fourlanders-owner at contesting.com
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Fourlanders digest..."
>>
>>
>> Today's Topics:
>>
>>    1. Re: [flatfoot_list] Grid on qsl card? (John Ackermann N8UR)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Mon, 7 Oct 2019 11:29:15 -0400
>> From: John Ackermann N8UR <jra at febo.com>
>> To: flatfoot_list at lists.febo.com, Fourlanders
>> 	<fourlanders at contesting.com>
>> Subject: Re: [Fourlanders] [flatfoot_list] Grid on qsl card?
>> Message-ID: <f5c4546c-3d11-9114-4205-6713a7a90266 at febo.com>
>> Content-Type: text/plain; charset=utf-8
>>
>> Some of you know that I've been trying to reconstruct my log records for
>> 6M operations from Beaver Island.  Over the years I used several
>> computers for logging and *thought* that by uploading to LoTW I would
>> have all the info I need.
>>
>> Turns out that's not the case.  Basically, you cannot retrieve from LoTW
>> the other station's information like state or gridsquare, even if you
>> included it in your upload record.  So to find out what grids I've
>> worked but not confirmed isn't easy.
>>
>> To make a start on the problem, I decided to torture myself a little and
>> wrote a Python 3* program to download LoTW data and munge it to at least
>> find out what I'm missing.  The program allows a fair number of
>> selection and sorting options, so you can do things like select DX-only
>> 6M QSOs that are confirmed but lack a gridsquare, or all unconfirmed 6M
>> QSOs between 01-01-2010 and 12-31-2012.
>>
>> I wrote it under Linux but there's no reason it shouldn't work under
>> DOS/Windows as well if you install Python 3.  It is strictly
>> command-line at the moment.  Under either OS it requires a handful of
>> easy-to-find library modules that you'll need to install.
>>
>> The program and README file are at: https://github.com/n8ur/lotw_tool
>>
>> Share and enjoy!
>>
>> 73,
>> John
>>
>> * Note -- as I have learned to my pain, Python 3 is a lot different
>> (read harder) than Python 2.  But since it's what all the cool kids are
>> using, I decided I should use it and get at least part way down the
>> learning curve.
>>
>>
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> Fourlanders mailing list
>> Fourlanders at contesting.com
>> http://lists.contesting.com/mailman/listinfo/fourlanders
>>
>>
>> ------------------------------
>>
>> End of Fourlanders Digest, Vol 199, Issue 1
>> *******************************************
> 
> 
> _______________________________________________
> Fourlanders mailing list
> Fourlanders at contesting.com
> http://lists.contesting.com/mailman/listinfo/fourlanders
> Sent to: jra at febo.com
>