[GRASS-dev] Re: [GRASS GIS] #1388: r3.univar gives bad results for cell counts

[GRASS GIS]

#1388: r3.univar gives bad results for cell counts
-----------------------+----------------------------------------------------
 Reporter:  hamish     |       Owner:  grass-dev@…              
     Type:  defect     |      Status:  new                      
 Priority:  critical   |   Milestone:  6.4.2                    
Component:  Raster     |     Version:  svn-develbranch6         
 Keywords:  r3.univar  |    Platform:  Linux                    
      Cpu:  x86-32     |  
-----------------------+----------------------------------------------------

Comment(by hamish):

 Replying to [comment:3 mmetz]:
 > I have submitted some more (tested) fixes, particularly for zonal stats.

 thanks, I'll give it a better look after I get back from sea.

 > IMHO, it may be safer to have val_f and val_d as FCELL and
 > DCELL because they are used in G3d_getValue().

 my main concern is that I apparently went to the trouble of adding a
 comment that they should be available for general use, so I'd like to
 audit that we aren't breaking any assumptions based on that comment, and
 no new casts are needed.


 ----
 also I notice that r3.to.rast is giving me just min=max=0 2D maps from
 seemingly good 3D floating point temperature data? (gr6.5; r3.null was run
 to remove value=99.999 null cells, maybe that had something to do with
 it?)


 thanks,
 Hamish

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