grid qth origin?
Joe
I note that the Rwanda dxpedition FT8 QSOs I log initially show up in JTAlert (or on WSJTX) as from grid KI58, but when they are logged in DXKeeper they are changed to KI47ts, which is what QRZ shows for them. This, of course, causes the contact to fail the worked before test unless I have the "Ignore Grid..." boxed checked in JTAlert settings. My questions are (a) does JTAlert provide grid information to DXKeeper when it requests the QSO to be logged (may be a question for Lauren), and (b) if so, does DXKeeper overwrite this information when it looks up the contact in QRZ (my callbook option)? Seems like the answers are yes and yes, but...
Joe/WQ6Q |
|
Dave AA6YQ
+ AA6YQ comments below
I note that the Rwanda dxpedition FT8 QSOs I log initially show up in JTAlert (or on WSJTX) as from grid KI58, but when they are logged in DXKeeper they are changed to KI47ts, which is what QRZ shows for them. This, of course, causes the contact to fail the worked before test unless I have the "Ignore Grid..." boxed checked in JTAlert settings. My questions are (a) does JTAlert provide grid information to DXKeeper when it requests the QSO to be logged (may be a question for Lauren), and (b) if so, does DXKeeper overwrite this information when it looks up the contact in QRZ (my callbook option)? Seems like the answers are yes and yes, but... + When importing a QSO record from an external application like JTAlert, DXKeeper never replaces information in that record. + If when sending a QSO record to DXKeeper, an external application specifies that DXKeeper should look for an Override, then if DXKeeper finds an override for the QSO record's callsign, it will update the QSO record's location fields with the location information in that Override. 73,
|
|
Dave AA6YQ
The first statement below should have been "When importing a QSO record from an external application like JTAlert, DXKeeper never replaces information in that record with information from a callbook lookup"
|
|
Joe
Got it!
Thanks, Dave... Joe/WQ6Q |
|