[GRASS-dev] Re: [GRASS GIS] #959: r.surf.contour. Resulting range of values has an incorrect 0 minimum.

[GRASS GIS]

#959: r.surf.contour. Resulting range of values has an incorrect 0 minimum.
----------------------------------+-----------------------------------------
 Reporter:  clerici               |       Owner:  grass-dev@…              
     Type:  defect                |      Status:  new                      
 Priority:  normal                |   Milestone:  6.4.1                    
Component:  Raster                |     Version:  svn-releasebranch64      
 Keywords:  r.surf.contour, NULL  |    Platform:  Linux                    
      Cpu:  Unspecified           |  
----------------------------------+-----------------------------------------

Comment(by hamish):

 > Also fixed for 6.4.1 in 43605. I regard it as a change that
 > should have happened several years ago.

 sure; all backports need thorough testing, so:

 tested r.surf.contour in 6.5svn using NC dataset commands from
 http://grass.osgeo.org/wiki/Contour_lines_to_DEM#r.surf.contour

 searching for artifacts in the derivative layers,
 {{{
 r.slope.aspect elev=elev.1mcont.surf slope=elev.1mcont.surf.slope \
   aspect=elev.1mcont.surf.aspect pcurv=elev.1mcont.surf.pcurv \
   tcurv=elev.1mcont.surf.tcurv
 }}}

 the profile curvature map highlights the "thatched roof" effect at contour
 lines as before. but all in all it's pretty good and nothing that a 5x5
 r.neighbors smoothing can't clean up.

 integer 0 contour levels tested ok too:
 {{{
 r.mapcalc "elev.1mcont.sealevel = int(elev.1mcont - 115)
 }}}

 ----
 remaining in CELL-only is r.surf.idw; ''r.surf.idw is much faster than
 r.surf.idw2 but does not create floating-point maps directly. Otherwise
 the module output is practically identical.''
 see  http://grass.osgeo.org/wiki/Contour_lines_to_DEM#r.surf.idw



 thanks,
 Hamish

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/959#comment:4>
GRASS GIS <http://grass.osgeo.org>