There are many aerial sensors that are supported, including standard-frame cameras and the project files for some aerial triangle applications. Each has properties that can be refined to modify the processing applied to the imagery when it's added to a mosaic dataset. There are several defaults, but you can further modify these and save them for your own use at another time.
Raster types supported by ArcGIS are listed in the Raster Type drop-down list on the Add Rasters To Mosaic Dataset tool. If your organization has created its own raster type, or if you have modified the properties for a raster type and saved it, you may need to browse to the *.art file to choose it. Raster types can be divided into two groups: those describing files, tables, or web services and those describing products, typically from satellite sensors.
ADS
ArcGIS supports the Leica ADS40 and ADS100 airborne sensors. The input file used by this raster type is the .sup file.
When using this raster type, you can edit the raster type properties by clicking the Raster Type Properties button.
For more information about the ADS airborne sensor, see Leica airborne systems 
.
Applanix
The Applanix DSS is a medium-format, digital airborne remote sensing system, using integrated inertial technology to produce georeferenced color and color infrared (CIR) imagery. The main input file used by this raster type is the Applanix DSS eo_std.txt file.
When using this raster type, you must edit the raster type properties by clicking the Raster Type Properties button.
For more information about the Applanix raster type, see Adding Applanix DSS data to a mosaic dataset.
Frame Camera
The Frame Camera raster type allows you to add raster data captured by various aerial cameras (such as Pictometry, UltraCam, Applanix, and ISAT) to a mosaic dataset. This raster type requires you to provide two tables, the frames table and the cameras table. The frames table contains camera information specific to each frame such as the frame camera image path and the perspective X/Y/Z coordinate. The cameras table contains camera-specific parameters such as focal length and the principle point coordinate X/Y.
You need to extract this information from the frame camera metadata file and populate the information into the frames table and the cameras table. To see which fields are recognized for the frames table, see Valid fields for the frames table. To see which fields are recognized for the cameras table, see Valid fields for the cameras table.
Once the required fields are generated in the tables, you can use the frames and cameras tables as input in the Add Rasters To Mosaic Dataset tool to add images to the mosaic dataset. Assign the frames table as the input for the tool and define the cameras table path in the Frame Camera raster type properties page.
| Product type | Product type descriptions | Processing templates |
|---|---|---|
All | Generic frame camera type accounts for all frame camera types |
|
ISAT
ImageStation Automatic Triangulation (ISAT) is an automatic image point extraction and triangulation package from Intergraph . Both analog and digital cameras are supported. The input file used by this raster type is the ISAT project file.
When using this raster type, you must edit the raster type properties by clicking the Raster Type Properties button.
For more information about the ISAT raster type, see Adding data from ISAT to a mosaic dataset.
MATCH-AT
MATCH-AT is an automatic digital aerial triangulation package from Trimble Inpho. Both analog and digital cameras are supported. The input file used by this raster type is the MATCH-AT project file.
When using this raster type, you must edit the raster type properties by clicking the Raster Type Properties button.
For more information about the MATCH-AT raster type, see Adding data from MATCH-AT to a mosaic dataset.
Table raster type to support digital cameras
The Table raster type can be used to add any digital standard frame imagery to a mosaic dataset.
To learn more about the Table raster type, see Files, tables, and web raster types.
Scanned Aerial Imagery
The Scanned Aerial Imagery raster type is designed for creating mosaic datasets from scanned aerial photos. The Frame Camera raster type can also add scanned aerial photos to a mosaic dataset; however, the Scanned Aerial Imagery raster type will add an image property that is used in the block adjustment process to choose the most appropriate properties and algorithms.
This raster type requires you to provide two tables, the frames table and the cameras table. The frames table contains camera information specific to each frame such as the frame camera image path and the perspective X/Y/Z coordinate. The cameras table contains camera-specific parameters such as focal length and the principle point coordinate X/Y.
You need to extract this information from the frame camera metadata file and populate the information into the frames table and the cameras table. To see which fields are recognized for the frames table, see Valid fields for the frames table. To see which fields are recognized for the cameras table, see Valid fields for the cameras table. Once the required fields are generated in the tables, you can use the frames and cameras tables as input in the Add Rasters To Mosaic Dataset tool to add images to the mosaic dataset.
UAV/UAS
UAV/UAS raster type is designed to add aerial photos that were taken with an unmanned aerial vehicle or an unmanned aerial system. This type of imagery doesn't usually contain complete camera interior orientation information. The UAV/UAS raster type contains a camera model database that can help obtain such information by reading the camera model from the UAV/UAS image's EXIF header. In addition, this raster type also supports UAV/UAS photos that are processed by third-party software such as Pix4D and Agisoft. It can directly use the exported log file from the software as camera file or auxiliary file input in the raster type properties.
For this raster type, there are two additional tabs in the Raster Type Properties:
- Auxiliary Inputs—GPS or exterior orientation parameters of each image. The user can provide an estimated flight height if such information is available. Both Orientation File and Flight Height parameters are optional.
- Frame Camera—This tab contains the camera model information. The user can either give a custom *.cam file that contains the camera interior orientation information or select from the Camera Maker and Camera Model lists.
For more information about adding UAV\UAS data and adjusting it, see Bundle block adjust UAS or UAV data.