If you want a quick fix, use a text editor on your 160 ADIF file and replace all instances of <SECTION with <ARRL_SECT and it should import the state into DxBase correctly.
>Yes, this is essentially what I suggested could be done with an >automated script. HOWEVER, as someone pointed out to me in private >mail, SS imports which too contain only sections, populate the >state. I confirmed that in my DxBase log. My SS and ARRL160 ADIF >files (created by N1MM logger and used for DxBase import) only >contain section information. My DxBase entries for those imported >logs contain states for SS but not for ARRL160. Curious, I went >back and examined previous years' logs. I noticed that some >previous 160 contests had the state information. But I had used CT >for those contests. The problem lies with N1MM. For the logs that >get the state (SS), the ADIF has <ARRL_SECT>, while the logs that do >not get the state (ARRL160), the ADIF has <SECTION>. I will drop a >note to N1MM about this. > > >At 12/14/2007 03:33 AM, Gary Senesac AL9A wrote: >>The state problem is not DXB's import, it is your ADIF file. The >>160M contest exchange (and others) includes SECTION, not >>STATE. Some sections are the same as state abbreviations, but some >>are not - NTX, STX, SFL, NFL, WNY, ENY, WWA, EWA, etc., not to >>mention all of the various CA sections. >> >>I get around this by opening the ADIF file in notepad and use the >>find and replace all as follows: >>Change all <SECTION:2> to <STATE:2>. This will fix all 2 character >>section abbreviations to 2 character state abbreviations. >>Change all <SECTION:3> to <STATE:2>. This will catch the sections >>fields missed by the previous find and replace. >>Find all 3 character sections and replace with their 2 character >>state abbreviations. Include the > bracket in each search string >>to avoid changing some other string in error. For example: >>Change all >NTX to >TX.. >>Change all >WWA to >WA. >>Change all >SJV to >CA. >>Change all >LAX to >CA, etc. >> >>Once all the possible 3 character sections have been changed to >>their equivalent 2 character states save the file and do the >>Non-DXB import. You will see warning messages for the VE's and any >>DX, but they're not states so it doesn't matter. >> >>73, >>Gary AL9A >> >>----- Original Message ----- From: "Rod Greene" <[EMAIL PROTECTED]> >>To: <[email protected]> >>Sent: December 13, 2007 11:39 AM >>Subject: [Dxbase] Import >> >> >>>All, >>> >>>I recently exported records from two contests that I did in N1MM to ADIF, >>>and then imported them into DXB. The first import (for the ARRL 10 Meter >>>contest) worked fine. By saying Fine, I mean all the data was transferred >>>into the correct fields in DXB. However, when I imported the records for the >>>ARRL 160 contest, the "State" information didn't transfer - Except for the >>>two records where I worked Alaska (AK) and Hawaii (HI). For those two >>>records, the State information transferred correctly into DXB. The two ADIF >>>files are very similar but there are some small differences. I used a text >>>editor to make the data in the 160 ADIF file match that of the 10M ADIF. >>>That didn't help and the results were the same, still no transfer of the >>>State information except for those two off-shore contacts. >>> >>>Any suggestions as to what may be the problem? It seems to be in the Import >>>program as I can see in the examples window that the State information >>>doesn't appear yet when I run the Import program for the other data from the >>>10 M contest, it does. ??? I know from the documentation that the Import >>>program follows some logic to make sure the new records are formatted >>>correctly, etc. but the State information is being discarded or not created >>>even though it appears correct when looking at the ADIF source data. i.e., >>>the <SECTION 2:ID> looks good. >>>Hope this makes sense. If anyone wants to look at the data, I can send the >>>files (or parts) when I get home. >>> >>>Thanks and 73, Rod >>> >>> >>>-- >>>Rod Greene, W7ZRC >>>3560 N. McDermott Rd. >>>Meridian ID 83642 >>>______________________________________________________________ >>>Dxbase mailing list >>>Home: http://mailman.qth.net/mailman/listinfo/dxbase >>>Help: http://mailman.qth.net/mmfaq.htm >>>Post: mailto:[email protected] >> >>______________________________________________________________ >>Dxbase mailing list >>Home: http://mailman.qth.net/mailman/listinfo/dxbase >>Help: http://mailman.qth.net/mmfaq.htm >>Post: mailto:[email protected]
