[Dx4win] Bug when importing from LOTW
Hello! If stations from Russia has added their oblast in LOTW, those from Moscow (MA) or Moscow region (MO) will in DX4WIN sometimes be added as MA zone 5 or MO zone 4, respectively. Thus it seems like if there is an abrevation that is the same as an US state it will be entered in the state field and the CQ zone of that state will be added, independent of country prefix. This has also true for one VK6 stations (WA) and and one BY4 stations (SD). I have attached a copy of a record from LOTW that afte import to DX4WIN turns up as: Perfix UA State MO Zone 4 It is not all imported records that have this effekt. The second record (R3AG) did not add MA to the State field. I am using DX4WIN 8.05 on a Lenovo Thinkpad X201 with Windows 7. 73 de Mel - SM0MPV 8S0C - Contest Call APP_LoTW_OWNCALL:48S0C STATION_CALLSIGN:48S0C CALL:6UA3DSS BAND:320M FREQ:814.18500 MODE:3SSB APP_LoTW_MODEGROUP:5PHONE QSO_DATE:820120324 TIME_ON:6135257 QSL_RCVD:1Y QSLRDATE:820140922 DXCC:254 COUNTRY:15EUROPEAN RUSSIA APP_LoTW_DXCC_ENTITY_STATUS:7Current PFX:3UA3 APP_LoTW_2xQSL:1Y CQZ:216 ITUZ:229 GRIDSQUARE:6KO85sk STATE:2MO eor APP_LoTW_OWNCALL:48S0C STATION_CALLSIGN:48S0C CALL:4R3AG BAND:320M FREQ:814.17004 MODE:3SSB APP_LoTW_MODEGROUP:5PHONE QSO_DATE:820110514 TIME_ON:6124019 QSL_RCVD:1Y QSLRDATE:820140921 DXCC:254 COUNTRY:15EUROPEAN RUSSIA APP_LoTW_DXCC_ENTITY_STATUS:7Current PFX:2R3 APP_LoTW_2xQSL:1Y CQZ:216 ITUZ:229 GRIDSQUARE:6KO85tt STATE:2MA eor __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Dx4win] Bug when importing from LOTW
That's correctly formatted ADIF - the Russian Oblast code is put into the STATE field, which is overloaded for entities like Canada (province codes), Russia (Oblasts), Mexico (States), Argentina, Brazil, etc. STATE:n is used for all of those. See http://www.adif.org/304/ADIF_304.htm#Primary_Administrative_Subdivisions for a list of entities with these. The LoTW site recently started putting this information into it's ADIF exports, when the station that you worked supplies this information in their station location. This addition has apparently tripped up some applications that think STATE:n means US State. That's not the case. 73, -Rick On Thu, Sep 25, 2014 at 2:58 AM, Mel SM0MPV sm0...@ssa.se wrote: Hello! If stations from Russia has added their oblast in LOTW, those from Moscow (MA) or Moscow region (MO) will in DX4WIN sometimes be added as MA zone 5 or MO zone 4, respectively. Thus it seems like if there is an abrevation that is the same as an US state it will be entered in the state field and the CQ zone of that state will be added, independent of country prefix. This has also true for one VK6 stations (WA) and and one BY4 stations (SD). I have attached a copy of a record from LOTW that afte import to DX4WIN turns up as: Perfix UA State MO Zone 4 It is not all imported records that have this effekt. The second record (R3AG) did not add MA to the State field. I am using DX4WIN 8.05 on a Lenovo Thinkpad X201 with Windows 7. 73 de Mel - SM0MPV 8S0C - Contest Call APP_LoTW_OWNCALL:48S0C STATION_CALLSIGN:48S0C CALL:6UA3DSS BAND:320M FREQ:814.18500 MODE:3SSB APP_LoTW_MODEGROUP:5PHONE QSO_DATE:820120324 TIME_ON:6135257 QSL_RCVD:1Y QSLRDATE:820140922 DXCC:254 COUNTRY:15EUROPEAN RUSSIA APP_LoTW_DXCC_ENTITY_STATUS:7Current PFX:3UA3 APP_LoTW_2xQSL:1Y CQZ:216 ITUZ:229 GRIDSQUARE:6KO85sk STATE:2MO eor APP_LoTW_OWNCALL:48S0C STATION_CALLSIGN:48S0C CALL:4R3AG BAND:320M FREQ:814.17004 MODE:3SSB APP_LoTW_MODEGROUP:5PHONE QSO_DATE:820110514 TIME_ON:6124019 QSL_RCVD:1Y QSLRDATE:820140921 DXCC:254 COUNTRY:15EUROPEAN RUSSIA APP_LoTW_DXCC_ENTITY_STATUS:7Current PFX:2R3 APP_LoTW_2xQSL:1Y CQZ:216 ITUZ:229 GRIDSQUARE:6KO85tt STATE:2MA eor __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html -- Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
[Dx4win] MORE LOTW CONFIRMATIONS
On Tuesday I posted a question on this reflector concerning how to upload LoTW confirmations from DX4Win to ClubLog. Thanks to John 5B4AHK I have the solution. All one has to do is, when you have downloaded the lotwreport.adi file following an upload to ARRL, and imported that into DX4Win. You then upload that same ADIF file to ClubLog and BINGO! I tested it by doing a clean whole-log upload to CL which contained three recent particular unconfirmed QSOs with VK9NT on 12m, ZD9XF on 80m and HC2AO also on 80m, all new band slots. I checked that these Qs were just showing Worked in CL. Then I did a normal export to LoTW from DX4W. After waiting a couple of hours, hoping that some confirmation would ensue, I requested the lotw report and downloaded that into DX4W. These three QSOs were confirmed now both on LoTW and in DX4W. I then uploaded the same report file to CL and again waited a short while for processing. When I received the upload advice from CL I looked at my DXCC chart on CL and there they are. Simples as they say. 73 Andy G3SVD __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
