On 15/04/17 05:31, Vaclav Petras wrote:
> Back to filling holes in lidar data, I also think that the "fill in the
> gaps" approach is quite promising, so I ported the r.fill.gaps module to G7:
Great! I have read the diff and that was very
helpful for me. I can see that the old and
new raster APIs
On Tue, Mar 21, 2017 at 10:01 AM, Markus Neteler wrote:
>
> > Another drawback is that it was written
> > for GRASS 6 (but converting it to GRASS 7 should not
> > be hard, since it uses only the basic raster API).
>
> FWIW New names can be looked up here:
>
Back to filling holes in lidar data, I also think that the "fill in the
gaps" approach is quite promising, so I ported the r.fill.gaps module to G7:
https://grass.osgeo.org/grass72/manuals/addons/r.fill.gaps.html
I didn't review the code, but the documentation is very nice and detailed.
I did
On Tue, Mar 21, 2017 at 12:29 PM, Benjamin Ducke wrote:
...
> I just realized that I have never committed "r.fill.gaps"
> to the add-ins repo.
>
> I have just done that now:
> http://grasswiki.osgeo.org/wiki/AddOns/GRASS_6#r.fill.gaps
cool!
...
> The code is optimized to
On 21/03/17 10:12, Blumentrath, Stefan wrote:
> Hei Martin,
>
> Same experience here. For larger datasets from LiDAR I rather use IDW
> for interpolation.
I just realized that I have never committed "r.fill.gaps"
to the add-ins repo.
I have just done that now:
Hei Martin,
Same experience here.
For larger datasets from LiDAR I rather use IDW for interpolation.
The "per hole filling" in r.fillnulls is not utilizing multiple cores and if
you have a lot of holes that can slow down the whole process significantly.
Not sure if a mask can help to avoid
Hi,
recently I was playing with DMT products available in Czech Republic, basically:
* DMR4G regular grid of points (spacing 5m)
* DMR5G irregular point network (average spacing ~3m)
When creating raster-based DMT I tested scenarios bellow:
1) create raster with resolution 5m from DMR4G (no