This is a near impossible task! All of the examples cited thus far (VK, ZL, G, TK) are all countries that have more than one IOTA reference associated with them. eg TK given below covers FOUR different IOTAs! "G" is the same.
However there are in fact 104 DXCC entities that count for one,and only one, IOTA reference. These are listed in the IOTA directory. These could be cross referenced in a database. That just leaves 231 countries that between can count for over 900 IOTAs! 73 Fred G4BWP ----- Original Message ----- From: "FireBrick" <[EMAIL PROTECTED]> To: "DX Base Mailing List" <[email protected]>; "Peter Dougherty" <[EMAIL PROTECTED]> Sent: Thursday, August 01, 2002 12:06 PM Subject: Re: [DXBase] IOTA Questions Correction > I think there is a database problem here. > As the IOTA numbers are incorporated in the log database or .mdb file, it > would take an Import option. > Someone would have to periodically update a file with known operation > Callsigns and their IOTA designations. > The file would have to be date/time specific to handle the situations where > one day W9OL/P was on one island and the following day he was on a different > rock. > Maybe a programmer can see a way around this but this could really create a > mess. > > Then an import feature would have to be implemented to search your log for > these entries and fill in any IOTA data. (If there was such a feature my > IOTA number would jump dramatically) :-) > > In the event that you work TK1XX, (just an example) which would be Corsica > for example and all operations from the TK prefix would count for an IOTA, > that issue may be easier to accomplish. > > I don't believe any of the callbooks provide IOTA data for base calls such > as TK1XX. If any do that would make the issue easier. > > Presently DXB does fill IOTA info into the log if it's provided in a Cluster > spot. (you must have this feature implemented in the log preferences). > > > ----- Original Message ----- > From: "Peter Dougherty" <[EMAIL PROTECTED]> > To: "DX Base Mailing List" <[email protected]> > Sent: Wednesday, July 31, 2002 10:52 PM > Subject: [DXBase] IOTA Questions Correction > > > > I originally wrote: > > > > >NZ, the British Isles, etc, where the entire DXCC entity is one single > > >IOTA reference. > > > > OK, I just gave two *really bad* examples there...just realized it after I > > hit SEND (he says with a very red face...) Sorry. > > > > I think I should have said any log entry for England (for example) should > > auto-populate as EU005, Australia OC001, etc. > > > > >Of course, for entities where there's any ambiguity at all, it could > > >easily be left blank--but considering the number of entities that are > > >their own IOTA, I don't see why that functionality is missing. > > > > - pjd > > > > _______________________________________________ > > DXBase Reflector - Please visit us on the web at www.dxbase.com > > - - - - - - - - - - - - - - - - - - - - - - - > > To UNSUBSCRIBE please visit: > > http://mailman.qth.net/mailman/listinfo/dxbase > > > > > > > _______________________________________________ > DXBase Reflector - Please visit us on the web at www.dxbase.com > - - - - - - - - - - - - - - - - - - - - - - - > To UNSUBSCRIBE please visit: > http://mailman.qth.net/mailman/listinfo/dxbase >
