in GRASS 6.4.0 RC5 (run on OpenSuse 11.0) I have encountered a problem
in v.in.ascii when importing tables whose columns are delimited by
space. The option 'fs=space' (with or without the apostrophes) does not
seem to work. Only when the columns are delimited by non-space character
(I'v tested '|' and ','), v.in.ascii works well. I store the atribution
data in dbf file.
In previous versions of GRASS the problem does not exist.
The workaround is quite easy (including some non-space delimiters to the
imported table) but I would appreciate the next version to be without
thit bug (or feature ...).
in GRASS 6.4.0 RC5 (run on OpenSuse 11.0) I have encountered a problem
in v.in.ascii when importing tables whose columns are delimited by
space. The option 'fs=space' (with or without the apostrophes) does not
seem to work. Only when the columns are delimited by non-space character
(I'v tested '|' and ','), v.in.ascii works well. I store the atribution
data in dbf file.
In previous versions of GRASS the problem does not exist.
The workaround is quite easy (including some non-space delimiters to the
imported table) but I would appreciate the next version to be without
thit bug (or feature ...).
Thanks to Martin Landa, the problem is solved: The space (delimiter)
must be only one, more spaces between the items (columns) results in the
error, so it is necessary to reduce the number of spaces to one.
E.g:
echo -e "1 2\n3 4" | v.in.ascii out=x fs=space --o
does work
echo -e "1 2\n3 4" | v.in.ascii out=x fs=space --o
does not work (at least at my computer).
The problem is associated only with GRASS >= 6.4. At GRASS 6.3 I am not sure (do not have it available now), in GRASS <=6.2 there is no issue with multiple spaces (verified).
Best regards
Milan Salek
Milan Salek napsal(a):
Dear all,
in GRASS 6.4.0 RC5 (run on OpenSuse 11.0) I have encountered a problem
in v.in.ascii when importing tables whose columns are delimited by
space. The option 'fs=space' (with or without the apostrophes) does not
seem to work. Only when the columns are delimited by non-space character
(I'v tested '|' and ','), v.in.ascii works well. I store the atribution
data in dbf file.
In previous versions of GRASS the problem does not exist.
The workaround is quite easy (including some non-space delimiters to the
imported table) but I would appreciate the next version to be without
thit bug (or feature ...).
Thanks to Martin Landa, the problem is solved: The space
(delimiter) must be only one, more spaces between the items
(columns) results in the error, so it is necessary to reduce
the number of spaces to one.
right, because e.g. if the delimiter was a comma, and a field
were empty, "," would denote the empty field. This is intended
behaviour. Alternate wild idea: try using fs=tab without touching
your data and see what happens.
you can pipe your data though "tr --squeeze-repeats ' '" to
cleanse it.