locked Re: "Any Digital Mode" and Wanted Zone


Joe Subich, W4TV
 

What does the QSO in question show? Is the
"APP_DXKeeper_EQSL_QSL_RCVD" set but the "AG" field does not indicate
they are AG (I don't know its exact name without looking)? If they are
not "AG" surely EQSL_QSL_RCVD should not be set. Or does DXKeeper now
flag non-AG QSL as EQSL_QSL_RCVD?
<App_DXKeeper_EQSL_RCVD> is 'Y' because the QSO has been confirmed in
eQSL.

<APP_DXKeeper_EQSL_MEMBER> is "Y" because the station is an eQSL member
but has not supplied the necessary documentation for AG status. If the
station would supply the documentation, <APP_DXKeeper_EQSL_MEMBER>
would be "A".

The problem is the eQSL confirmation is not valid for WAZ because the
station is not AG.

DXKeeper has always identified *all* eQSL confirmations as EQSL_QSL_RCVD
= 'Y' consistent with ADIF. DXKeeper only *counts* eQSL confirmations
if EQSL_MEMBER = 'A'.

73,

... Joe, W4TV


On 2021-03-16 11:31 PM, HamApps Support (VK3AMA) wrote:
On 16/03/2021 10:07 am, Joe Subich, W4TV wrote:
On second look ... DXKeeper is correct.  The eQSL confirmation is
by a station that it *NOT AG*. This it doesn't count for CQ WAZ.

Are you checking the "eQSL.cc member" field in DXKeeper for "A"
(AG status)?

73,

   ... Joe, W4TV
No.
The presence or non-presence of a "eQSL (AG)" field in any of the supported loggers is not checked. A station can be eQSL(AG) but not have confirmed the QSO. JTAlert looks for an eQSL specific confirmation field in the log. In the case od DXKeeper, it is the "APP_DXKeeper_EQSL_QSL_RCVD" field.
What does the QSO in question show? Is the "APP_DXKeeper_EQSL_QSL_RCVD" set but the "AG" field does not indicate they are AG(I don't know its exact name without looking)? If they are not "AG" surely EQSL_QSL_RCVD should not be set. Or does DXKeeper now flag non-AG QSL as EQSL_QSL_RCVD?
de Laurie VK3AMA

Join Support@HamApps.groups.io to automatically receive all group messages.