[GRASS-dev] v.what.rast: topology really necessary?

Blumentrath, Stefan Stefan.Blumentrath at nina.no
Sat Jan 14 13:38:08 PST 2017

Hi Martin,

And thanks so much for your effort!

I just patched r70332 and tested in NC, where it works perfectly fine with:

v.random --overwrite --verbose output=random_topo npoints=5000
v.db.addtable map=random_topo columns="elev double precision"

v.out.ascii -c --overwrite --verbose input=random_topo type=point output=$HOME/test.asc columns=elev format=point
v.in.ascii -b --overwrite --verbose input=$HOME/test.asc output=random_notopo skip=1

time v.what.rast --verbose map=random_notopo raster=elev_ned_30m at PERMANENT column=elev
time v.what.rast --verbose map=random_topo raster=elev_ned_30m at PERMANENT column=elev

BTW. during testing I noticed that v.db.addtable also requires topology level 2 (therefore I exported to ASCII and imported without topology)...

Again, thanks so much! This can provide a quite efficient workflow for my colleagues with GPS-tracking data (points) in PostGIS...


-----Original Message-----
From: Martin Landa [mailto:landa.martin at gmail.com] 
Sent: lørdag 14. januar 2017 17.06
To: Blumentrath, Stefan <Stefan.Blumentrath at nina.no>
Cc: GRASS developers list (grass-dev at lists.osgeo.org) <grass-dev at lists.osgeo.org>
Subject: Re: [GRASS-dev] v.what.rast: topology really necessary?

Hi Stefan,

2017-01-11 11:38 GMT+01:00 Blumentrath, Stefan <Stefan.Blumentrath at nina.no>:

could you try patch for v.what.rast [1]? Ma

[1] https://trac.osgeo.org/grass/ticket/3249#comment:13

Martin Landa

More information about the grass-dev mailing list