Rather than use raster DTM maps I decided to use depth measurement points
themselves.
The data look 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
The command I'm using is:
d.vect map=lady_channel_sounding_points display=zcoor type=point zcolor=blue size=7
and the resulting map is attached.
Perhaps I should make the computational region smaller to make individual
values visible, but are the display and color values what they should be?
The values are displayed in red, not blue.
TIA,
Rich
(attachments)

On Thu, 30 Sep 2021, Micha Silver wrote:
Here's what I did. Notice that I added the "-z=3" option to v.in.ascii so
that the new points vector is 3D. Then the "zcolor=" option to d.vect
works.
Micha,
The command I used is:
v.in.ascii -zr in=~/projects/washington/project/data/bathymetry/coe/CL_34_WSHX_20210720_CS.xyz out=wash_transect format=point sep=comma columns='x double precision, y double precision, elev=int' x=1 y=2 z=3
--o
It has the -z option specified. It also has 'z=3' at the end to indicate the
elevation values are the third column in the file.
If I replace -zn with -z=3 GRASS tells me:
ERROR: v.in.ascii: Sorry, <=> is not a valid flag
ERROR: v.in.ascii: Sorry, <3> is not a valid flag
And GRASS still tells me:
ERROR: Unable to open input file
</home/rshepard/projects/washington/project/data/bathymetry/coe/CL_34_WSHX_20210720_CS.xyz>:
No such file or directory
It's quite frustrating as it had no problem finding CL_33_LDYX_20210712_CS.xyz
in the same directory just before I entered the command for importing CL_34_WSHX_20210720_CS.xyz.
Thanks,
Rich