[Dxbase] State field in ADIF

[Neal Campbell]

The standard has a lot of stuff that we will not include as I imagine no
logger (except maybe Dave's) does them all as it is meant to cover all
difffernt types of logging programs  (it would create a log form the size of
Texas to cover everything) but it seems pretty logically specified for what
I want DXB to do. Since seeing it in action over the past 6 months I have a
lot more enthusiasm for its process and the result seems pretty good.

73
Neal Campbell
Abroham Neal Software
www.abrohamnealsoftware.com
(540) 645 5394 NEW PHONE NUMBER

Amateur Radio: K3NC
Blog: http://www.abrohamnealsoftware.com/blog/
DXBase bug reports: email to cases at dxbase.fogbugz.com
Abroham Neal forums: http:/www.abrohamnealsoftware.com/community/





On Tue, Mar 23, 2010 at 3:14 PM, Jack <lennoxj at bellsouth.net> wrote:

> Yes, I suspected the newer ADIF publications must have changed some things.
> It's unfortunate that the group elected to redefine existing fields thereby
> making past implementations subject to fail.  This hobby is riddled with
> loosy goosy standards that tend to be violated over and over again making
> automated support a constantly moving target... lol ...
>
> Jack
>
> ----- Original Message -----
> From: "Dave AA6YQ" <aa6yq at ambersoft.com>
> To: "DXBase Reflector" <dxbase at mailman.qth.net>
> Sent: Tuesday, March 23, 2010 2:52 PM
> Subject: Re: [Dxbase] State field in ADIF
>
>
> >>>>AA6YQ comments below
> >
> > -----Original Message-----
> > From: dxbase-bounces at mailman.qth.net
> > [mailto:dxbase-bounces at mailman.qth.net]On Behalf Of Jack
> > Sent: Tuesday, March 23, 2010 9:59 AM
> > To: George Harlem W1EBI; 'DXBase Reflector'
> > Subject: Re: [Dxbase] State field in ADIF
> >
> >
> > George,
> >
> > This is interesting to say the least.  The ADIF specification which
> DXbase
> > 2007 was coded to identifies the "STATE" field in ADIF to be the "US
> > State".
> >
> > If the ADIF specification has changed to now use the "STATE" field for a
> > Russian State, I would suggest there is a problem.  How would any import
> > program know that when the STATE field lists NV, that it is NOT a US
> State
> > but instead is some other non US entity?
> >
> >>>>By inspecting DXCC field, which identifies the QSO's DXCC entity. If
> the
> > DXCC field specfies "United States", "Alaska", or "Hawaii", then STATE
> > specifies a US State. If the DXCC field indidcates "Canada", then STATE
> > specifies a Canadian province. If the DXCC field specifies "Japan", then
> > STATE specifies a Japanese Prefecture. etc.
> >
> >>>>The generalization of STATE and COUNTY from "US State" and "US County"
> >>>>to
> > "Primary Administrative Subdivision" and "Secondary Administrative
> > Subdivision" respectively was completed in ADIF 2.1.5, which was approved
> > by
> > the ADIF development community in September 2004.
> >
> >    73,
> >
> >        Dave, AA6YQ
> >
> > ______________________________________________________________
> > 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
> >
>
>
> ______________________________________________________________
> 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
>