[GRASS-dev] [GRASS GIS] #2053: r.recode: 0.0 or 1.0 as limits do not seem to be taken into account

[GRASS GIS]

#2053: r.recode: 0.0 or 1.0 as limits do not seem to be taken into account
----------------------------------------------------+-----------------------
 Reporter:  nikosa                                  |       Owner:  grass-dev@…              
     Type:  defect                                  |      Status:  new                      
 Priority:  major                                   |   Milestone:  7.0.0                    
Component:  Raster                                  |     Version:  unspecified              
 Keywords:  r.recode, DCELL, CELL, rules, needinfo  |    Platform:  Unspecified              
      Cpu:  Unspecified                             |  
----------------------------------------------------+-----------------------

Comment(by glynn):

 Replying to [comment:4 annakrat]:
 > Any opinion on the suggested change? This is in my view quite serious
 bug.

 If it's going to deduce the type from the rules, I suggest checking for a
 decimal point prior to parsing rather than checking whether the parsed
 value is exactly representable as an integer. IOW, "0.0:1.0:0:255" will
 perform a float-int recode while "0:1:0:255" will perform a int-int
 conversion.

 I wouldn't suggest using the input map's type for the input type unless
 this will produce identical results.

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