-
Many thanks to everyone who offered feedback to the initial proposal
in December: W5XD, K8CC, EI5DI, WF1B, K2MM, KA5WSS, N6TR, K1EA, AE6Y,
N1ND, S56A, VK4EMM, AA6TY, N3EQL, WA7BNM, N8BJQ, K4JRB and K5FUV. Did
I leave anyone out?
-
The initial idea was to create a standard summary sheet that could be
prepended to the ARRL Format log that is created when the user does a
WRITELOG or equivalent after the contest. After going through the SS
log checking process with N6TR, I've now taken the liberty to
unilaterally create an Unofficial ARRL Format which I am calling the
Cabrillo format, and have included examples. Please make the output
of your programs look like the new Cabrillo format.
-
The Cabrillo format for Sweepstakes looks like this:
QSO: 14042 CW 1997-11-03 0101 N5KO 1211 B 74 SCV KA5WSS/VE3 1071 A 74 ON
QSO: 14042 CW 1997-11-03 0102 N5KO 1212 B 74 SCV NJ2L 1122 B 81 WNY
QSO: 14042 CW 1997-11-03 0102 N5KO 1213 B 74 SCV K9ZO 902 A 69 IL
You will note that data is in fixed columns and is space delimited, so
as to make it both human and robot readable. However, in the case of
a field overflow, the information should be truncated so that it fits
into the field and doesn't disrupt data in other columns, so a call
like KA5WSS/ARRL-JUBILEE would appear like this:
QSO: 14042 CW 1997-11-03 0101 N5KO 1211 B 74 SCV KA5WSS/ARR 1071 A 74 ON
QSO: 14042 CW 1997-11-03 0102 N5KO 1212 B 74 SCV NJ2L 1122 B 81 WNY
QSO: 14042 CW 1997-11-03 0102 N5KO 1213 B 74 SCV K9ZO 902 A 69 IL
-
One goal is to make the logs and summary sheets easy to digest by both
humans and by computers. The only appropriate non-printable
characters in a log submission should be SPACE and the appropriate text
end-of-line sequence for the platform the logging program runs on,
such as CR/LF for DOS.
-
The list of contests included in this proposal was initially directed
by K5FUV. However, in time we can extend this to include others
(Field Day, WAE, etc).
-
One big disconnect at ARRL HQ between paper summary sheets and
electronic logs is that the electronic logs don't include the ARRL
section. For ARRL Contests (all contests with names like ARRL-10,
ARRL-DX-SSB, etc), please include something in your logging program
startup that prompts the user for his ARRL section at the same time as
he is prompted for his callsign and the contest type and so forth, and
then include it in the file you generate for electronic log
submission.
-
Lines can exceed 80 characters in length.
-
CLAIMED-SCORE is included so that a High Claimed Scores report may be
generated. Line score data such a QSOs, QSO points, multipliers,
on-time and off-time will be computed during the log checking process.
-
CLUB, OPERATORS, SOAPBOX, and ADDRESS lines may appear multiple times
with different data, as shown. Please limit the nubmer of ADDRESS:
lines to a total count of four so that the name and address may be fit
onto a standard mailing label.
NAME: Trey Garlough
ADDRESS: 7375 Oak Ridge Road
ADDRESS: Aptos, CA 95003
ADDRESS: USA
Other types of lines may only appear once.
-
All lines types shown in the spec are required in a valid entry. If
no soapbox is entered into the logging program, please write out
something like
SOAPBOX:
SOAPBOX:
SOAPBOX:
SOAPBOX:
so that people will get the right idea if they decide to edit the file
by hand. Same thing applies to NAME, ADDRESS, CLUB, and OPERATORS.
-
A space-delimited list of operator callsign(s). You may also list the
callsign of the host station by placing an "@" caracter in front of
the callsign within the operator list. KH6ND operating from KH7R's
QTH as KH7X could describe this situation in his Cabrillo file like
this
CALLSIGN: KH7X
OPERATORS: KH6ND @KH7R