On Tue, Jun 2, 2015 at 10:18 AM, Tomáš Brunclík <[email protected]> wrote: > Hello all, > after about 10 hours of processing (the computer got to sleep state over > night) still progress 0%.
You may file an enhancement ticket - likely r.surf.contour has never been optimized. > Is it normal on such region size and core i5 PC? Well, it will only use 1 CPU unless being parallelized. But often a code optimization is more efficient (as done for many modules in GRASS GIS 7, see https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures). Maybe there is potential in r.surf.contour as well. Just one other hint below: > Dne 1.6.2015 v 11:44 Tomáš Brunclík napsal(a): > > Hi Irantzu, > I am just trying again with this dataset: > https://dl.dropboxusercontent.com/u/24062833/ES2003_1m_mb_contour.zip ... > For the record, the commands I used: > > #First created new location using the data as source of its projection > settings and imported the file (from startup GUI), then: > > g.region vector=ES2003_1m_mb_contour@PERMANENT > > g.region res=1 better use g.region res=1 -a in order to avoid "odd" pixel resolution: > g.region -p ... > nsres: 0.99998578 > ewres: 1.00006542 ... this will then become precisely 1.0. I'll now try myself the interpolation. Markus _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
