Aerial imagery raster types

These include standard-frame cameras and the project files for some aerial triangle applications.

Caution:

For all these raster types, make sure the spatial reference information in the input files and the DEM are the same. If you need to apply a geoid correction to your elevation data, you should create a mosaic dataset containing the elevation data and use the Arithmetic function to apply the required equation. For specific steps, see Converting from orthometric to ellipsoidal heights.

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.

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 Camera 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 table as input in the Add Rasters To Mosaic Dataset to ingest images to the mosaic dataset. Assign Frames table as the input for the tool and define 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	Default Pan sharpen Pan sharpen and Multispectral Stretch

Frame Camera product 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 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.

Note:

If a MATCH-AT version 5 project has the camera information embedded, an external camera file is not required. MATCH-AT projects of other versions must have an external camera file.

Digital camera support using the Table raster type

The Table raster type can be used to add any digital standard frame imagery to a mosaic dataset. This approach requires two inputs:

1. A table containing orientation parameters, other variables, and a pointer to the processing XML
2. An RPDef file that specifies the required processing parameters and raster properties in an XML structure

Examples for these two inputs are provided in the Workflow to add Ultracam imagery to a mosaic dataset sample.

Feedback on this topic?