Re: Invalid administrative subdivision errors
|
toggle quoted message
Show quoted text
+ AA6YQ comments below
Dave, Thank you and all the others for helping me get my logs transferred to DXLab.? I have one final error to clear up to finish this initial set of log?imports.?
?
This op appears to be from Moscow, Russia, which seems to be ADIF Country Code 54, Oblast 170, CQ zone 17, ITU zone 29, UA3{ABC} per ADIF 3.0.3 Specifications.? It seems like DXKeeper does not like the "district" KR-14.? It would be happy with KR-13 or KR-15 (from the pull-down menu, no KR-14). The ADIF 3.0.3 Specifications link to the RDA List shows:? "KR-14 BELOREChENSK NEW RDA since 01.01.2025." Is it possible that this new KR-14 is missing from DXKeeper?
+ To obtain an updated Secondary Subdivision Database that reflects the RDA List changes made in January, see /g/DXLab/message/227144
+Ordinarily, the updated Secondary Subdivision Database would have been included in a next version of DXKeeper by now, but I'm extending "Realtime Award Tracking" to support pursuit of the new IOTA HF and VHF award categories, which is a significant development effort in both DXKeeper and SpotCollector. + Alternatively, to stop DXKeeper from considering a QSO with inconsistent Primary or Secondary Subdivisions to be "broken", uncheck the "Subdivision validity checking" box in the "Other Awards" panel along the right side of the Configuration window's Awards tab. ? ? ? ? 73, ? ? ? ? ? ? ?Dave, AA6YQ
?
|
