[GRASS-dev] [GRASS GIS] #2686: r.hazard.flood error output

GRASS GIS trac at osgeo.org
Wed Jun 3 06:29:27 PDT 2015


#2686: r.hazard.flood error output
---------------------------+---------------------------------
  Reporter:  zimbogisgeek  |      Owner:  grass-dev@…
      Type:  defect        |     Status:  new
  Priority:  normal        |  Milestone:  7.0.1
 Component:  Addons        |    Version:  svn-releasebranch70
Resolution:                |   Keywords:  r.hazard.flood
       CPU:  All           |   Platform:  All
---------------------------+---------------------------------

Comment (by madi):

 Replying to [comment:5 neteler]:
 > Replying to [comment:4 madi]:
 > > Replying to [comment:3 lucadelu]:
 > > > Hi Madi, but the code is dividing the same maps
 > > >
 > > > {{{
 > > > "$r_flood_map = $rast1 / $rast1"
 > > > }}}
 > > >
 > > > so it return for every pixel 1, is it the right behavior?
 >
 > The behaviour in question comes from r.mapcalc:
 >
 > > yes, the expected result is a binary map (yes=1, no=null)
 >
 > Here a quick test:
 >
 > {{{
 > r.mapcalc "result = 1/1"
 > r.univar -g result | grep 'min\|max\|null'
 > null_cells=0
 > min=1
 > max=1
 >
 > r.mapcalc "result2 = 0/0"
 > r.info result2 | grep 'min\|max\|null'
 >  |   Range of data:    min = NULL  max = NULL
 >
 > r.mapcalc "result3 = null()/null()"
 > r.info result3 | grep 'min\|max\|null'
 >  |   Range of data:    min = NULL  max = NULL
 > }}}
 >
 > Is this what should happen in r.hazard.flood?

 Precisely so.

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



More information about the grass-dev mailing list