We are currently still using ArcGIS 10 for our Desktop and Server.
We have suddenly come across the following problem and not sure what has changed that can be causing our published Mosaic Datasets to grey out when zoomed into the individual tiles level. We have made sure that the ArcGIS Server SOC and SOM accounts have full access to the directory wherein which we are publishing our Mosaic Datasets. We have also ensured that we are using UNC paths for the Mosaic Dataset. The Mosaic Dataset draws correctly within ArcCatalog, in that the Mosaic displays correctly when zoomed into the individual tiles. As soon as we publish the Mosaic Dataset, the published service will display the overviews but not the individual tiles. Our only work around at this stage is to store the images within the File Geodatabase. The problem is that we can't keep converting our aerial orthophotos into grids as we are losing the compression that they are currently stored in (ECW and MrSID) and will run out of storage space. Any help or advice will be appreciated.
After speaking to Peter Becker from ESRI, it was indeed identified that unless you have a server licence for ECW or MrSID it won't publish. I've converted our images into a File Geodatabase as ESRI Grid's and published from there. Thanks for your response.
You should convert the data to Tiff. Peter Becker would agree with that and I would be surprised if that wasn't already advised. Tiff should be faster than File Geodatabase rasters. Please note that FGDB rasters and Esri GRID are two completely seperate formats. It's impossible to store an Esri GRID in a File Geodatabase.
Thanks for the clarification of the following. Apologies for the incorrect use of terminology. I presumed that if my rasters were stored within a File Geodatabase, that they were in fact stored as ESRI GRID's. After reading your post, I investigated the format of my images within the File Geodatabase and they are FGDBR. What's the difference between FGDBR and ESRI GRID's? What's the reason that TiFF are better than storing my images within a File Geodatabase?
"Optimized image formats�??Some imagery can be slower to read than others due to their storage format or compression, and it is recommended that you convert these into more optimal formats. For example, an ASCII DEM image format is slow to read; therefore, it is recommended that you convert it to a format such as TIFF. Also, if the image is very large and not tiled it is recommended that you convert this to a tiled TIFF format to optimize disk access."
Since you have to convert from ECW you might as well go to an optimized image format like Tiff. Also, while in ArcMap go to Customize > Options > Raster tab, and make sure Created Tiled Tiff is checked on. It should be on since that is the default. You can even compress the Tiff file, so you might consider Tiled Tiff with jpeg compression. If you know Peter Becker and he is familiar with your data he can probably guide you on this quite well.
For the format questions please see the following.
Thanks for the following its greatly appreciated. I'll read through the following to better understand my options for managing our imagery and contact Peter, to confirm my proposed workflow for managing our imagery.