Select to view content in your preferred language

raster result disappears after new calculation

1071
2
07-12-2011 03:44 PM
LeoZurita1
Deactivated User
I am using the Raster Calculator to generate different results within the Default.gdb, but every time I create a new raster result, the previous one disappears from the database.
Does someone have an idea why ArcGIS 10 does that? and how I can retain the result rasters?
the temporary solution I have is saving every time the result with Export Data..., but that is time consuming.
I am attaching a screencap of how my list of layers looks..
Thanks for any input
Leo
0 Kudos
2 Replies
JeffreySwain
Esri Regular Contributor
So by your description, it sounds like you are using version 10 and putting the output in the default.gdb.  Do you know if you have it set to overwrite existing results in the options?  Also it sounds as if you are also using the Results tab to re run the analysis. Is this correct?  If you are using this workflow, the results will be overwritten.  I would not think you would need to export them, but you will have to change the output name when you reuse the command via the Results window.  The output should reside in the default gdb.  So you will have to change the name each time.
0 Kudos
LeoZurita1
Deactivated User
Hi Jeff, thanks for the response.
I checked the Geoprocessing Options and the Overwrite... is not ticked on.
I used the Results window to remake some of the operations, but every time I did change the name of the raster result, and still my previous raster disappear. In fact, when using the Raster Calculator, by default the new name of the raster is set as "rasterx+1" (x being the previous number on the series).
So, what I was showing on the screencap before is that "raster7" disappear (hence the red exclamation mark) from the Default.gdb once I run the operation for "raster8", and then again "raster8" disappear when I run the operation for "raster9". The "w6c" and "w7c" are the same grids that I store in another folder to keep the results that I needed.
Can you imagine what else can be causing the grids to be automatically deleted from the Geodatabase every time a new operation is run?
Thanks!
0 Kudos