Parts of raster disappear

[WilliamIsaacs]

Howdy,

Set up:

I have created a raster mosaic in ArcGIS 10.2.2 of georeferenced  .tif aerial photographs. size is about 9.5 Gigs uncompressed, and the tif's are 1 band,16 bit that I converted from MrSIDs in ArcMap. I have defined and built overviews, created pyramids and stats, seamlines and blended along the seamline for mosaic method. This is everything that I normally do to make a Raster Mosaic in a fgdb and never had this issue before.

so here is my question:

When I'm at full extent the image is fine, as I zoom in parts of the raster disappear(not checkerboard-ing just white background) and as I move the image different parts with appear or disappear. The pattern changes depending on which mosaicking method I select. I have found a work around but I would rather not lose any data by exporting the mosaic as new raster. Any suggestions or possible solutions?

Thanks

Will

[WilliamIsaacs]

Yes there was overlap, about 1/3 of the images left and right and 1/4 top and bottom.

[GabrielUpchurch1]

So just to verify, when you set the Mosaic Method to 'Seamline' and Mosaic Operator to 'Blend,' you are observing the issue?  Would it be possible for you to post a screenshot depicting an example of the issue (with the seamlines layer turned on).  Also, what Computation Method and Sort Method did you specify when building the seamlines?

These are the first places I would begin investigating.  If your current solution meets your needs, don't feel compelled to provide this info.  I am inquiring just in case you are interested in figuring out what was causing the unexpected behavior.

[WilliamIsaacs]

Here are a few screenshots the first two are when the method is along seamlines and blend, the last is closest to center and blend.

[WilliamIsaacs]

Also the computational method is Radiometric and the sort method is North_west for the generate seamlines. I am just as curious so any help on figuring it out is appreciated.  I had to get it done, that is why I went around the issue. I would love to know why it did it and what I need to do differently in the future if it were to happen again.

[GabrielUpchurch1]

I am happy to assist if I can.  Mosaic datasets can be pretty complex beasts so this may take some back and forth.  I am pondering the possibilities based on the current info but after reviewing the screenshots, they all seem to suspiciously be displaying ~20 datasets.  I know you mentioned adjusting the "Maximum number per mosaic"  setting but can you verify the setting is actually set to 50 and also that you have removed and re-added the mosaic dataset to ArcMap?  This is worth double-checking before we delve into the other possibilities.

[WilliamIsaacs]

Thank you, I used the toolbox tool called "Set Mosaic Dataset Properties" to set the "Max number per mosaic" to 50. Then I right-clicked the Mosaic in the Catalog to screenshot the properties and it was still 20 so I manually typed in 50 and clicked ok and the rasters appeared. So that was the issue, it seems. Thank you for everyone who helped on this. Timothy Hales​ you had the correct answer in the beginning i just didn't correct it properly. 

[GabrielUpchurch1]

Awesome!  Glad it ultimately turned out to be an easy fix.  I am not surprised Timothy Hales​ had the correct solution.  I may have learned a thing or two about working with raster data in Desktop from him.

[TimothyHales]

William Isaacs​  - Glad to hear that worked for you.

Gabriel Upchurch​ - Thanks for the kind words! It's all about knowledge transfer, and I am sure you are passing is along as well.

[SubuSwaminathan1]

William,

I would suggest you log a bug with esri tech support. I found a similar bug around the time of 10.1 SP1 where 'Set Mosaic Dataset Properties' does not really set and save the correct value in mosaic dataset properties. Even the ArcCatalog way of manually set and save was not working consistently for certain properties. This made it impossible to automate mosaic dataset processing using model builder or python scripts. I had hoped these got fixed in later versions but does not look like it from your experience.

Confirm the bug if it still exists. It will save others a lot of time.

Thanks

Subu

[RebeccaStrauch__GISP]

William, you may want to re-mark the correct answer

Mark a reply as the Correct Answer​  Since the one you have marked now wasn't the answer.  it will make it easier for others to find in the future.  (Maybe Gabriel's?  I didn't see Timothy's)