[Dx4win] IOTA Checkin DX4WIN 9.01

[Jim Reisert AD1C]

Paul has added a feature to 9.01 to check the IOTA field for all QSOs.
It does a few things:

1.  Assigns the appropriate IOTA for QSOs made with a DXCC entity that
is fully contained in a single IOTA group, like Barbados, 8P (IOTA
NA021)

2.  Assigns the IOTA Island for any IOTA that has only one island,
like Barbados, 8P (NA021).  Note that this will also occur when
importing a log from another program.

3.  Checks that the DXCC entity for the QSO is appropriate for the
IOTA assigned.  For example, NA021 (Barbados) is not a value IOTA for
a QSO with Puerto Rico, KP4.  Note that for USA IOTA, DX4WIN also
checks that the STATE is valid for that IOTA.  For example, NA065 is a
valid IOTA for WA, but not for FL.

The IOTA check will not modify any IOTA fields that are already set.
Instead, DX4WIN will report any errors in your log (see below).

You can run the check as follows:

    QSO | Multiple QSO Operations | Check IOTAs

You will get a prompt like the following:

    Checking IOTA and Island for 153811 QSOs
    Are you sure

Click Yes and run the check.  Then you may see a window like the following:

    80 IOTAs were set
    4096 IOTA Islands were set
    14 Invalid IOTAs were reported
    No Invalid Islands were reported
    Look for IOTAMSG: in the QSO notes

Here is an example:

    OE4VIE/ANT in Austria, OE
    IOTA = AN016, Antarctica
    IOTAMSG: Bad IOTA

At one point, the DX4WIN country file thought that OE4VIE was in
Antarctica due to the /ANT at the end.  However, he was just in
Austria.  At the time, I must have added the AN016 IOTA.  Now the IOTA
checker reports that this is in error.

Here is another example:

    K3AEB in PA (Pennsylvania)
    IOTA = NA069
    IOTAMSG: Bad IOTA

This is a bad IOTA.  Pennsylvania does not have any IOTA groups.  What
appears to have happened here is that I worked K3AEB in December 1997
when he was on Sanibel Island, FL.  When I worked him again during the
PA QSO party in October 2000, DX4WIN auto-populated the IOTA field
from the previous QSO.  That of course was not correct for this case,
and I did not notice it at the time of the 2000 QSO.

The IOTA prefix/state database was generated by my software, but I
have had to make some tweaks by hand.  For example, EU016, EU090,
EU110 and EU136 were in YU, Yugoslavia before Croatia became a
separate DXCC entity.  OC148 was previously in the deleted DXCC entity
of Portuguese Timor, but is now part of the Timor-Leste DXCC entity.
The RSGB IOTA database only has the current DXCC entity for each IOTA,
so I had to add the old prefixes by hand.

If you find any IOTAMSG that you believe are incorrect, please send me:

1.  Full callsign
2.  IOTA you think it should be
3.  DXCC entity (Prefix) that your log says for that QSO
4.  If USA, the State that your log says for that QSO

I'll make the necessary changes in the next release of the IOTA mapping file.

73 - Jim AD1C

-- 
Jim Reisert AD1C, <jjreisert at alum.mit.edu>, http://www.ad1c.us