[Dxbase] State field in ADIF

[George Harlem W1EBI]

Jack, I don't claim to be at all familiar with ADIF specs, but I initially
posted to the N1MM reflector and a couple of group members indicated that
the spec for that field is not limited to a US state:
=========================================

RE: [N1MM] RDXC - Oblast is not a State 

According to ADIF specification STATE is NOT just "US state":

STATE is the code for the contacted station's
Primary Administrative Subdivision (e.g. US State, JA Island, VE
Province)

I think N1MM is working properly.

Regards &73!
Andrei, de ZL1TM
________________________________
> To: N1MMLogger at yahoogroups.com
> From: w1ebi at ...
> Date: Sun, 21 Mar 2010 23:33:35 +0000
> Subject: [N1MM] RDXC - Oblast is not a State
>
> The ADIF exported in 10.3.4 shows each Russian oblast as , which puts lots
of
MA and MO, etc., in the log as U.S. states. Can't that be changed to as part
of
the exchange so it does not get saved in DXbase or other archive logging
programs as a U.S. state? This did not occur in earlier N1MM releases with
RDXC
logs.
>
>
>
> George W1EBI

-----Original Message-----
From: Jack [mailto:lennoxj at bellsouth.net] 
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?

If what you indicate is true, I don't have any suggestions for resolution 
except to say that the ADIF rules need to be examined.  Perhaps there is 
more to this story that sheds light on things, but on the surface, the ADIF 
standard is flawed.

Regards,
Jack

----- Original Message ----- 
From: "George Harlem W1EBI" <w1ebi at lightband.com>
To: "'DXBase Reflector'" <dxbase at mailman.qth.net>
Sent: Monday, March 22, 2010 11:55 PM
Subject: [Dxbase] State field in ADIF


> After importing my log from the Russian DX Contest, I noticed that many
> Russian oblasts have two-letter abbreviations that are identical to some 
> US
> states (e.g., IN, KS, MA, MO, NV).  The current version of N1MM Logger
> correctly includes these in the ADIF field, <STATE:2>, which applies to 
> the
> political entity of the station.  However, DXbase assumes that a "state" 
> is
> only one of the 50 U.S. states, so I had to edit my log by deleting each
> instance of an oblast appearing to be Indiana, Kansas, etc.
>
> I am told that the <STATE> field, per ADIF spec, is not unique to U.S.
> states.  Can DXbase-Next be amended so that this field is imported only if
> the callsign prefix is K, KH6 or KL7?  Of course, a Russian DXbase user
> might then object...
>
> George W1EBI
>
> ______________________________________________________________
> 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
>