Pixel depth problem Mosaic Dataset Analyzer: Error 70127

554
14
Jump to solution
04-13-2017 05:10 PM
Highlighted
MVP Regular Contributor

I have a MD that is giving me this error when analyzed 

"The pixel type of the raster associated with the mosaic dataset item indicates that pixel values might be outside of the range allowed by the mosaic dataset."

The thing I do not get is that the MD is set to the same pixel depth as the source rasters? I do have a function applied to change meters to feet... 

MD properties

I don't understand why this error is showing up...

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
Highlighted
Esri Contributor

Forest,

Did you change the output pixel type of the function you used to match your mosaic dataset's pixel type? What function you use matters less than setting the right output pixel type. That is what is causing the analyzer to throw the error.

-Prashant

View solution in original post

14 Replies
Highlighted
MVP Esteemed Contributor

I am sure it is nothing, but the nodata value is ever so slightly different and the 'edit' option appears in the latter.  I presume the elevations are in keeping with other values even when converted to feet? and does it work without the function applied?

0 Kudos
Highlighted
MVP Regular Contributor

Ya, it is weird. I was thinking that in theory one could have a "large" 32bit float then when one divides by .3048 to go from meters to feet (the function) the output could be larger then then the 32bit float container. But even when I set the pixel depth to 64bit it still does shows the error. The data in the MD looks fine however. I don't know. I want to just ignore it. But I am having some problems getting this MD to work so I am trying to track down all errors.

0 Kudos
Highlighted
MVP Esteemed Contributor

I don't think those elevations  Single-precision_floating-point_format

0 Kudos
Highlighted
MVP Regular Contributor

Right, my elevation values are always going to be fine in a 32bit floating point. But arc may not be looking at what the values are. But just at the range of possible values.If this is the case I think esri should think about demoting this issue from a error to a warning.

Also the error is gone if I remove the function.

0 Kudos
Highlighted
MVP Esteemed Contributor

Which makes it stranger since the raster function list here applies to rasters and mosaic datasets, so one would presume an Arithmetic multiplication would not upscale the result. What about Unit Conversion?

0 Kudos
Highlighted
MVP Regular Contributor

Same error.

0 Kudos
Highlighted
MVP Esteemed Contributor

I give up... meters are better anyway   I would pass this on to tech support, since no one else monitoring the thread has any ideas to share either

0 Kudos
Highlighted
MVP Esteemed Contributor
Highlighted
MVP Regular Contributor

Hahaha, sure they are. Project requirement is for feet. My source rasters are mixed units in the vertical so I will have to covert no mater what.... 

I may call ersi next week on it... Who knows maybe an esri person will see this post Monday.

0 Kudos