ADIF Content Specs
  Content Specification for ADIF uploads to eQSL.cc
WM7D Callsign Database
 

[Login] [Register]



Thursday, July 9, 2020 20:29 UTC
Callsign:
Questions? Problems?

FAQ
Contact Us


MFJ Enterprises
MFJ Enterprises
Welcome New User
OK/OE3CQB
Christian Böhm from CZECH REP.
Site News
| If you have a new callsign, DO NOT keep uploading logs with the new call... (more)
Last Heard
160M: TA1CM, UA1ARD, more...
Latest eAwards
Most eAwards: EA3ZD,4Z4DX,F6ECI,ZL1BQD,F6ARS...
eAwardCallsignDate
eAfricatm RU2K Jul 09
eAntarcticatm F4GTB May 18
eAsiatm KP4SE Jul 09
eAustraliatm M5BFL Jul 05
eCanadatm K3HPA Jul 09
eDXtm OE6XMF Jul 09
eDX100tm RU2K Jul 09
eEchoLinktm EA7KCH Jun 19
eEuropetm M0HUI Jul 09
eFROMtm W7GF Jul 07
eGridtm M0HUI Jul 09
eJapantm M0GLP Jul 09
eNAmericatm M0HUI Jul 09
eNZtm JA5CEX Jun 18
eOceaniatm JH8FFJ Jul 09
ePFX300tm US5ZAT Jul 09
eSAmericatm JH8FFJ Jul 09
eSatellitetm LU4FTA Jul 06
eUKtm OE6XMF Jul 09
eWACtm JH8FFJ Jul 09
eWAStm KG5ZEL Jul 09
eZ40tm I0WBX Jul 04

Power Users: AA3B,N2BJ,N3RS...
Latest Authenticity Guaranteed
MFJ Enterprises
MFJ Enterprises
Community
Charter Members: EA7CN,F5CVI,G3PGA...
Earliest QSOs in the database
Some of our members' ancient QSL card collections!
Advertising Opportunities
If you have a ham radio oriented business, take a look at our advertising opportunities!
Amateur Radio Products
Shop Online for amateur radio books and other items! More...
Zip Codes - Free zip code lookup and zip code database download.

We accept up to ADIF V3.1.0 logs

New Submodes supported: FT4

26Dec2019 We are now capturing SAT_NAME as well as SAT_MODE

Programmers:

If you are writing a logging application and need information on all the eQSL.cc interfaces available,
bookmark the www.eQSL.cc/Programming page

