Hello,
today I had several S2S-Contact and I did not want to type them into the database “one after one”. so i decided to write a little CSV-file!
i had a look at the following site:
http://www.sotadata.org.uk/ChaserCSVInfo.htm
but there is no info about how to put in S2S-contacts. i tried to find the answer and after some experimenting i found out that the correct way is the following:
,
maybe it would be good to add this info to the “CHASERCSVINFO.HTML”!?
73 de martin
www.oe5reo.at
In reply to OE5REO:
Hello Martin,
could please explain what is ?
73’s
Laurent de F8CZI
In reply to F8CZI:
All is explained here.
Actual format is explained by Andy MM0FMF about halfway down this thread.
http://www.sotawatch.org/reflector.php?topic=7965#
I use this all the while now.
I create a single log and submit it twice, as both an activator log and chaser log. It sorts out which records are which and automatically does the S2S logging too. Marvellous.
73
Gerald
MW0WML
In reply to F8CZI:
hello laurent,
actually i don’t know what “v2” means … but today’s s2s-chaser-csv looks like this (and the upload worked):
V2,OE5REO/P,OE/OO-340,12/08/2013,0753,144MHz,FM,OE5EEP/P,OE/OO-174
V2,OE5REO/P,OE/OO-340,12/08/2013,0842,14MHz,SSB,ES4/PB2T/P,ES/ES-003
V2,OE5REO/P,OE/OO-340,12/08/2013,0916,144MHz,FM,OE5PGM/P,OE/OO-038
V2,OE5REO/P,OE/OO-340,12/08/2013,0922,14MHz,SSB,OE5PGM/P,OE/OO-038
V2,OE5REO/P,OE/OO-340,12/08/2013,0947,7MHz,SSB,OE5PGM/P,OE/OO-038
V2,OE5REO/P,OE/OO-340,12/08/2013,1032,24MHz,SSB,S52CU/P,S5/KS-012
V2,OE5REO/P,OE/OO-340,12/08/2013,1052,144MHz,FM,OE/OK2QA/P,OE/OO-002
73 de martin
www.oe5reo.at
In reply to OE5REO:
V2 means “Version 2” (of the CSV format), as oppose to the original version (which would have been V1) which doesn’t have any prefix.
73
Gerald
MW0WML
In reply to MW0WML:
O.K. thanks Gerald for the info!
Hopefully Andy, MM0FMF will add the info to this site soon:
http://www.sotadata.org.uk/ChaserCSVInfo.htm
73 de martin
www.oe5reo.at
Hello @ all
Thanks a lot for this information.
73’s
Laurent de F8CZI
Hi
I’ve been trying this afternoon to load a excel generated CSV for some recent S2S
However when I try to include comments in my CSV I get the following error
An error has occured whilst processing line 1 of the input file.
Please ensure the input file is valid CSV or TSV.
System.IndexOutOfRangeException: Index was outside the bounds of the array. at SOTA.AddChaserEntry.getChaserCSVLine(StreamReader sr, SqlConnection dbConnection, Int32 userId, Int32 checkMode, DateTime& lastDate, String& lastTime, Int32& summitID, Int32& S2SsummitID, Boolean& parseErrorFlag, Boolean& parseDuplicateFlag, Boolean& S2S, Boolean& Activator, Int32& csvVersion) in D:\SOTADATABASE\AddChaserEntry.cs:line 627 at SOTA.ChaserCSV2.Page_Load(Object sender, EventArgs e) in D:\SOTADATABASE\ChaserCSV2.aspx.cs:line 86
This format causes the error
V2,G6UYG/P,G/WB-005,14/07/2013,14:45,144,FM,G4OBK/P,G/WB-020,YES,Phill LOC:IO82nd Tx:55 Rx:55 Miles:28.79 Note:Me : VX8 Handie Flex Antenna
V2,G6UYG/P,G/WB-005,14/07/2013,14:46,144,FM,M6PYG/P,G/WB-020,YES,Geoff LOC:IO82nd Tx:55 Rx:55 Miles:28.79 Note:Me : VX8 Handie Flex Antenna
V2,G6UYG/P,G/WB-005,14/07/2013,14:55,144,FM,MV1EYP/P,GW/NW-060,YES,Tom LOC:IO82JT Tx:52 Rx:55 Miles:22.12 Note:Me : VX8 Handie Flex Antenna
V2,G6UYG/P,G/WB-005,14/07/2013,14:55,144,FM,MV0HGY/P,GW/NW-060,YES,Jimmy LOC:IO82JT Tx:52 Rx:55 Miles:22.12 Note:Me : VX8 Handie Flex Antenna
However – the following uploads fine, but although the notes / comments field is empty – the onscreen table after uploading the CSV but before clicking submit entry shows YES in both the S2S fields and the Notes fields
V2,G6UYG/P,G/WB-005,14/07/2013,14:45,144,FM,G4OBK/P,G/WB-020,YES
V2,G6UYG/P,G/WB-005,14/07/2013,14:46,144,FM,M6PYG/P,G/WB-020,YES
V2,G6UYG/P,G/WB-005,14/07/2013,14:55,144,FM,MV1EYP/P,GW/NW-060,YES
V2,G6UYG/P,G/WB-005,14/07/2013,14:55,144,FM,MV0HGY/P,GW/NW-060,YES
Any idea what I’m doing wrong ?
I’ve tried with just a single word comment just to check if it was a field length issue but just the word NOTE causes the same error.
Regards
Steve
G6UYG
In reply to G6UYG:
Embedded commas are not allowed in a comment unless the whole comment is wrapped in quotes.
This is bad:
V2,G6UYG/P,G/WB-005,14/07/2013,14:45,144,FM,G4OBK/P,G/WB-020,YES,Phill LOC:IO82nd Tx:55 Rx:55 Miles:28.79 Note:Me : VX8 Handie Flex Antenna
This is good:
V2,G6UYG/P,G/WB-005,14/07/2013,14:45,144,FM,G4OBK/P,G/WB-020,“YES,Phill LOC:IO82nd Tx:55 Rx:55 Miles:28.79 Note:Me : VX8 Handie Flex Antenna”
Andy
MM0FMF
In reply to MM0FMF:
Hi Andy
Thanks - that worked a treat.
Although I didn’t think I had any embedded commas, I was treating the YES for S2S as a separate field on it’s own so what I though was a field separation comma was the problem.
Thanks again.
Regards
Steve
G6UYG