CSV import

Dirk Hohndel dirk at hohndel.org
Wed Jan 7 08:39:40 PST 2015


On Wed, Jan 07, 2015 at 06:23:40PM +0200, Willem Ferguson wrote:
> On 07/01/2015 17:25, Dirk Hohndel wrote:
> >
> >6m     5 min
> >
> >4.5m       13 min
> >
> >Total run time: 41 minutes
> >
> >The dive notes are given, 1 line at a time, in the import table (see
> >attached screenshot 2). Result is that each dive takes several rows of space
> >in the import table: impossible to parse for import.
> >That simply is an invalid format.
>
> What is the limitation with repect to the notes? It is plain hand-typed text
> with LF line terminators, admittedly also with tab characters included which
> could confuse the parser with respect to delimiters. Nothing fancy. What
> about about taking the text from the Notes text box, deal with it as a long
> multiline null-terminated string, strip out any characters that conflict
> with the CSV formatting and store it in the CSV file as one long delimited
> string. That should allow the retention of tabs and LF characters. Or am I,
> as frequently, overlooking something basic?

Yes. Surround them with quotes. And note that a bunch of characters are
verboten in the CSV input. Including, of course, quotes.

But again. CSV is NOT intended to replace our storage formats.
It is NOT intended as a be all save all.
It is NOT intended as anything and everything anyone might want.

The goal here is to make it easy for people to import a manual dive log.
Nothing more, nothing less.

> Look at this dive note:
> Today we dived "Mark's Horrible Hole" and his "Potato grouper" turned out to
> be a large juvenile coral cod.

Not happening. Enter this in the UI. Or hand edit the XML file.

/D



More information about the subsurface mailing list