Creating and adding military data to mosaic datasets
The workflow for creating mosaic datasets and adding data to them is the same for military raster data as it is for other types of raster data. However, you should consider the properties and concepts described in the sections below to help ensure you get the most out of storing and using military data in mosaic datasets. For details on using general data in mosaic datasets, see Creating a mosaic dataset and the On-the-Fly Processing and Dynamic Raster Mosaicking article.
Workflow tips for creating mosaic datasets and adding data to them
First, create a mosaic dataset, using the Create Mosaic Dataset tool. Next, add DTED, CADRG, or CIB to the mosaic dataset using the Add Rasters To Mosaic Dataset tool. This tool loads an entire folder or nested folder hierarchy into a mosaic dataset. If you have folders in different locations, you can add several Add Rasters To Mosaic Dataset tools together in a geoprocessing model and run the whole set as a single process.
Note:RPF a.toc files cannot be added to a mosaic dataset.
Number of bands and pixel type
When you create a mosaic dataset using the Create Mosaic Dataset tool, you can specify values for the number of bands and pixel type (bit depth) the mosaic dataset will support. If you want to specify values for these optional properties, use the following table of recommended values. If you don't specify values, the Add Rasters To Mosaic Dataset tool assigns to the mosaic dataset the same properties as the first raster dataset added to the mosaic dataset.
Raster format | Recommended value for the number of bands property | Recommended value for the pixel type property |
|---|---|---|
CADRG/ECRG | 3 | 8_BIT_UNSIGNED |
CIB | 3 | 8_BIT_UNSIGNED |
DTED | 1 | 16_BIT_SIGNED |
HRE | 1 | 32_BIT_FLOAT |
Raster types
A raster type identifies metadata, such as georeferencing, acquisition date, and sensor type, along with a raster format. To support adding military data to mosaic datasets, ArcGIS includes raster types for CADRG/ECRG, CIB, DTED, HRE, and NITF data. When you add military raster data using the Add Rasters To Mosaic Dataset geoprocessing tool, select the appropriate military raster type (CADRG/ECRG, CIB, DTED, HRE, and NITF) from the Raster Type drop-down menu. Not only do these specific military raster types extract metadata information from the image and add it to the attribute table, but they also define update logic (used to determine which data gets overwritten) that is tailored to the nature of that particular type of raster data. For more information on the metadata, see File tables and lidar raster types. For more information on the logic, see Updating mosaic datasets containing military data.
Statistics and pyramids
- Calculating statistics on mosaic datasets is recommended.Note:
Mosaic dataset statistics are automatically calculated when mosaic dataset overviews are built.
- Calculating statistics on CADRG/ECRG, CIB, DTED, HRE, and NITF source data is not recommended.
- When adding NITF data to a mosaic dataset use the Stretch processing template on the NITF raster type and check the Estimate statistics check box on the Raster Type Properties tab which will improve the appearance of the data without having to calculate statistics on each source image.
- Building pyramids on CADRG/ECRG, CIB, and DTED source data is not recommended. However, pyramids may be necessary on NITF and HRE data depending on the size of the data.
Building pyramids on source data can be performed prior to adding data to a mosaic dataset using the Build Pyramids And Statistics geoprocessing tool or can be built when the data is added to a mosaic dataset by checking the Build Raster Pyramids check box on the Add Rasters To Mosaic Dataset geoprocessing tool.
Storing rasters with multiple resolutions
A mosaic dataset can store and manage multiple resolutions (pixel size) of data, and therefore, it is not necessary to create separate mosaic datasets to store each separate resolution. For example, each CIB product has a different resolution, but you can store all CIB products in a single mosaic dataset. It is advantageous to store all CIB products within a single mosaic dataset because you (or your users) have to access only one mosaic dataset.
Coordinate system considerations
You should consider the coordinate system of your source data. It is highly recommended that your data be in a projected coordinate system instead of a geographic coordinate system. Mosaic datasets make this easy because you do not have to project your source data. The mosaic dataset can have a different coordinate system than the source data. So, for example, if your source CADRG is in a geographic coordinate system, the mosaic dataset used to display it could be in a projected coordinate system.
Available templates
Available from the Defense and Intelligence community page on the ArcGIS Resource Center are desktop application templates that can help you create basemaps from CADRG/ECRG and CIB formats, such as the Scanned Maps Template and the Imagery Basemap Template. These templates include a geodatbase schema, tools, sample data, and documentation to get you started building basemaps from CADRG/ECRG, CIB, and other mosaic datasets.