[Dxbase] ADIF Export

Tue Dec 29 19:48:08 EST 2009

Thanks for enlightening me on the ADIF standards changes... Yep, it would 
appear that these tags do address the issue rather well, once implemented. 
Of course, to be effective, both the importing and exporting applicatons 
will need to adopt at least these tags.
Happy New Year everyone...
----- Original Message ----- 
From: "Joe WA6AXE" <wa6axe at hotmail.com>
To: <lennoxj at bellsouth.net>; <n7ws at k6mhe.com>; <dxbase at mailman.qth.net>
Cc: <michael at g7vjr.org>
Sent: Tuesday, December 29, 2009 6:06 PM
Subject: RE: [Dxbase] ADIF Export
Jack,
The ADIF 1.0 standard only had the QSL_RCVD .. and .. yes , now
the ADIF 2.x.x has
QSL_RCVD
EQSL_QSL_RCVD
LOTW_QSL_RCVD
It would appear that if DXbase adopts ADIF 2.x.x that the Selection Wizard's
ADIF Export function could be updated to reflect the new ADIF 2.x.x 
standard --
with each category of confirmation (Card, LoTW, and EQsl) having it's own
adif tags ...
73 Joe wa6axe
> From: lennoxj at bellsouth.net
> To: n7ws at k6mhe.com; dxbase at mailman.qth.net; wa6axe at hotmail.com
> CC: michael at g7vjr.org
> Subject: Re: [Dxbase] ADIF Export
> Date: 2009年12月29日 17:11:39 -0500
>> Maybe something has changed, but last time I researched the applicability 
> of
> the LoTW system maintained by ARRL, the only time an LoTW "confirmation"
> counted was when the user was dealing with an ARRL sponsored award. Maybe
> all ARRL sponsored awards now use LoTW, I don't know, but in the early 
> days
> of LoTW that wasn't the case.
>> As best I know, tracking CQ awards, IOTA awards, and such requires a "QSL
> card" and LoTW in not even part of the equation. Did all that change and
> now LoTW is a direct substitute for any award offered in amateur radio?
>> Just asking, because if that's not the case, then following the suggestion
> offered by Wes may solve his concern over using his club software by way 
> of
> an ADIF export from DXbase, but it would certainly break things for a lot 
> of
> others and distort the current distinction between having a physical card
> versus having an ARRL acknowledged confirmation report.
>> Perhaps the more recent ADIF standards addresses this already somehow, I
> don't know. But, the ADIF standard by which DXbase 2007 was coded uses 
> the
> QSL_RCVD field to reflect physical cards and thereby is universal and not
> ARRL specific. In other words, the QSL_RCVD field is populated exactly as
> the ADIF standard at the time required.
>> In the absence of any clear standards for handling Physical cards versus
> LoTW substitutes, I wonder if a more reasonable approach wouldn't be to
> import the ADIF file from DXbase which would reflect cards only for now, 
> and
> then import your LoTW from ARRL into your other software such as the club
> program mentioned by Wes.
>> Just thinking..... perhaps Neal already has something in mind, but I'm 
> not
> sure a clear solution has yet been put on the table in the discussion so
> far.
>> Cheers
> ----- Original Message ----- 
> From: <n7ws at k6mhe.com>
> To: <dxbase at mailman.qth.net>; "Joe WA6AXE" <wa6axe at hotmail.com>
> Cc: <michael at g7vjr.org>
> Sent: Tuesday, December 29, 2009 1:43 PM
> Subject: Re: [Dxbase] ADIF Export
>>> > Thanks Joe,
> >
> > So nothing's changed between versions. I hope that in any future version
> > this
> > is fixed.
> >
> > VP2E is different from VP2 by any measure and "QSL" means confirmed, not
> > "QSL
> > Card" so the QSL_RCVD field should get populated with "Y" when the QSO 
> > is
> > confirmed by either a card or LOTW.
> >
> > 73,
> >
> > Wes
> >
> >
> > On December 29, 2009 at 1:13 AM Joe WA6AXE <wa6axe at hotmail.com> wrote:
> >
> >>
> >> Wes,
> >>
> >> When exporting with DXbase2007, the <QSL_RCVD:1>N still shows
> >> "N" -- even though the CFM column shows LOTW ... so, it is keying on
> >> a CARD rcvd to make it a "Y" ...
> >>
> >> On the VP2E -- the <PFX:3>VP2 is the WPX column's PREFIX
> >> and the <DXBPFX:4>VP2E is the actual PREFIX column from your
> >> logbook ..
> >>
> >> 73 Joe wa6axe
> >>
> >> > Date: 2009年12月29日 01:01:09 +0000
> >> > From: n7ws at k6mhe.com
> >> > To: dxbase at mailman.qth.net
> >> > Subject: [Dxbase] ADIF Export
> >> >
> >> > Maybe this has been fixed in later versions, but in 2005, there are
> >> > some
> >> > issues
> >> > with the way DXBase exports ADIF.
> >> >
> >> > This has surfaced since I've begun using Clublog (www.clublog.org) 
> >> > for
> >> > some
> >> > tracking purposes. Clublog reads .adi files for its input. I've had a
> >> > lot
> >> > of
> >> > QSOs that fail to show confirmed in Clublog and I've tracked it to 
> >> > the
> >> > fact
> >> > that
> >> > DXB doesn't appear to change the QSL_RCVD field to "Y" when the QSO 
> >> > is
> >> > confirmed
> >> > via LOTW. DXB uses a field DXBQSL_RCVD with a numeral instead. This 
> >> > is
> >> > unrecognized by Clublog, and I suspect a lot of other programs.
> >> >
> >> > Another issue I noted was that QSOs with VP2E show PFX = VP2 when
> >> > exported.
> >> >
> >> > Has this stuff been fixed in later versions or will it be if a new
> >> > version
> >> > is
> >> > offered?
> >> >
> >> > Wes N7WS
> > ______________________________________________________________
> > Dxbase mailing list
> > Home: http://mailman.qth.net/mailman/listinfo/dxbase
> > Help: http://mailman.qth.net/mmfaq.htm
> > Post: mailto:Dxbase at mailman.qth.net
> >
> > This list hosted by: http://www.qsl.net
> > Please help support this email list: http://www.qsl.net/donate.html
>>
_________________________________________________________________
Your E-mail and More On-the-Go. Get Windows Live Hotmail Free.
http://clk.atdmt.com/GBL/go/171222985/direct/01/