Hello all,
For years, I've been able to create an 8-bit signed mosaic dataset and it would indicate, in its Properties dialog, that the mosaic dataset was an "unsigned int". I could then set a NODATA value of -128 for the rasters I was going to add to that dataset.
I am trying to do same in Pro 3.5.1 but am having no luck. It seems to me I ran into the same problem last year (or even earlier) so am guessing that something has changed in the "Create Mosaic Dataset" tool's functionality.
When I use "Create Mosaic Dataset" and select "8-bit signed" for the Pixel Type (Product Definition=None; Number of Bands=1) , I end up with a mosaic dataset that is identified as a "char" in its Properties dialog and I am unable to set a negative NODATA value for it.
It is possible to change the pixel type of the mosaic dataset in the Properties dialog itself. Doing that allows me to set the NODATA value to -128 using the dialog also. However, I am creating a number of these and using a model to do so; stopping in the middle of a process and forced to interact with the GUI in order to continue is not desirable.
Anyone know if there's a way to get around this? The functionality is obviously still in there somewhere, since you can change it in the GUI. How can I get at it through the tool's command line?
Any suggestion are welcome.
Additional info added later:
I am still able to create the mosaic dataset as 8-bit signed in ArcCatalog 10.8.1 and see, in its Properties panel, that the Pixel Type is "signed integer". However, viewing the same mosaic dataset's properties in Pro identifies it as "8-bit char".
Interestingly, I am unable to use the "Define Mosaic Dataset NoData" in ArcCatalog 10.8.1 either. I have to use the GUI to set it to -128 (just like Pro, after I've changed the Pixel Type in Pro).
The last time I ran all these models to create fgdbs, mosaic datasets, etc. was in ArcMap 10.4.1. At that time, setting the NODATA value using the GP tool worked. I guess it's been a while.
