[GRASS-user] v.in.ascii column identifications

GRASS GRASS user
1

The 8.0.dev manual for v.in.ascii describes the column identifiers:
x=integer
     Number of column used as x coordinate (points mode)
     First column is 1
     Default: 1
y=integer
     Number of column used as y coordinate (points mode)
     First column is 1
     Default: 2
z=integer
     Number of column used as z coordinate (points mode)
     First column is 1. If 0, z coordinate is not used
     Default: 0

Entering v.in.ascii on the command line (lines wrapped in alpine):
v.in.ascii -z
in=~/projects/washington/project/data/bathymetry/coe/CL_33_LDYX_20210712_CS.xyz
out=lady_xsec_depths for=point x=1 y=2 z=3 col='x double precision, y double
precision, z integer' --o

yields this response from GRASS:
WARNING: ntokens: 1, xcol: 0, ycol: 1, zcol: 2
ERROR: Broken row 2: '7709581.42,697951.64,24'

When I change the command to match the above:
ERROR: Column numbers must not be negative
GRASS project/bathymetry:analyses > ERROR: Column numbers must not be negative

And when I try it again:
bash: GRASS: command not found

What might be going on here? Now neither the command line nor the GUI will
import an ASCII point file.

Rich

2

Hi Rich,

Please check your "separator" settings. Default is pipe |, but your data seems to be comma delimited.

Cheers
Stefan

-----Original Message-----
From: grass-user <grass-user-bounces@lists.osgeo.org> On Behalf Of Rich Shepard
Sent: fredag 1. oktober 2021 18:07
To: grass-user@lists.osgeo.org
Subject: [GRASS-user] v.in.ascii column identifications

The 8.0.dev manual for v.in.ascii describes the column identifiers:
x=integer
     Number of column used as x coordinate (points mode)
     First column is 1
     Default: 1
y=integer
     Number of column used as y coordinate (points mode)
     First column is 1
     Default: 2
z=integer
     Number of column used as z coordinate (points mode)
     First column is 1. If 0, z coordinate is not used
     Default: 0

Entering v.in.ascii on the command line (lines wrapped in alpine):
v.in.ascii -z
in=~/projects/washington/project/data/bathymetry/coe/CL_33_LDYX_20210712_CS.xyz
out=lady_xsec_depths for=point x=1 y=2 z=3 col='x double precision, y double precision, z integer' --o

yields this response from GRASS:
WARNING: ntokens: 1, xcol: 0, ycol: 1, zcol: 2
ERROR: Broken row 2: '7709581.42,697951.64,24'

When I change the command to match the above:
ERROR: Column numbers must not be negative GRASS project/bathymetry:analyses > ERROR: Column numbers must not be negative

And when I try it again:
bash: GRASS: command not found

What might be going on here? Now neither the command line nor the GUI will import an ASCII point file.

Rich

_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fmailman%2Flistinfo%2Fgrass-user&amp;data=04|01|Stefan.Blumentrath%40nina.no|febb7f0f75b04a758b1008d984f57cf7|6cef373021314901831055b3abf02c73|0|0|637687012593647527|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&amp;sdata=wPke%2FDQRpWHE0Xg6jZwhrh0XoVEOkj9ISz51fH6fXQg%3D&amp;reserved=0

3

On Fri, 1 Oct 2021, Stefan Blumentrath wrote:

Please check your "separator" settings. Default is pipe |, but your data
seems to be comma delimited.

Stefan,

In the GUI I selected 'comma', forgot to do so on the command line.
Regardless, the GUI didn't bring in the data. I'll check it again.

Thanks,

Rich