The input raster map is read at its native resolution, the output raster map will be produced for the current computational region set with g.region. Any MASK will be respected, masked values will be treated as NULL cells in both the input and the output map.
Spline step values ew_step for the east-west direction and ns_step for the north-south direction should not be smaller than the east-west and north-south resolutions of the input map. For a raster map without NULL cells, 1 * resolution can be used, but check for undershoots and overshoots. For very large areas with missing values (NULL cells), larger spline step values may be required, but most of the time the defaults (1.5 x resolution) should be fine.
The Tykhonov regularization parameter (lambda) acts to smooth the interpolation. With a small lambda, the interpolated surface closely follows observation points; a larger value will produce a smoother interpolation. Reasonable values are 0.0001, 0.001, 0.005, 0.01, 0.02, 0.05, 0.1 (needs more testing). For seamless NULL cell interpolation, a small value is required. The default lambda value is set to 0.01.
From a theoretical perspective, the interpolating procedure takes place in two parts: the first is an estimate of the linear coefficients of a spline function; these are derived from the observation points using a least squares regression; the second is the computation of the interpolated surface (or interpolated vector points). As used here, the splines are 2D piece-wise non-zero polynomial functions calculated within a limited 2D area. The length of each spline step is defined by ew_step for the east-west direction and ns_step for the north-south direction. For optimal performance, the spline step values should be no less than the east-west and north-south resolutions of the input map. Each non-NULL cell observation is modeled as a linear function of the non-zero splines in the area around the observation. The least squares regression predicts the the coefficients of these linear functions. Regularization avoids the need to have one one observation and one coefficient for each spline (in order to avoid instability).
A cross validation "leave-one-out" analysis is available to help to determine the optimal lambda value that produces an interpolation that best fits the original observation data. The more points used for cross-validation, the longer the time needed for computation. Empirical testing indicates a threshold of a maximum of 100 points is recommended. Note that cross validation can run very slowly if more than 100 observations are used. The cross-validation output reports mean and rms of the residuals from the true point value and the estimated from the interpolation for a fixed series of lambda values. No vector nor raster output will be created when cross-validation is selected.
r.resamp.bspline input=raster_surface output=interpolated_surface method=bicubic
# set region to area with NULL cells, align region to input map g.region n=north s=south e=east w=west align=input -p # interpolate NULL cells r.resamp.bspline -n input=input_raster output=interpolated_nulls method=bicubic # set region to area with NULL cells, align region to input map g.region raster=input -p # patch original map and interpolated NULLs r.patch input=input_raster,interpolated_nulls output=input_raster_gapfilled
g.region raster=elev_srtm_30m -p d.mon wx0 d.histogram elev_srtm_30m r.univar -e elev_srtm_30m # remove too low elevations (esp. lakes) # Threshold: thresh = Q1 - 1.5 * (Q3 - Q1) r.mapcalc "elev_srtm_30m_filt = if(elev_srtm_30m < 50.0, null(), elev_srtm_30m)" # verify d.histogram elev_srtm_30m_filt d.erase d.rast elev_srtm_30m_filt r.resamp.bspline -n input=elev_srtm_30m_filt output=elev_srtm_30m_complete \ method=bicubic d.histogram elev_srtm_30m_complete d.rast elev_srtm_30m_complete
r.resamp.bspline -c input=input_raster
Overview: Interpolation and Resampling in GRASS GIS
Available at: r.resamp.bspline source code (history)
Latest change: Thursday Aug 15 02:20:04 2024 in commit: 0d5d274b6d4ca9414f66783a967f9b1331303243
Main index | Raster index | Topics index | Keywords index | Graphical index | Full index
© 2003-2024 GRASS Development Team, GRASS GIS 8.5.0dev Reference Manual