[SD-User] SDI - Island Ref Format in ADIF

[cq]

From: "Martyn Johnson" <Martyn.Johnson at cl.cam.ac.uk>
To: "cq" <cq at philcatterall.plus.com>
Cc: <sd-user at contesting.com>; <Martyn.Johnson at cl.cam.ac.uk>
Sent: Tuesday, August 02, 2005 11:42 AM
Subject: Re: [SD-User] SDI - Island Ref Format in ADIF


> > If the log is then converted to ADIF spec via SDICHECK for import into a
logging program the format is then no in compliance with the ADIF spec. The
correct IOTA ADIF format is 5 character which must include the hyphen (e.g.)
EU-005.
>
> It's more complicated than that.
>
> SDICHECK actually seems to put IOTA in the record twice, both with and
without a hyphen. Here is an example from my log:
>
> <Call:4>YM0T         <Mode:3>SSB  <Band:3>20M  <Freq:6>14.300
<RST_Sent:2>59  <RST_Rcvd:2>59
> <QSO_Date:8>20050730 <Time_On:4>1737 <SRX:3>315  <IOTA:5>AS159
<IOTA:6>AS-159 <STX:3>015
> <EOR>
>
> It will depend on the interpreting program which one of these wins!
>
> -- 
> Martyn M1MAJ


Hi Martyn

Yes, same here. Not an expert but you would think that logging programs
rather than contest logging programs would pick out the relevant ADIF spec 6
character data. In the case of Logger 32 (V2.4) it plucked out the 5
character data instead. Perhaps uses of other programs who have imported
their IOTA logs from SD would like to comment on how their imports went?
Perhaps it's down to the fact that the <IOTA:5> string appears first in the
line so that's the one Logger 32 chose.

73 Phil


Phil Catterall Callsign: G4OBK
Previous Callsigns: GD4OBK GM4OBK SV5/G4OBK SV9/G4OBK J42004Q
Ham Radio Website: http:\\www.qsl.net\g4obk
----- Original Message ----- >
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.338 / Virus Database: 267.9.8/61 - Release Date: 01/08/05
>
>



-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.9.8/61 - Release Date: 01/08/05