[GRASS-user] GUI vector import column format issue

Rich Shepard rshepard at appl-ecosys.com
Fri Oct 1 08:29:33 PDT 2021


Using the wxGUI when GRASS was invoked I tried to import an ASCII point file
looking like this:
lon,lat,depth
7719886.85,702082.80,21
7719910.22,702014.88,21
7719927.67,701945.79,24
7719930.64,701875.40,19
7719933.85,701804.44,37
7719942.24,701734.58,40
7719949.17,701664.16,41
7719958.36,701594.64,38
7719965.04,701524.66,38

The processing window fails to import the file:
(Fri Oct  1 08:19:22 2021) 
v.in.ascii -r input=/home/rshepard/projects/washington/project/data/bathymetry/coe/CL_34_WSHX_20210720_CS.xyz output=wash_sounding_pts separator=comma
Scanning input for column types...
Skipping 452 of 1211 rows falling outside of current region
Number of columns: 3
Number of data rows: 1211
ERROR: 'x' column is not of number type, encountered: 'lon'
(Fri Oct  1 08:19:22 2021) Command finished (0 sec)

Yesterday, using the text interface when invoking GRASS there were no issues
using v.in.ascii on the adjacent file which begins like this:
lon,lat,depth
7709581.42,697951.64,24
7705545.87,698624.07,16
7709732.27,699488.73,27
7712090.79,699428.24,62
7716863.99,701238.89,32
7701540.85,698790.50,31
7713676.33,699192.82,58
7705283.41,697549.00,31
7705037.10,698489.22,16

Why might the GUI see the first column, longitude, differently than the
command line version of v.in.ascii? Could it be that the GUI needs the
header text delimited while the command line version doesn't?K

TIA,

Rich


More information about the grass-user mailing list