LOG UPLOADING
Logs imported into the eQSL.cc global database must be in ADIF format.
The specifications for this format are at http://adif.org.uk/adif
However, those specifications do not define the CONTENT that is acceptable, the minimum required fields, and the maximum field lengths.
So, here are our requirements:
ADIF CONTENT SPECIFICATIONS
We accept up to ADIF V3.1.0 logs
Only ADIF format files can be imported. Cabrillo, Excel, or "Comma Delimited" files cannot be uploaded, and will be rejected. The filename or extension are not important. What is important is proper format of the tags within the file, defining the fields per the ADIF specification (see hyperlinks above), with each record ending in an EOR tag.
Minimum valid record contents
QSO_DATEYYYYMMDD
TIME_ONonly HH and MM are used
CALLinvalid if > 13 characters
MODEmust be one of table below
BAND or FREQ or SAT_MODEmust be one of table below (Sat_Mode not supported in .NET real-time import)
Optional fields that will be imported if present
FREQIn Megahertz. Only one decimal point is permissible. Optional field unless BAND is missing, in which case it is mandatory. We do not check for agreement between BAND and FREQ. (Not supported yet in .NET real-time import)
Prop_Mode (new in ADIF 2)MANDATORY for IRLP ("IRL"), EchoLink ("ECH"), Satellite ("SAT"), EME, CQ100 (should read "INTERNET", as should all other Internet-assisted or VOIP protocols), and other special propagation modes - Truncated to first 3 characters. See Enumerated List in the ADIF 2 spec for valid codes (Not supported yet in .NET real-time import)
LOG_PGM or PROGRAMID in the headerContains the name of the logging software - If it matches the "Software Title" from our Logger Listing, then statistics will be accumulated on it. So please make sure we have your logger in our database!
QSLMSGTruncated after 240 characters (Note: The field called 'COMMENT' is normally used only for private comments and is NOT printed on the eQSLs
RST_SENTmaximum 8 characters
SUBMODESee the MODES table below for valid contents
SAT_MODESee the SAT_MODES table below for valid contents
SAT_NAMEMaximum 15 characters, but we reserve the right to standardize satellite names to allow easier matching between incoming and outgoing eQSLs (i.e. XW-2A vs CAS-3A, etc.)
MY_CNTYUS County from which you are operating. Note that this should match exactly what is in the profile of the account you are uploading into! See FAQ for details
MY_GRIDSQUAREGrid Square from which you are operating. Note that this should match exactly what is in the profile of the account you are uploading into!
MY_LATLatitude from which you are operating. Note that this should match exactly what is in the profile of the account you are uploading into!
MY_LONLongitude from which you are operating. Note that this should match exactly what is in the profile of the account you are uploading into!
If you want to verify that your log file is in ADIF format, and you have used NotePad or WordPad or a similar text editor before, you can use one of them to read your log file (it may have a .ADI extension but does not need to).

Look for lines like the ones below. They can all be on the same line or on different lines, and there will be one set for each QSO. There may also be other information such as Name or Freq or Comments, all of which are permissible.

<QSO_DATE:8>20000409 <TIME_ON:4>1130 <CALL:6>WB4WXX <BAND:3>20M <MODE:3>SSB <RST_SENT:2>57 <EOR>

MODES
ModeOptional SubModes
AM
ARDOP
ATV
C4FM
CHIP CHIP128, CHIP64,
CLO
CONTESTI
CW PCW,
DIGITALVOICE
DOMINO DOMINOEX, DOMINOF,
DSTAR
FAX
FM
FSK31
FSK441
FT8
HELL FMHELL, FSKHELL, HELL80, HFSK, PSKHELL,
ISCAT ISCAT-A, ISCAT-B,
JT4 JT4A, JT4B, JT4C, JT4D, JT4E, JT4F, JT4G,
JT44
JT65 JT65A, JT65B, JT65B2, JT65C, JT65C2,
JT6M
JT9 JT9-1, JT9-10, JT9-2, JT9-30, JT9-5, JT9A, JT9B, JT9C, JT9D, JT9E, JT9E FAST, JT9F, JT9F FAST, JT9G, JT9G FAST, JT9H, JT9H FAST,
MFSK FT4, JS8, MFSK11, MFSK128, MFSK16, MFSK22, MFSK31, MFSK32, MFSK4, MFSK64, MFSK8,
MSK144
MT63
OLIVIA OLIVIA 16/1000, OLIVIA 16/500, OLIVIA 32/1000, OLIVIA 4/125, OLIVIA 4/250, OLIVIA 8/250, OLIVIA 8/500,
OPERA OPERA-BEACON, OPERA-QSO,
PAC PAC2, PAC3, PAC4,
PAX PAX2,
PKT
PSK PSK10, PSK1000, PSK125, PSK250, PSK31, PSK500, PSK63, PSK63F, PSKAM10, PSKAM31, PSKAM50, PSKFEC31, QPSK125, QPSK250, QPSK31, QPSK500, QPSK63, SIM31,
PSK2K
Q15
QRA64 QRA64A, QRA64B, QRA64C, QRA64D, QRA64E,
ROS ROS-EME, ROS-HF, ROS-MF,
RTTY ASCI,
RTTYM
SSB LSB, USB,
SSTV
T10
THOR
THRB THRBX,
TOR AMTORFEC, GTOR,
V4
VOI
WINMOR
WSPR
IMPORTING ADIF FILES EARLIER THAN V3.0.4
FOR NOW, log uploads and real-time imports of logs that use formats older than ADIF V3.0.4 that included many of today's SUBMODEs in the MODE field will be converted automatically
ADIF V3.0.4 was published in 2013. If your logger is older than that, now would be a good time to upgrade!
MODE CONVERSIONS - NO LONGER FUNCTIONAL!
StandardThrough June 2017, any modes in this right-hand column were converted to the Standard Mode at left. These were not ADIF compliant and are now finally phased out. Make sure your logger is compliant with the latest revisions of the ADIF specification at http://adif.org.uk/adif
SSBA3J, J3E, USB, LSB, PHONE, VOICE
CWA1
ASCIASCII
CLOClover
HELLHellschreiber
JT65JT65A,JT65B,JT65C
JT9JT9-1,JT9-2,JT9-3,etc
PACPactor
PAC2Pactor II
PAC3Pactor III
PKTPacket
PSK31PSK,BPSK,BPSK31,QPSK
PSK63BPSK63
PSK125PSK125F
Q15Q15X25
THRBThrob
TORAmtor
BANDS
Any content not matching either of these 2 columns will be rejected and require manual intervention to fix
BANDIf BAND not specified, FREQ contents below will convert to BAND
2190m0.136 to 0.137
560m0.501 to 0.504
160m1.8 to 2.0
80m3.5 to 4.0
60m5.2 to 5.5
40m7.0 to 7.3
30m10.0 to 10.15
20m14.0 to 14.35
17m18.0 to 18.168
15m21.0 to 21.45
12m24.0 to 24.99
10m28.0 to 29.7
6m50 to 54
4m70 to 71
2m144 to 148
1.25m222 to 225
70cm420 to 450
33cm902 to 928
23cm1240 to 1300
13cm2300 to 2450
9cm3300 to 3500
6cm5650 to 5925
3cm10000 to 10500
1.25cm24000 to 24250
6mm47000 to 47200
4mm75500 to 81000
2.5mm119980 to 120020
2mm142000 to 149000
1mm241000 to 250000
1 These Old Bands have been deprecated...used to be converted to this
SAT A2m
SAT B70cm
SAT J2m
SAT JL2m
SAT K15m
SAT KT15m
SAT L23cm
SAT R15m
SAT RA2m
SAT RK15m
SAT RT15m
SAT S70cm
SAT T15m
SAT U/S70cm
SAT U/V70cm
SAT_MODEs
1 If neither BAND nor FREQ was specified, but SAT_MODE was specified, we will perform this conversion:
SAT_MODEConverts to this BAND
A2m
B70cm
J2m
JL2m
K15m
KT15m
L23cm
L/U23cm
L/V23cm
R15m
RA2m
RK15m
RT15m
S70cm
T15m
U/S70cm
U/V70cm
1 SATELLITES: Prior to the SAT_MODE tag, we allowed specification of that mode inside a BAND tag, but after ADIF 3.1 we no longer support that. Use the SAT_MODE tag instead. Also be aware that if a SAT_MODE tag is supplied, then the PROP_MODE will automatically be set to SAT. It is possible to commit the error of supplying conflicting BAND and SAT_MODE tags, in which case the BAND overrides SAT_MODE. If you need to specify a different mode than one of those listed above, please contact eQSL.cc technical support. Important note for .NET real-time logger imports: SAT_MODE and PROP_MODE are not yet supported in the .NET interface. U/S and U/V were just added 18Dec2005. Other new modes will be added soon. Sat_Name import only began on Christmas Day, 2019.

©Copyright 1998-2020 Electronic QSL Card Centre, a division of Air Wave Productions, LLC
Read the full Notice of Copyrights, Trademarks, and Liability Limitations for this site