Geodatabases and raster calculator?

JacobGjesdahl

Hi, I had a model set up to work correctly but slow and someone suggested I change it to geodatabase files to make it go faster.  Now I'm facing the problem that lots of things no longer work.  The one in particular that I can't figure out on my own is that the raster calculator just makes a big block equal to 1 when it should only be doing a few areas (this worked fine before making it a geodatabase).  This is my expression:

Con( "%noview_value%" == 1 &
    ((("%beview_value%" == 0) & ("%hhview_value%" == 0)) |
    (("%beview_value%" == 1) & ("%hhview_value%" == 1))), 1, 0)

I've attached the python script so you can see what happens before this (only the stuff immediately before it should matter).  Do geodatabase raster routinely mess up raster calculator?  Does the syntax need tweaking in some way to deal with geodatabase rasters?

Thanks in advance,
Jacob

model.py.zip

OI_demo.gif

curtvprice

You should not use "%" signs within raster calculator. You should use model variables which are either raster datasets or raster layers, for example:

Con( "Noview value" == 1 & 
    ((("Beview value" == 0) & ("HHview value" == 0)) |
    (("Beview value" == 1) & ("HHview value" == 1))), 1, 0)

When you open Raster Calculator from inside the model, the valid model elements should be there in the dialog at the upper left with an icon identifying them as model variables (as opposed to raster layers in the current map).

I don't know how the gdb works into this, unless you have temporary dataset names that are confusing things.

Note, if you're working in modelbuilder, it's best to just attach the model (i.e. a tbx file with a model in it) - the python export is very difficult to interpret.