Thanks for raising the adif issue and I can promise it will get a thorough review for 2010.
For something that sounds like it should be straightforward, ADIF is not so easy to deal with. First of all, there are 2+ versions (I say plus because the draft 3 of ADIF is pretty well advanced). So if your import program supports a version than your export version, you can expect trouble. The second problem is that the ADIF standard is increasingly being developed in isolation. In talking with several of the other software authors, it seems that it is a standard driven by an incredinly small group (often one [person ) and comments from other software writers don't seem to affect the ultimate outcome, so many of them have "given up". So you end up with a list of a zillion modes being defined, etc., stuff that we could not actually give you the option of selecting in a program because the list would be so large its unfeasible. I think we all support the idea behind ADIF and try to implement the parts that make sense to each of us. Jim, ADIF, has written a utility that tries to take the standard and translate it into what DX4WIN understands. Since DXBase uses its own adif import program, it simplifies the process for me because I can support the import of the zillion modes, etc. without having to make them available in the user interface. I can also make sure that the export is compliant without giving every option done in the "standard". Anyway, I promise it will be brought up to date in the next release. Neal Campbell Abroham Neal Software www.dxbase.com www.abrohamnealsoftware.com www.sdrsystems.com (540) 242 0911 Amateur Radio: K3NC Blog: http://www.abrohamnealsoftware.com/blog/ DXBase bug reports: email to [email protected] Abroham Neal forums: http:/www.abrohamnealsoftware.com/community/ DX Cluster: dxc.k3nc.com port 23 On Tue, Oct 6, 2009 at 10:09 AM, [email protected] <[email protected]> wrote: > I just want to echo Doug comments with mine. > I am not leaving DXBase but I want to point out the problem with the ADIF > Import that has gone on for years. > > I use Writelog for all my logging and then import those qso's into DXbase. > Writelog uses the country database that is maintained by > AD1C. The ADIF file has the correct PREF during the import but when I go > into DXBase I have to check very closely as DXbase will replace the correct > Pref with the parent. > > An example is FT5GA, imported as France, TX5SPA, imported as France and > 3D20CR, imported as Conway Reef which is correct. > > It seems to me that the import should look at the ADIF PREF and if it > exists then use it else if it is null or blank then populate it. > > Seems simple enough? > > Joe K0BX > Stop the insanity! > Please do not add me to any distribution lists (Joke, Stories or Junk) > without my permission. > > > > ______________________________________________________________ > Dxbase mailing list > Home: http://mailman.qth.net/mailman/listinfo/dxbase > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[email protected] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > ______________________________________________________________ Dxbase mailing list Home: http://mailman.qth.net/mailman/listinfo/dxbase Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
