Home | Concepts | API | Samples |
Concepts > Rasters > Basic Principles | |||||||||||||||||
Mosaics | |||||||||||||||||
Mosaics can be displayed very quickly and are useful if the underlying data is not changing or any overlap of the images is inconsequential. However, in the case of large mosaics, the creation can be time-consuming due to the processing that is required. Preprocessing steps that may be required depend on the loading tools used, but may include pixel alignment, color balancing, and projection. During loading, processing includes the creation of pyramids and calculation of statistics, typically completed after all the individual images have been loaded. For color mapped imagery, mosaicking requires that the color map be dropped from the target raster dataset. Once mosaicking is complete, a composite color map can be added to the target. An alternative to mosaicking is to insert the source input rasters as separate records in a raster catalog. A raster catalog displays many individual rasters as a seamless layer without having to mosaic them. These are typically useful if the data in the catalog has to be updated frequently or if there is a requirement for maintaining data in areas where images overlap. However, it is also possible to mosaic source images to the individual records of a raster catalog. Raster data can be grouped together into a raster catalog by mosaicking data together that agrees in pixel bit depth, number of bands and cell registration, and alignment. Mosaciked Raster Datasets vs Raster Catalogs
It is typical to mosaic data that has been generated from the same source, such as an aerial photo flight. However, given the sophistication of the ArcSDE client application, it is possible to convert source imagery so that it can be mosaicked together assuming that such a task is necessary given the requirements of the application. The Raster API provides three modes of mosaicking:
|
feedback |
privacy |
legal |
![]() |