I think I found a way to check some of the data fairly easily. 1) Download your LoTW QSL file including details
2) Download your LoTW QSL file excluding details 3) Import both files into separate logs 4) Using your favorite Database/Spreadsheet program compare the 2. I did this and I think I found some of my log errors and corrected them. One of the QSOs I'm still curious about is U1RC from 1992. DXBase wants = the prefix to be UA and the QSL wants the prefix to be UR. I believe it's = UR. Does anyone know for sure? 73, Art W2NRA Art Searle Director of Finance/Treasurer [EMAIL PROTECTED] (631) 730-4084 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] = On Behalf Of William H. Hein Sent: Thursday, May 06, 2004 8:23 AM To: [email protected] Subject: [DXBase] spot filtering;35% of LoTW QSLs have bad QTH data? Thanks for the people who responded to my post about filtering EU VHF = spots. The cluster I use, K1XX, uses DX Spider. I found the DX Spider manual online and am now able to filter out VHF spots not to or from CQ zones = 3,4 or 5 with a few simple commands. Regarding the incorrect QTH data in the LoTW database, I saw the posting below on the LoTW reflector the other day. This person determined that = 1400 or his 4000 LoTW QSLs have bad QTH data (35% error rate, pretty awful). = I have also noticed a lot of similar errors in my own LoTW files (about = 3000 QSLs from the 95,000 QSOs I've uploaded), but haven't tallied the = figures. I strongly recommend that DXBase 2005 users NOT use the LoTW ADIF import feature to update any field other than the LoTW confirmation itself. = Doing so is likely to frequently overwrite good QTH data with bad. 73, Bill NT1y -------------------------------------------------------------------------= -- Date: Wed, 5 May 2004 08:05:05 -0500 From: "FireBrick" <[EMAIL PROTECTED]> Subject: Re: Confirmed Entities so far Funny you mention this. Because just over the weekend I checked my 4k plus LoTW Qsls. Over 1400 = had some instance of incorrect data. Usually misspelled counties, incorrect = ITU zones. Seems that because when you are entering your data for your = original certificate, LoTW asks for ITU zone first and CQ Zone second. I'm pretty sure that was the way it was. I'm betting that a lot of people may have missed that and put them in CQ then ITU. I'm not counting zone discrepancies where a W1 is now living in = California etc. I hope people will check their data and 'Renew' their certificates with = the correct info. _______________________________________________ DXBase Reflector - Please visit us on the web at www.dxbase.com - - - - - - - - - - - - - - - - - - - - - - -=20 To UNSUBSCRIBE please visit: http://mailman.qth.net/mailman/listinfo/dxbase
