tsteven4
commented
3 months ago The documentation says
If the first line contains any tabs, the data lines are assumed to be tab separated. Otherwise the fields are assumed to be separated by commas
What the code actually does is: If the first line contains a tab, the fields are assumed to be tab separated. Otherwise, if the first line contains a semicolon, the fields are assumed to be separated by semicolons.. Otherwise, if the first line contains a vertical bar, then the fields are assumed to be separated by vertical bars. Otherwise a comma separator is assumed.
Note that the header line and the data lines are all assumed to use one common separator to separate the fields, either a comma, tab, semicolon or vertical bar.
unicsv_fieldsep = ",";
if (header.contains('\t')) {
unicsv_fieldsep = "\t";
} else if (header.contains(';')) {
unicsv_fieldsep = ";";
} else if (header.contains('|')) {
unicsv_fieldsep = "|";
}
noyannus
When input cvs fields contain
;, gpsbabel throws the"unicsv" Invalid latitude 1e+25 in waypointerror on the first data line (tried on various lines).It works as expected with a field structure (header and data) of separated fields like so:
"lat","lon","name","foo","bar","baz","blah","boom", "...", "..."With some fields (
fooand several after it) beforehand concatenated and separated with–or with#, all is well also. This works:"lat","lon","name","foo – bar – baz – blah – boom – ...", "...""lat","lon","name","foo# bar# baz# blah# boom# ...","..."But if the separator of these already merged fields in the input are separated with a semicolon, the latitude (incidentally the first data field to be processed, maybe that means something?) is
Invalid."lat","lon","name","foo; bar; baz; blah; boom; ...","..."causes the error.gpsbabelis called with"${<path/to/gpsbabel>}" -i unicsv -f "${TEMPFILE}" -o gpx -F "${OUTFILE}".This is different from #591, as no
fields optionis involved.Observed with
GPSBabel Version 1.9.0onopenSUSE Tumbleweed 20240624, withKernel 6.9.5-1-default (64-bit).