Hi all,
there is a new module in grass7 for raster interpolation called
r.resamp.bspline, based on the lidar tool methods. NULL cells are
filled on the go, no need to fill them first. Alternatively, the
module only interpolates NULL cells in the input raster, running quite
fast in this mode. The
Hi,
2010/5/7 Markus Metz markus.metz.gisw...@googlemail.com:
there is a new module in grass7 for raster interpolation called
r.resamp.bspline, based on the lidar tool methods. NULL cells are
filled on the go, no need to fill them first. Alternatively, the
module only interpolates NULL cells
On Fri, May 7, 2010 at 11:38 AM, Martin Landa landa.mar...@gmail.com wrote:
Hi,
2010/5/7 Markus Metz markus.metz.gisw...@googlemail.com:
there is a new module in grass7 for raster interpolation called
r.resamp.bspline, based on the lidar tool methods. NULL cells are
filled on the go, no need
... because in the python script there is in line 120
reg = grass.region()
but it should be the python equivalent to bash
eval `g.region -gm | grep res`
note the -m flag. This is necessary because the input buffer distance
for r.buffer must be in meters.
Markus M
Markus Metz wrote:
... because in the python script there is in line 120
reg = grass.region()
but it should be the python equivalent to bash
eval `g.region -gm | grep res`
note the -m flag. This is necessary because the input buffer distance
for r.buffer must be in meters.
Fixed in
On Fri, May 7, 2010 at 1:43 PM, Markus Metz
markus.metz.gisw...@googlemail.com wrote:
...
BTW, r.buffer in trunk is broken for latln, wrong results and slow, in
grass64 results are fine and it is much faster (???).
+1!
Markus
___
grass-dev mailing
Markus Metz wrote:
BTW, this module should probably stay in `raster/` instead of
`vector\lidar`.
For compilation it is easier if it is in vector/lidar because it uses
stuff in lidarlib. Otherwise it will fail because raster modules are
compiled before vector modules -lidarlib not yet
On Fri, May 7, 2010 at 2:19 PM, Glynn Clements gl...@gclements.plus.com wrote:
Markus Metz wrote:
BTW, this module should probably stay in `raster/` instead of
`vector\lidar`.
For compilation it is easier if it is in vector/lidar because it uses
stuff in lidarlib. Otherwise it will fail
#567: Create new GRASS SVN sub-repository
--+-
Reporter: neteler | Owner: warmerdam
Type: task | Status: assigned
Priority: normal | Component: Systems Admin
Resolution: |
