#763: r.statistics method=distribution: no percentages for negative basemap
values
--------------------------+-------------------------------------------------
 Reporter:  peifer        |       Owner:  grass-...@…              
     Type:  defect        |      Status:  new                      
 Priority:  normal        |   Milestone:  6.4.0                    
Component:  Raster        |     Version:  6.4.0 RCs                
 Keywords:  r.statistics  |    Platform:  Unspecified              
      Cpu:  x86-32        |  
--------------------------+-------------------------------------------------

Comment(by peifer):

 Replying to [comment:4 glynn]:
 > ...but some code still follows the old zero-is-null convention.
 >
 [[BR]]
 This is what I observed, from a simple end-user perspective. But actually,
 I didn't want to believe it and I never dared to create a ticket whenever
 I came across such an observation.

 As stated: my current practice is to reclassify my maps so that all
 legitimate 0's (and negative values) are replaced by some more or less
 meaningful positive integer. Can you confirm that this continues to make
 sense, if one wants to be on the safe side?

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

_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to