On Wed, 10 May 2023, Anna Petrášová wrote:
There is r.surf.contour, so that sounds like the tool you need.
Thank you, Anna. I'll re-do the process.
Best regards,
Rich
___
grass-user mailing list
grass-user@lists.osgeo.org
On Wed, May 10, 2023 at 12:34 PM Rich Shepard
wrote:
> On Wed, 10 May 2023, Anna Petrášová wrote:
>
> > Sounds like the vector geometry was already 3D, that's the case when you
> > use use=z. If the vector would be 2D (see v.info) you would have to use
> the
> > attribute table.
>
> Anna,
>
>
On Wed, 10 May 2023, Rich Shepard wrote:
There are several r.resamp.* modules in the core distribution. Please advise
me which would be most appropriate for my rasterized contour elevation map.
Should I use one of the v.surf.* modules then re-rasterize the resulting
map? If so, please
On Wed, 10 May 2023, Rich Shepard wrote:
Is there an r.* module to interpolate elevations between the contour lines
so I have cells?
There are several r.resamp.* modules in the core distribution. Please advise
me which would be most appropriate for my rasterized contour elevation map.
TIA,
On Wed, 10 May 2023, Anna Petrášová wrote:
Sounds like the vector geometry was already 3D, that's the case when you
use use=z. If the vector would be 2D (see v.info) you would have to use the
attribute table.
Anna,
When I used the 2D file, regardless of which parameter I used or both,
Sounds like the vector geometry was already 3D, that's the case when you
use use=z. If the vector would be 2D (see v.info) you would have to use the
attribute table.
On Wed, May 10, 2023 at 12:14 PM Rich Shepard
wrote:
> My current topographic vector data file has a column name for the
My current topographic vector data file has a column name for the elevation
data, ContourEle. Reading the v.to.rast page there is a use parameter (with
'z' for elevation) and an attribute_column parmater. Because the vector
map's database table does not have a column named 'z', but the one named
