mosaic several existing mosaic datasets into one new mosaic dataset?

[larryzhang]

Hi, all

With 10 SP1, is it feasible to mosaic several existing (well-done) mosaic datasets or 'image services' from mosaic datasets into one new mosaic dataset?

For example, there are three historical image services (served from mosaic datasets of IKONOS 2009, QuickBird 2009, and airphoto 2009). Each contains hundreds of image datasets. All have 'overviews' in each mosaic dataset. Some of image datasets overlap, but majority covered different locations.

What we are planning to do is to add extra values from those existing historical ones (also easy to view for end users), i.e., to mosaic those existing 'image services' or 'mosaic datasets' into one new mosaic dataset, saying 'Imagery 2009'. And then, serve this new mosaic again.

We tried it and failed to locate specific functions or proper image formats during creation of Mosaic Dataset.

Any advices?

[JeffreySwain]

Per the help, image services can be added to mosaic datasets (isdef, iscdef, isref and rpdef).   There is also information on migrating to mosaic datasets. 

Adding a 'mosaic dataset' raster type should bring in the original data. There may be a need to adjust the Min/Max PS when you have so many different mosaic datasets to ensure proper display. As the spatial extent of the new combined mosaic dataset will be vastly different from the original one. 

I am not sure what processes may not be included during your import, but I would recommend placing a Support call for specific help with your complex dataset.

[larryzhang]

Thanks for your reply, Jeff

Intentionally, we did want to have the format �??image service, and/ or mosaic dataset�?? to directly be supported, in addition to isdef, iscdef, isref and rpdef, so that we can add the existing mosaic datasets into new mosaic dataset. In practice, this kind of implementation would be also helpful. For example, a larger mosaic datasets may be assigned to 2-3 people to create, and then the leader (one of them) can merge (add, import) all others have done into one mosaic dataset. Other benefits are: more easily to update mosaic datasets; and conveniently conduct QA/QC...

Currently, those existing image services were combined into MXD and served as map service. For sure, it is much easy /efficient and took us only 2 minutes. However, one of the disadvantages is that the map service is not operational within Image Analysis.

+++++++++++++++++++

By the way, can you urgently help verify if the �??View In Google Earth�?? is fully functional in ArcGIS Server 10 SP1 (image ext)?

The reason is that the KMZ files saved from ESRI image service online (like http://imagery.arcgisonline.com/ArcGIS/rest/services/LandsatGLS/Agriculture/ImageServer) work very well, including image service display and performance (caching/refreshing) in GE /GE Pro.

But, from many trials with our Dev, QA & cluster Prod server 10 SP1, it gives different conclusions. I am wondering if our servers don�??t have the latest release or service packs installed. Fore details, please link to http://forums.arcgis.com/threads/29424-Image-service-on-Google-Earth-Pro?p=98635&viewfull=1#post9863...

[larryzhang]

Hi, all,

I would like to share one thought on 'how to help efficiently and reliably update larger mosaic dataset with new raster datasets'.

Intentionally, we want minimize operation time and any negative impacts directly on the existing mosaic dataset in production server, when 'update' it.

We have just tried an approach on updating the existing mosaic dataset via a second mosaic dataset ('temporary or intermediate'). Here, both share same spatial extent and have independent  overviews with same levels.

After 'ADD' the temporary WELL-DONE mosaic dataset into the existing mosaic dataset, however, only raster datasets are imported. That is, 'overviews' are ignored in the existing mosaic dataset from the second mosaic dataset.

Is it possible to keep 'AS IS' in the existing mosaic dataset,  including raster datasets and overviews from the second one?

As indicated in another post, with 10 SP2, without 'delete' and 're-define' all overviews,  it does not work properly any more, while to update.  In other word, it seems an issue for users to only work on 'newly-added' raster datasets, if no way to import both raster datasets and overviews from temporary mosaic dataset into existing mosaic dataset.

http://forums.arcgis.com/threads/30424-Updating-amp-Generating-Overviews-on-Mosaic-Dataset-with-10-S...

[MelanieHarlow]

You can do 3 things (listed in order of recommendation) ...

1) Use the Table raster type to add your mosaic datasets into the new mosaic dataset.
Run the Synchronize Mosaic Dataset tool when you've updated the original mosaic datasets, to make sure the new mosaic dataset is updated. (This can affect the fields you've added)

2) Use the Raster Dataset raster type to add your mosaic datasets into the new mosaic dataset. This works ok when you're not adding too many. Max mosaic datasets in a mosaic dataset using this raster type is 8.

3) If you're adding the image service created from the mosaic dataset, then you'll use the Web Services raster type.

[larryzhang]

Thanks for assistance, melanie

The Option I works somehow, in particular, when the MD covering small spatial extent (100 -300 km by 300 km), if using high-resolution images like GeoEye.

However, the following strange occurrence is indentified with the local Ain_el_Abd_1970 datum & Lambert projection (Ain_el_Abd_1970_Aramco_Lambert_2 in ArcGIS 10):

�?� when the mosaic dataset is growing, which covers the whole nation (from 300 - 900 by 1500 Km), the overviews from the 'updating' mosaic dataset can be imported, but the system is not able to re-create the coarsest overviews into the existing mosaic dataset. So, this still causes some levels of the coarser overviews not visible (missing), when viewing the 'updated' mosaic dataset at the full extent;

�?� Sometimes, the re-defined (but not built) coarser overviews weirdly show different spatial reference name, which should be 'Ain_el_Abd_1970_Aramco_Lambert_2'. For example, one name presened, if source datasets in TIFF (like UTM /WGS); another name produced, if source in IMG (like UTM /local datum or WGS).

You can do 3 things (listed in order of recommendation) ...

1) Use the Table raster type to add your mosaic datasets into the new mosaic dataset.
Run the Synchronize Mosaic Dataset tool when you've updated the original mosaic datasets, to make sure the new mosaic dataset is updated. (This can affect the fields you've added)

2) Use the Raster Dataset raster type to add your mosaic datasets into the new mosaic dataset. This works ok when you're not adding too many. Max mosaic datasets in a mosaic dataset using this raster type is 8.

3) If you're adding the image service created from the mosaic dataset, then you'll use the Web Services raster type.

Yes, the Option 2 ONLY works with limited numbers of raster dataset, but can be used in any spatial extents (from small to large).