here are some updates for v.surf.bspline vs. today's CVS.
The most important is not calling G_write_history() until after
the raster map is closed with G_close_cell().
Also:
* added opt->guisection for some options to make the GUI less
cluttered. (feel free to come up with a better name for the tab)
* added G_command_history() to save the command line into the history
file so you can later know what the input map and settings were, and
G_put_cell_title() to set the output map title. (see r.resamp.interp)
I think it is good policy that all modules which create a new raster map
should use those.
Hi Hamish and all,
Thank you for the update and the information
I'll merge this update to my v.surf.bspline version and try to send my last updates today.
Cheers,
Roberto.
Hamish ha scritto:
Hi Roberto,
here are some updates for v.surf.bspline vs. today's CVS.
The most important is not calling G_write_history() until after
the raster map is closed with G_close_cell().
Also:
* added opt->guisection for some options to make the GUI less
cluttered. (feel free to come up with a better name for the tab)
* added G_command_history() to save the command line into the history
file so you can later know what the input map and settings were, and
G_put_cell_title() to set the output map title. (see r.resamp.interp)
I think it is good policy that all modules which create a new raster map
should use those.
Hamish
--
Roberto Antolín Sánchez
Politecnico di Milano – Polo Regionale di Como
(Laboratorio di Geomatica V2.8)
Via Valleggio, 11 – 22100 Como, Italy
tel: +39 031 332 7533 || fax: +39 031 332 7519 email: roberto.antolin@polimi.it
Hi all,
you didn't update the CVS, did you? Don't do it. I uploaded it on my version and I'll send altogether today
Hamish ha scritto:
Hi Roberto,
here are some updates for v.surf.bspline vs. today's CVS.
Hamish
Now one question. Due to allocation memory problems with raster on my pc some weeks ago, I introduced a limitation on the raster dimensions only in my v.surf.bspline version. So, the CVS wasn't updated. But yesterday, a user told me that he didn't have any problem at all using the no "limited" version on CVS. So, I decide to set a limitation in the number of raster cells: about 30mill. I think it is high enough.
But, which is the best way to controll these kinds of things? Should I set a limitation in the number of cells? If afirmative, which one? Maybe, considering float cells instead double? As a possible thing I would like to allocate the whole raster (as It works now) instead of considering smaller rasters and merge them at the end.
Cheers,
Roberto.
--
Roberto Antolín Sánchez
Politecnico di Milano – Polo Regionale di Como
(Laboratorio di Geomatica V2.8)
Via Valleggio, 11 – 22100 Como, Italy
tel: +39 031 332 7533 || fax: +39 031 332 7519 email: roberto.antolin@polimi.it
