SOTA Results and Summits Database<\/p>\n
SOTA Activator and Chaser TSV\/CSV file format
\nThis facility lets you upload a large number of QSOs in one bulk transaction.
\nYou need to create a Comma Separated Variable (CSV) or Tab Separated Variable (TSV) file with the fields laid out as shown in the example below.
\nYou then submit this file, which is checked for errors before presenting you with the option to save the QSOs to your database.
\nYou can mix activation records,chaser records and S2S (summit to summit) records all in the same file.
\nYou can include multiple activations in this file but all records for each activation must be together.
\nEach activation is deemed to end when the [MySummit] reference changes.
\nIf you activate the same summit on several days you must upload each activation in a separate file otherwise the file will be
\nassumed to only contain a single activation.
\nThe new prefered Version 2 (V2) format consists of upto ten fields as follows
\n[V2] [My Callsign][My Summit] [Date] [Time] [Band] [Mode] [His Callsign]
\nor
\n[V2] [My Callsign][My Summit] [Date] [Time] [Band] [Mode] [His Callsign][His Summit]
\nor
\n[V2] [My Callsign][My Summit] [Date] [Time] [Band] [Mode] [His Callsign][His Summit] [Notes or Comments]
\nEach field is separated by either a Comma (CSV) or Tab (TSV).
\nEach QSO is a single record and there is one record to a line, terminated in [CR][LF].
\nHere is an example:
\nV2,G3WGV,G\/LD-008,24\/04\/03,1202,7.0MHz,CW,G4ELZ,
\nV2,G3WGV,G\/LD-008,24\/04\/03,1204,7.0MHz,CW,G3NOH,,PSE QSL Direct
\nV2,G3WGV,G\/LD-008,24\/04\/03,1227,144MHz,FM,GW4GTE,,Dave
\nV2,G3WGV,G\/LD-008,24\/04\/03,1228,144MHz,FM,GW0TLK\/M
\nV2,G3WGV,G\/SC-008,08\/06\/03,1404,7.0MHz,CW,GM0AAA\/P
\nV2,G3WGV,G\/SC-008,08\/06\/03,1405,7.0MHz,CW,ON4CK\/P
\nV2,G3WGV,G\/SC-008,08\/06\/03,1407,7.0MHz,CW,DL0DAN\/P,DM\/BW-019,S2S
\nV2,G3WGV,G\/SC-008,08\/06\/03,1410,14.0MHz,CW,YU7LS
\nV2,G3WGV,,10\/06\/03,1023,432MHz,FM,G4TJC,G\/SP-015,Simon (chaser entry)
\nField notes
\nField
\nComments<\/p>\n
My Callsign
\nThis is the callsign you used for the QSO. No spaces in the callsign please
\nMy Summit
\nThis MUST be the full SOTA reference of the summit you where activating, as shown in the above example.
\nIf you are entering a chaser log, this field will be blank. See last entry in the example.<\/p>\n
Date
\nThe date of the QSO. Most date formats are accepted but be careful about USA vs. International date format. Use of
\nInternational date format (DD\/MM\/YY) is recommended<\/p>\n
Time
\nThe time in UTC. Either HHMM or HH:MM will work. Use the 24 hour clock!<\/p>\n
Band
\nYou can enter the frequency in MHz (14.285MHz) or pick from the following:
\n160m: 1.8MHz
\n80m: 3.5MHz
\n60m: 5MHz
\n40m: 7MHz
\n30m: 10MHz
\n20m: 14MHz
\n17m: 18MHz
\n15m: 21MHz
\n12m: 24MHz
\n10m: 28MHz
\n6m: 50MHz
\n2m: 144MHz
\n70cm: 432MHz
\n23cm: 1240MHz<\/p>\n
Mode
\nCW, SSB, FM, Data, AM, Other worK<\/p>\n
Other Callsign
\nThe callsign of the station worked. No spaces in the callsign please<\/p>\n
Other Summit
\nThis field is only needed if the station was also activating a SOTA summit. This is the full SOTA reference of the summit the chasing station was activating, as shown in the above example.
\nIf there is no [Other Summit] you can leave this blank. If there is a comment then you must insert a TAB or
\ncomma to mark the field as being blank. See entries for G3NOH or GW4GTE<\/p>\n
Notes or Comments
\nAn optional field for recording short notes about the QSO.
\nThis could include the Operator’s name and location, Signal Report, QSL information, or almost anything else.
\nYou can embed a TAB or comma in this field. If you do you must enclose the entire Notes field in double-quotes.<\/p>\n
The easiest way to create your TSV\/CSV file is using Excel. This allows you to arrange your log data in columns then save it as either a TSV or CSV file.
\nEither is accepted by the SOTA program.<\/p>\n
Common errors
\n1. Spaces in the callsigns. Our callsigns do not have spaces in them!
\n2. Date or time out of order. The input parser will show an error if the log is not in sequential order
\n3. Errors in the SOTA reference number. Spaces in the reference, leaving off the ITU prefix, or specifying a reference that does not exist will all result
\nin an error being reported.
\nIf an error is detected then it is shown in Red and you should then modify the file to correct the error and resubmit it. Once you get an error free report, you
\nshould carefully check that everything is correct before saving it. As soon as you have saved the data you will be able to see the effect in the various tables.<\/p>\n","protected":false},"excerpt":{"rendered":"
SOTA Results and Summits Database SOTA Activator and Chaser TSV\/CSV file format This facility lets you upload a large number of QSOs in one bulk transaction. You need to create a Comma Separated Variable (CSV) or Tab Separated Variable (TSV) file with the fields laid out as shown in the example below. You then submit … <\/p>\n