[Dx4win] Problem w/ADIF import from LOTW
--- [EMAIL PROTECTED] wrote: > How does one update the State & County fields while importing a ADIF from > LOTW. When using the > demo version I could upload these same ADIF files and the fields would > populate just fine. Is there a setting that I'm missing? Hi Ted, There are several import options, the two more important of which are: - import only updates UPLOAD CONFIRMED flag - import replaces existing QSOs I believe the second option will fill in those fields, the first will NOT. Be advised that MANY folks have uploaded incorrect station information to the LoTW site. A common mistake is to have the CQ and ITU zones swapped. It's possible that Paul may enhance this function in the future. 73 - Jim AD1C Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.us From [EMAIL PROTECTED] Thu Mar 10 10:15:35 2005 From: [EMAIL PROTECTED] (Tony Lord) Date: Thu Mar 10 10:15:28 2005 Subject: [Dx4win] Awards Count In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Hi all, May I ask as dumb question? As I make QSO's and then, as I send and receive QSL, marking up the QSL cards in DX4WIN, will the software automatically tell me when I have reached the threshold for an award?? i.e. when that last vital QSL card arrives, does the software pop up and say, HEY you've reached such and such a level for DXCC?? Or do I have to make a manual check from time to time?? Regards & 73's de Tony G8DQZ
[Dx4win] APPNOTE: Why do we have callsign exceptions?
Periodically I will write something about the country files. If you find these useful, let me know and I'll write more, especially if you have a topic in mind. I'll try to post these somewhere on my web site: http://www.ad1c.us/dx4win/ Today's topic: Why do we have callsign exceptions? In an ideal world, the ITU prefix (http://life.itu.int/radioclub/rr/ap42.htm) would fully specify the location of a callsign. However, we do not live in an ideal world. Many prefixes are unique to a particular entity: DL4, J3, VK5 to name a few. However, many are not: 3D2, CE0, FO0, JD1, VP8, the list goes on. One can pick a standard default, i.e. 3D2 is more likely to be Fiji than Rotuma or Conway Reef. However, when a 3D2 call is used from one of those two entities, it must be added to the exception list. Prefixes change over time. Lesotho, 7P used to be ZS8. Palmyra, KH5 used to be KP6. In the first case, ZS8 was reclaimed by South Africa and now is used only from Marion Island. In the second case, no KP6 calls have been issued since the switch, but they could be. Sometimes a prefix is used past its expiration date. Take KX6 for example. Stations in the Marshall Islands began using the new V7 prefix in September, 1978. However, a number of KX6 stations remained on the air into the late 1980s. During the 1980s, the FCC began issuing 2x1 KX6 callsigns to stations in the 6th call area. Sure, a 2x2 callsign is most likely Marshall Islands, but coding up each special case in software makes it harder to make changes down the line. Sometimes the prefix doesn't tell you everything about the entity. For example, many 4K1 callsigns were used from Antarctica, KC4 in CQ Zone 39. But some were used from zones *other than* zone 39, and some were used from other Antarctic island like South Shetlands, VP8/H. The following is a list of the conditions when a callsign exception is needed: 1. The prefix is ambiguous - here is a list of some common ones: 3D2, 3Y, 4U, CE0, CE9, FO, GB, HK0, JD1, KC6, PY0, SV0, TO, TX, VK0, VP8, ZK1 Sometimes this affects only the CQ zone and not the entity. For example there are a number of different prefixes used in Antarctica, KC4. Some prefixes are only used from a particular CQ zone, for example FT5Y and ZL5 are both in CQ zone 30. However, some prefixes like VK0 or VP8 can be used from any of the following CQ zones: 12, 13, 29, 30, 32, 28 or 29. 2. The callsign is used from more than one location. For example, VK9ZR has been used from both Willis Island and Mellish Reef. 3. The callsign isn't correct for the entity. For example, there are a number of folks who moved to the states (lower-48 USA) but kept their KH6 or KL7 callsigns. 4. The callsign uses a portable designator that may not be a valid prefix. For example, a number of Israeli's signed /SK in 1998 - SK is typically a prefix for Sweden! Sometimes the portable designator changes the entity, for example RZ3BY/0 is in Asiatic Russia, UA9 not European Russia, UA. Or the portable designator can change the CQ Zone, for example VE3EXY/2 operated from CQ Zone 2. 5. The callsign uses an old prefix, even after a new prefix has been issued. Many of the old Russian calls had this problem, like 4K2 stations operating from Franz Josef Land in 1994. 6. The callsign uses a portable designator that is the same length as the callsign. Normally the shorter part contains the DXCC entity prefix, for example SV9/HA0HW/P. However, what if there is no shorter part? Take this callsign: N6YA/VP2A. You can look at it and probably determine that it's Antigua, V2. But what about this callsign: VP2A/N6YA. It's also probably Antigua, but how can the computer tell that these two callsigns are both for the same entity? Software has to consistently pick first or second, leaving the rest to be taken care of by callsign exceptions. A number of visitors to Chinese club stations have this problem, i.e. OH2BH/BY1PK or W8JAY/BY4AA. Sometimes a tweak to the prefix mappings can compensate for a special callsign. However, this must be weighed against how that prefix may be used in the future. For example, even though "NLD" would be a prefix for USA (if that was even used), it's more typically used by Kuwait during their annual "National Liberation Day" celebration. Therefore, adding the single prefix mapping for NLD to 9K can save a number of callsign exception mappings. However, "SK" is commonly used in Sweden, so adding "SK" as a prefix mapping for Israel in 1998 would not have been such a good idea. Ideally, the list of callsign exceptions should stabilize over time. Eventually, but maybe not in my lifetime, all the old exceptions will be understood, and only new ones for current/future operations will be added. However, the people who have worked these problematic callsigns may not use DX4WIN, so collecting
[Dx4win] Printing QSL Cards
Hello All, I have mentioned this before but I need to print some of my QSL cards with QSO specific notes. I still don't know if this is being considered as a new feature. I wish someone at DX4WIN would let me know. In the mean time, does anyone know of a good QSL card printing program or other logging program that I could use to print some of my contacts with notes? I am visually impaired so hand writing the additional information is not a good solution. Thanks for your help. David
[Dx4win] Newbie Questions: DX4Win + LoTW
After lots of procrastinating, I've finally gotten my act to use LoTW. I have logs for 5 different US callsigns. My questions are: - In doing card submissions./checks, DX4Win was apparently configured to not flag any of the DXCC categories (mixed, band. mode). Do I need to fiddle with any of those settings? After I submit to LoTW, are those flags (and stats) reset? How? - I assume I only upload the DX entries of my log(s). That being the case, how do I extract only those QSOs? Thanks in advance, Eric W3DQ Washington, DC -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.7.1 - Release Date: 3/9/2005
[Dx4win] Printing QSL Cards
I have heard many good things about this one: http://www.df3cb.com/bv/ Will NA2NA telnet://na2na.net an AR-Cluster node - Original Message - From: "David Tingler" <[EMAIL PROTECTED]> To: Sent: Thursday, March 10, 2005 4:36 PM Subject: [Dx4win] Printing QSL Cards > Hello All, > > I have mentioned this before but I need to print some of my QSL cards with > QSO specific notes. I still don't know if this is being considered as a > new > feature. I wish someone at DX4WIN would let me know. > > In the mean time, does anyone know of a good QSL card printing program or > other logging program that I could use to print some of my contacts with > notes? I am visually impaired so hand writing the additional information > is > not a good solution. > > Thanks for your help. > > David > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] Newbie Questions: DX4Win + LoTW
--- Eric Rosenberg <[EMAIL PROTECTED]> wrote: > - In doing card submissions./checks, DX4Win was apparently configured > to not flag any of the DXCC categories (mixed, band. mode). > Do I need to fiddle with any of those settings? > After I submit to LoTW, are those flags (and stats) reset? How? These flags have nohing to do with exporting QSOs. They only have to do with how your DXCC statistics are computed. > - I assume I only upload the DX entries of my log(s). That being the > case, how do I extract only those QSOs? No, you can upload ALL QSOs. Just create a date filter, export those QSOs to an ADIF file, sign it and upload to LoTW web site. LoTW export is just that - it exports QSOs. It doesn't know anything about awards. 73 - Jim AD1C -- Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.us From [EMAIL PROTECTED] Thu Mar 10 18:49:25 2005 From: [EMAIL PROTECTED] (Alan Zack) Date: Thu Mar 10 18:51:48 2005 Subject: [Dx4win] APPNOTE: Why do we have callsign exceptions? In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Jim, Along this line of thought, are there updates to the CTY.DAT files for the KH8SI operation at Swain Island? This is a different IOTA and LAT/LONG than the home KH8 island calls, and MAYBE? (depending on the ARRL) a new country, along the line of the Ducie Island DXpedition. When I log them in DX4WIN the log takes KH8SI as OC077, Amer Samoa, but their web site at http://www.swains-island.org shows their logging program info as: Prefix|Country name KH8/S Swains Island Zone | Start date 32 3-2-2005 Details 11.00 Hours BehindUTC IOTA | ITU | Continent OC-200 63 Oceania Longitude |Latitude 171.05 West 11.05 South GRID AH48LX Jim Reisert AD1C wrote: > Periodically I will write something about the country files. If you find > these > useful, let me know and I'll write more, especially if you have a topic in > mind. I'll try to post these somewhere on my web site: > > http://www.ad1c.us/dx4win/ > > Today's topic: Why do we have callsign exceptions? > > In an ideal world, the ITU prefix (http://life.itu.int/radioclub/rr/ap42.htm) > would fully specify the location of a callsign. However, we do not live in an > ideal world. > > Many prefixes are unique to a particular entity: DL4, J3, VK5 to name a few. > However, many are not: 3D2, CE0, FO0, JD1, VP8, the list goes on. One can > pick > a standard default, i.e. 3D2 is more likely to be Fiji than Rotuma or Conway > Reef. However, when a 3D2 call is used from one of those two entities, it > must > be added to the exception list. > > Prefixes change over time. Lesotho, 7P used to be ZS8. Palmyra, KH5 used to > be KP6. In the first case, ZS8 was reclaimed by South Africa and now is used > only from Marion Island. In the second case, no KP6 calls have been issued > since the switch, but they could be. Sometimes a prefix is used past its > expiration date. Take KX6 for example. Stations in the Marshall Islands began > using the new V7 prefix in September, 1978. However, a number of KX6 stations > remained on the air into the late 1980s. During the 1980s, the FCC began > issuing 2x1 KX6 callsigns to stations in the 6th call area. Sure, a 2x2 > callsign is most likely Marshall Islands, but coding up each special case in > software makes it harder to make changes down the line. > > Sometimes the prefix doesn't tell you everything about the entity. For > example, > many 4K1 callsigns were used from Antarctica, KC4 in CQ Zone 39. But some > were > used from zones *other than* zone 39, and some were used from other Antarctic > island like South Shetlands, VP8/H. > > The following is a list of the conditions when a callsign exception is needed: > > 1. The prefix is ambiguous - here is a list of some common ones: > > 3D2, 3Y, 4U, CE0, CE9, FO, GB, HK0, JD1, > KC6, PY0, SV0, TO, TX, VK0, VP8, ZK1 > > Sometimes this affects only the CQ zone and not the entity. For > example there are a number of different prefixes used in > Antarctica, KC4. Some prefixes are only used from a particular CQ > zone, for example FT5Y and ZL5 are both in CQ zone 30. However, > some prefixes like VK0 or VP8 can be used from any of the > following CQ zones: 12, 13, 29, 30, 32, 28 or 29. > > 2. The callsign is used from more than one location. For example, > VK9ZR has been used from both Willis Island and Mellish Reef. > > 3. The callsign isn't correct for the entity. For example, there are > a number of folks who moved to the states (lower-48 USA) but
[Dx4win] APPNOTE: Why do we have callsign exceptions?
--- Alan Zack <[EMAIL PROTECTED]> wrote: > Along this line of thought, are there updates to the CTY.DAT files for > the KH8SI operation at Swain Island? This is a different IOTA and > LAT/LONG than the home KH8 island calls, and MAYBE? (depending on the > ARRL) a new country, along the line of the Ducie Island DXpedition. > When I log them in DX4WIN the log takes KH8SI as OC077, Amer Samoa, > but their web site at http://www.swains-island.org shows their logging > program info as: It's unlikely to be a new DXCC country. Just populate the IOTA field with OC200 and you'll get the updated bearing/distance. 73 - Jim AD1C -- Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.us From [EMAIL PROTECTED] Thu Mar 10 20:18:30 2005 From: [EMAIL PROTECTED] (Wendell Wyly - W5FL) Date: Thu Mar 10 20:20:55 2005 Subject: [Dx4win] Problem w/ADIF import from LOTW In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Unfortunately, No. It would be a really nice feature to be added to DX4WIN. The choices today are only as follows: 1) Update the qsl status received via LOTW. 2) Replace the entire qso with that uploaded from LOTW which is not a good thing, although it does populate the state, county, country, zone, etc., fields. You would soon learn to check these fields very carefully, before you allowed them to be changed because a LOT of people on LOTW do not know their own information and have it WRONG in LOTW. Just for a quick check, what is your ARRL Zone, CQ Zone, Grid, and if you were DX or on an island IOTA? DX4WIN is a really fine program and these type of neat updates are not without many obstacles. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, March 09, 2005 8:10 PM To: dx4win@mailman.qth.net Subject: [Dx4win] Problem w/ADIF import from LOTW How does one update the State & County fields while importing a ADIF from LOTW. When using the demo version I could upload these same ADIF files and the fields would populate just fine. Is there a setting that I'm missing?
[Dx4win] APPNOTE: Why do we have callsign exceptions?
Yes, this worked fine. Along this line, YB7M was on the air tonight stating they were giving out a new IOTA, OC-268. But when OC268 is typed into the DX4WIN IOTA box it is not accepted. I put it into the NOTES FOR THIS CALL box instead. How does one add a new IOTA to the list? TIA & 73 Jim Reisert AD1C wrote: > --- Alan Zack <[EMAIL PROTECTED]> wrote: > > >>Along this line of thought, are there updates to the CTY.DAT files for >>the KH8SI operation at Swain Island? This is a different IOTA and >>LAT/LONG than the home KH8 island calls, and MAYBE? (depending on the >>ARRL) a new country, along the line of the Ducie Island DXpedition. >>When I log them in DX4WIN the log takes KH8SI as OC077, Amer Samoa, >>but their web site at http://www.swains-island.org shows their logging >>program info as: > > > It's unlikely to be a new DXCC country. Just populate the IOTA field with > OC200 and you'll get the updated bearing/distance. > > 73 - Jim AD1C > > > -- > Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 > USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.us > > -- __ Alan Zack Amateur Radio Station K7ACZ Las Vegas, Nevada, USA Quality Engineer, The Boeing Company, Retired Aviation Chief Warrant Officer, U.S. Coast Guard, Retired U.S. Coast Guard, Always Ready, Always There Every hour, Every day, Around the Clock and Around the World SEMPER PARATUS http://www.gocoastguard.com http://www.uscg.mil/d14/units/asbp/uscgasbp/ DEPARTMENT OF HOMELAND SECURITY
[Dx4win] APPNOTE: Why do we have callsign exceptions?
At 09:02 PM 3/10/2005, Alan Zack wrote: >Along this line, YB7M was on the air tonight stating they were giving out >a new IOTA, OC-268. But when OC268 is typed into the DX4WIN IOTA box it >is not accepted. I put it into the NOTES FOR THIS CALL box instead. How >does one add a new IOTA to the list? File -> Databases -> IOTA. Ctrl-Insert to add a new IOTA, fill in the details. It will be added in my next release. - Jim -- Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.us
