An ADIF export puts the <ADIF_VER> field at the beginning of the file before the header. The ADIF spec states that:
The ADIF version may be included in the header info as follows: <adif_ver:4>1.00 is included as part of the header specification, an importing program can easily determine the ADIF version used to create the file. Note that this must not be at the beginning of the header info, because < as the first character indicates that there is no header.
I linked 2.2.7, but this same text is in 2.2.0 and 2.2.2 (the web page doesn't seem to have the 2.2.1 that's in the exported file).
I noticed this issue when exporting my log for use in WG7J's GridMapper. Moving the tag to the end of the header fixes the issue.
Very interesting, I'll fix it, thank you!
I must say that ADIF specification is funny. I doubt there is any logging program with full ADIF support. ADIF should be common format with common field data. I have no idea what CLUBLOG and HRDLOG specific fields can be in the specification. Maybe I could ask for some specific field CQRLOG has and it will be part of new ADIF standard :D :D. For app specific data there is APP_ prefix in the tag. ADIF is big mess and "XML style" adif is even worse.
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com