The problem is related to the following line:
grass.call([‘nnbathy’,
‘-W’, ‘%d’ % 0,
‘-i’, ‘%s’ % self._tmpxyz,
‘-x’, '%d % self.nn_w, ‘%d’ % self.nn_e,
‘-y’, ‘%d’ % self.nn_n, ‘%d’ % self.nn_s,
‘-P’, ‘%s’ % self.ALG,
‘-n’, ‘%dx%d’ % (self.cols, self.rows)],
stdout=fsock)
east, west, north and south must be real.
I have updated the SVN repository
R
···
2018-05-25 10:17 GMT+02:00 lorenzo benvenuto <benvenuto.lorenzo@gmail.com>:
Dear lists,
I’m working with the commands v.surf.nnbathy, and r.surf.nnbathy; I give as input a vector map and a raster map respectively, and differently from what I expected, the value of the interpolated raster map is not the same on the real points (I mean the points of the input maps).
It looks like a sort of smoothing effect is applied.The syntax of the command I’ve used is:
v.surf.nnbathy input=vector_map_input@maspset1 output=raster_map_output@mapset1
r.surf.nnbathy input=raster_map_input@maspset1 output=raster_map_output@mapset1, where raster_map_input@maspset1, comes from the comand
v.to.rast input=vector_map_input@mapset1 type=point output=raster_map_input@mapset1 use=attr attribute_column=TI’m using Grass 7.4.0 on Ubuntu 16.04 and I’ve downloaded the last updated nnbathy library; I’ve also treid the same commands on Grass 7.0.3 on Lubuntu but I got the same problem.
Lastly I’ve tried the command r.surf.nnbathy using Grass 6.4.4 and an old version of nnbathy library (downloaded on 2016): in this case the value of the interpolated raster map is exactly the same on the real points.
Does anyone have the same problem?
Regards,
Lorenzo
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user