Select to view content in your preferred language

ArcGIS Pro 3.4.2: The “Raster Calculator” tool fails and ends with the error “Could not save raster dataset to RasterC_6 with output format FGDBR.”

366
6
05-05-2025 02:09 AM
Labels (1)
JamalNUMAN
Legendary Contributor

ArcGIS Pro 3.4.2: The “Raster Calculator” tool fails and ends with the error “Could not save raster dataset to RasterC_6 with output format FGDBR.”

In the screenshot below, I couldn’t figure out why the “Raster Calculator” tool fails and ends with the following error:
Could not save raster dataset to RasterC_6 with output format FGDBR.

What could be the issue here?

 

Clip_547.jpg

----------------------------------------
Jamal Numan
Geomolg Geoportal for Spatial Information
Ramallah, West Bank, Palestine
Tags (1)
0 Kudos
6 Replies
DuncanHornby
MVP Notable Contributor

I think the source of the problem is the error 000539. Looking at your naming convention you are using, I'm going to guess that the input raster is INTEGER? If you need to retain it in integer, then rather than multiple by 0.5 try dividing by 2? Or convert the raster to a float.

JamalNUMAN
Legendary Contributor

What’s frustrating is that ArcGIS Pro—specifically the model builder—is not stable. With the same settings, it sometimes works as if there were never an issue. Then, after a while, running the model again triggers the same error.

Is this a bug? We never encountered such issues in ArcMap when working with rasters.

Clip_2107.jpg

 

----------------------------------------
Jamal Numan
Geomolg Geoportal for Spatial Information
Ramallah, West Bank, Palestine
0 Kudos
Robert_LeClair
Esri Esteemed Contributor

Perhaps you've seen these tools and errors warnings here:
010240: Could not save raster dataset to <value> with output format <value>.—ArcGIS Pro | Documentat...
Solved: Receiving Error 000539/Error 010240 when trying to... - Esri Community

Also, what is your bit depth for all the inputs, intermediate data, and outputs?  Are they the same?

JamalNUMAN
Legendary Contributor

Right. All the inputs, intermediate layers, and outputs have a 32-bit pixel depth, as shown in the screenshots below.
The data is attached.

 

Clip_2131.jpgClip_2132.jpgClip_2133.jpgClip_2134.jpg

----------------------------------------
Jamal Numan
Geomolg Geoportal for Spatial Information
Ramallah, West Bank, Palestine
0 Kudos
DuncanHornby
MVP Notable Contributor

Hi Jamal,

I downloaded your sample data and ran your model...it ran without error for me! Is the geodatabase you are writing into in a google drive/dropbox/one drive location, that may be file locking it? I've attached the file geodatabase with the output.

DuncanHornby_0-1746781246557.png

 

JamalNUMAN
Legendary Contributor

To reproduce the issue, simply set the mask to “LandsatTM2001.img,” as shown in the screenshots below.

 

Clip_2135.jpgClip_2136.jpg

----------------------------------------
Jamal Numan
Geomolg Geoportal for Spatial Information
Ramallah, West Bank, Palestine
0 Kudos