Back to Top

Aerial imagery raster types

In this topic

  1. ADS
  2. Altum
  3. Use Applanix imagery
  4. AVIRIS
  5. ESRI Frame XML
  6. Frame Camera
  7. Generic RPC
  8. GORI
  9. ISAT imagery
  10. Match-AT imagery
  11. MOD
  12. PAR
  13. RedEdge
  14. Scanned Aerial Imagery
  15. Table raster type to support digital cameras
  16. UAV/UAS
  17. Vexcel Osprey

Raster types supported by ArcGIS AllSource are listed in the Raster Type drop-down list in 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. You can divide raster types into two groups: those describing files, tables, or web services and those describing products, such as an aerial camera.

Caution:

For all of 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, 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.

ADS

ArcGIS AllSource supports the Leica ADS40 and the ADS100 Airborne Sensors. The input file used by this raster type is the .sup files.

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 systemsLeica airborne systems.

Altum

MicaSense Altum produces multispectral, thermal, and high-resolution imagery from a multisensor system. The input files used by this raster type are the .tif files for the bands, one from each sensor, including five multispectral bands (blue, green, red, red edge, near-infrared) and one thermal band.

When adding Altum data to a mosaic dataset, files will be filtered to search for the following extensions: *_1.tif, *_2.tif, *_3.tif, *_4.tif, *_5.tif, *_6.tif. Additionally, three processing templates are supported: All bands, Multispectral, and Thermal. The All bands and Multispectral templates can process pixels into radiance or surface reflectance using the information from the imagery. The Thermal template processes pixels into degrees Celsius.

Use Applanix imagery

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.

  1. Create a mosaic dataset.
  2. In the Catalog pane, right-click the mosaic dataset and click Add Rasters.

    The Add Rasters to Mosaic Dataset tool opens.

  3. Click the Raster Type drop-down list and click Applanix.
  4. Click the Edit Raster Type Properties button.

    The Raster Type Properties dialog box appears. Here you will enter specific information about the DEM and the camera.

  5. Click the Camera Definition tab to define the camera information, which is often found in a file supplied by the data or camera vendor.
  6. Click the Camera Model drop-down arrow and make a selection.

    This sets any predefined parameters for the chosen camera model. The following camera models are available:

    Camera modelDefaults

    DSS 322

    • Number of Pixels (Columns): 5,436
    • Number of Lines (Rows): 4,092
    • Pixel Size (Microns): 9

    DSS 439

    • Number of Pixels (Columns): 7,216
    • Number of Lines (Rows): 5,412
    • Pixel Size (Microns): 6.8
    Applanix DSS camera models

  7. Enter a value for Focal Length and choose the appropriate units.
  8. Enter the principal point of autocollimation along the x-axis in the PPA X text box and choose the appropriate units.
  9. Enter the principal point of autocollimation along the y-axis in the PPA Y text box and choose the appropriate units.
  10. Click the Type of Distortion drop-down arrow , and choose either Konrady Coefficients or Radial Distortions.
    • If you choose Radial Distortions, a table appears where you can enter the values provided in the camera calibration report. This is the recommended method. Once you've entered the values in this table, you can view the calculated coefficients by changing the Type of Distortion method to Konrady Coefficients.
    • If you choose Radial Distortions, you must click the Radial Lense Distortion Coefficient Method drop-down arrow and choose one of the options:
      • Konrady (Esri)
      • Konrady (USGS)

      This may already have been applied by the camera's postprocessing software. Verify that this distortion value is needed. If it is not needed, leave the 0 value defaults.

      ArcGIS uses Konrady coefficients to calculate radial distortion correction for standard-frame cameras. These coefficients model the radial distortion as a function of the radial distance from the center (r) as a power sequence. There are two ways these coefficients can be applied: USGS Konrady and Esri Konrady. They differ in how they use the coefficients, so the method used should match the way the coefficients were derived.

      The Esri equation is 

      error = K1 + K2 * r2 + K3 * r4

      The USGS equation is 

      error = K1 + K2 * r3 + K3 * r5

      where K1, K2, and K3 are Konrady coefficients and r is the radial distance from the center.

  11. Click the General tab.
  12. Check your exterior orientation file.

    If the extension is not .txt, you must enter it in the Filter text box. For example, if it is .dat, change .txt to .dat.

  13. Optionally, click the Save As button to save these changes to the raster type by saving the raster type to a file that can be reused in place of the Applanix raster type in the drop-down list.
  14. Click the Processing tab to set the properties to define the elevation model used in the orthorectification of the imagery.

    The following are tips for using a DEM:

    • If your DEM is smaller than the extent of the collection of images, the images are cropped to the extent of the DEM. Also, the DEM impacts the orthorectification, so it is best if the DEM is at least as large, in extent, as the collection of images.
    • Make sure the spatial reference system in the exterior orientation file and the DEM are the same; otherwise, you may have to modify the DEM by either checking the Geoid check box or entering z offset and factor values. Optionally, you can apply a geoid correction to your elevation data by creating a mosaic dataset containing the elevation data and using the Arithmetic function to apply the required equation.

    • You can use a DEM stored as a raster dataset (in any ArcGIS-supported raster format), stored in a raster catalog, a mosaic dataset, an image service, or a WCS service.

    • If you have multiple DEM raster datasets you can add them to a mosaic dataset to create a single dataset that can be used as the DEM.

    • If the format has a NoData value, it is supported. You can verify the NoData value in the raster properties of your raster dataset. If you need to convert a value to NoData, use the Copy Raster tool and define a value for the NoData Value parameter. This tool will output a new raster dataset. If you do not want to create a new raster dataset, you can add your DEM to a mosaic dataset and use the Define Mosaic Dataset NoData tool to define the NoData value. Using this method you can define more than one value to be interpreted as NoData.

  15. Click the Orthorectification drop-down arrow to choose one of the following elevation methods:
    DEM

    Choose the DEM from the raster dataset, mosaic dataset, image service, or WCS service you want to use for orthorectification.

    Constant elevation

    Enter the value of the constant (average) elevation for the area covered by the images.

    Average Elevation from Image Metadata

    Average elevation does not apply to Applanix data; therefore, do not use this.

    Average Elevation from DEM

    Average elevation does not apply to Applanix data; therefore, do not use this.

  16. Optionally, you may need to set some elevation adjustment parameters if the DEM option was chosen.

    Z offset

    The base value to be added to the elevation value in the DEM. This could be used to offset elevation values that do not start at sea level.

    Z factor

    The z-factor is a scaling factor used to convert the elevation values for two purposes:

    • To convert the elevation units (such as meters or feet) to the horizontal coordinate units of the dataset, which may be feet, meters, or degrees.
    • To add vertical exaggeration for visual effect.

  17. Click the Auxiliary Inputs tab.
  18. Click the browse button, browse to the folder containing the input images, and click OK.
  19. Click OK to close the Raster Type Properties dialog box.
  20. Click the Input drop-down arrow and click File.
  21. Click the browse button, browse to the exterior orientation file .txt, and click Open.

    The text file is added to the Source list.

  22. Define additional information, if necessary, in the Advanced Options section.
    1. If the spatial reference for the input data is different than the mosaic dataset, define it with the Coordinate system for Input Data parameter.
    2. If the data does not have pyramids or statistics, calculate them by checking Build Raster Pyramids and Calculate Statistics. This is highly recommended.
  23. Click OK to run the tool and add the data to the mosaic dataset.

The footprints created are simple polygons to define the four corners of the unorthorectified image. You should modify the footprints to match the shape of the orthorectified image before building overviews. These steps are shown next.

Recalculate the footprints

  1. Open the Build Footprints tool.
  2. Browse to the mosaic dataset, or click the Mosaic Dataset drop-down arrow to choose the mosaic dataset layer.
  3. Change the Minimum Data Value and Maximum Data Value low and high extents of the bit depth, such as 0 and 255 for 8-bit data.
  4. To shrink the footprints, specify a Shrink Distance value.

    This value is specified in the units of the mosaic dataset's coordinate system and will reduce the overall size of each footprint polygon.

  5. Click OK to run the tool.

Build overviews

  1. Open the Build Overviews tool.
  2. Browse to the mosaic dataset, or click the Mosaic Dataset drop-down arrow to choose the mosaic dataset layer.
  3. Click OK to run the tool.

The overviews take some time to generate. Once completed, the mosaic dataset is ready to use.

AVIRIS

Airborne Visible / Infrared Imaging Spectrometer (AVIRIS) is an airborne sensor that captures images in 224 contiguous spectral bands, with wavelengths from 400 to 2,500 nanometers. This sensor, also known as AVIRIS-Classic, has been in use since 1986 and has been replaced by the next generation sensor, AVIRIS-NG (Next Generation), which measures wavelength ranges from 380 to 2,510 nanometers. The hyperspectral images from both instruments are stored in ENVI format. Example applications of the AVIRIS hyperspectral images include tracking methane leaks, detecting oil spill, and conducting wetland change analysis. For more information about the instruments, their applications, and data access, see AVIRIS-Classic and AVIRIS-NG.

The AVIRIS raster type supports data from both AVIRIS-Classic and AVIRIS-NG. This raster type has only one processing template, the Default template, which supports both radiance and surface reflectance data, and adds all bands to the mosaic dataset.

Note:

Since the .hdr file extension is not browsable as a raster dataset in the Catalog pane, use the Add Hyperspectral Data dialog box to add one AVIRIS image to the map.

Product typeProcessing templates
  • Default
  • Default Processing Template
  • Level1
  • Radiance
  • Level2
  • Surface Reflectance

ESRI Frame XML

The Esri Frame XML is an image support text file that contains the interior and exterior orientation parameters required to accurately project the associated image on a map. The metadata contained in the .xml file is already adjusted so no further block adjustment is required. The advantage of using the Esri Frame XML is that it enables the raw imagery to be accurately rendered in its correct geospatial location without the need for orthorectification. The .xml file is a derivative of the Export Mosaic Dataset Items geoprocessing tool and can be used to create .xml support files for drone, digital aerial, and scanned aerial imagery data that has already been block adjusted.

The Esri Frame XML can be created by doing the following steps.

  1. Create either an Ortho mapping workspace that contains, drone, digital aerial, or scanned aerial imagery data, or a Reality mapping workspace containing drone or digital aerial imagery.
  2. Perform a block adjustment of the images, or if working with previously adjusted data, move to the next step. For additional information on block adjustment, see the topic Block adjustment.
  3. Use the selection tool to highlight the images you want to export with their orientation data saved in the .xml file.
  4. With the selection still active, on the ArcGIS AllSource main menu, click Analysis > Tools in the Geoprocessing category.

    The Geoprocessing pane appears.

  5. In the Geoprocessing pane search box, enter Export Mosaic Dataset Items and click Enter.

    The search results are presented in the Geoprocessing pane.

  6. From the search results, click Export Mosaic Dataset Items to open the tool.

    The Export Mosaic Dataset Items tool dialog box appears.

  7. For Mosaic Dataset, select Image Collection from the drop-down list.
  8. For Output, specify a location to save the results.
  9. Below NoData Value, check the Export images to image space check box.
  10. Accept all other defaults and click Run.

    This copies the selected images and their block adjustment information saved in an .xml file to the folder identified earlier in the process.

Once completed, the copied images can be added to the map view or the Stereo window (if overlapping), and rendered in their correct geographic location using the image information stored in the associated .xml file.

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 Frames table schema. To see which fields are recognized for the cameras table, see Cameras table schema.

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 ingest images to the mosaic dataset. Assign the frames table as the input for the tool and define the cameras table path on the Frame Camera raster type properties page.

Generic RPC

When using the Ortho mapping workflow, the Generic RPC raster type enables the input and display of satellite images that have their Rational Polynomial Coefficient (RPC) sensor model information stored as an .rpc txt file. This may include the following:

  • Natively supported satellite imagery that has been block adjusted using third party software, and have the adjusted RPC information stored in a generic .rpc text file.
  • Satellite imagery that is not natively supported, but stores their RPC data in a .rpc text file, such as BlackSky satellite imagery.

If working outside the Ortho mapping workspace environment, satellite images with their RPC data stored in a .rpc text file can be added to a mosaic dataset by using the Raster Dataset raster type. When working with this type of data, it is important that the .rpc file and the associated images are in the same folder.

Do the following to add satellite images with an associated .rpc text file to a mosaic dataset.

  1. Create a mosaic dataset.
  2. In the Catalog pane, right-click the mosaic dataset and click Add Rasters.

    The Add Rasters to Mosaic Dataset tool opens.

  3. Click the Raster Type drop-down list and select Raster Dataset.
  4. In Input Data, click the drop-down menu and select Folder.
  5. Browse to and select the folder containing the .rpc files and click OK.
  6. Accept all other defaults and click Run.

Once completed, the satellite images will be added to the mosaic dataset and displayed in the map.

Do the following to add satellite images with an associated .rpc text file to a Workspace.

  1. On the Imagery tab, in the Ortho Mapping group, click the New Workspace drop-down menu and select New Workspace.
  2. In the Workspace Configuration window, type a name for your workspace.
  3. In the Workspace Type drop-down menu, choose Ortho Mapping.
  4. For Sensor Data Type select Satellite from the drop-down menu.
  5. Accept all other defaults and click Next.
  6. In the Image Collection window, under the Sensor Type drop-down menu, choose Generic RPC.
  7. For Folder Containing Images, click the Browse button, navigate to the image folder on your machine, select it, then click OK.
  8. Under Spatial Reference, click the Browse button.
  9. In the Spatial Reference window, set an appropriate x,y and z-coordinate system, then click Next.
  10. In the Data Loader window, accept the defaults and click Finish.

GORI

A GORI file, a derivative of Leica HxMap, is an ancillary text file that stores the spatial reference, interior and exterior orientation parameters required to support block adjustment of the image it is associated with. Each image within the aerial survey project will have one associated GORI file. Images with an associated .gori file can be added to a mosaic dataset using the Leica HxMap raster type. When creating an Ortho Mapping or Reality Mapping workspace, and the Sensor Data Type selected is Aerial Digital, the Leica HxMap raster type can be accessed from the Sensor Data Type drop-down list on the Image Collection page. See the following topics for additional information on creating an Ortho mapping or Reality mapping workspace containing aerial digital imagery.

Note:

When working with GORI data, it is important that the .gori file and the associated images are in the same folder.

Do the following to add images with an associated .gori file to a mosaic dataset.

  1. Create a mosaic dataset.
  2. In the Catalog pane, right-click the mosaic dataset and click Add Rasters.

    The Add Rasters to Mosaic Dataset tool opens.

  3. Click the Raster Type drop-down list and select Leica HxMap.
  4. In Input Data, click the drop-down menu and select Folder.
  5. Browse to and select the folder containing the .gori files and click OK.
  6. Accept all other defaults and click Run.

Once completed, the images associated with the GORI files are added to the mosaic dataset and displayed in the map.

ISAT imagery

ImageStation Automatic Triangulation (ISAT) is an automatic image point extraction and triangulation package from Hexagon. Both analog and digital cameras are supported. The input file used by this raster type is the ISAT project file.

You can add ISAT data to a mosaic dataset using the ISAT raster type.

  1. Create a mosaic dataset.
  2. Create a mosaic dataset.
  3. In the Catalog pane, right-click the mosaic dataset and click Add Rasters.

    The Add Rasters to Mosaic Dataset tool opens.

  4. Click the Raster Type drop-down list and click ISAT.
  5. Click the Edit Raster Type Properties button.

    The Raster Type Properties dialog box appears. Here you will enter specific information about the DEM and the camera.

  6. Click the Properties tab.

    This tab allows you to specify the properties that will define the elevation model used in the orthorectification of the imagery.

    Tip:

    Make sure the spatial reference system in the exterior orientation file and the DEM are the same; otherwise, you may have to modify the DEM by either checking the Geoid check box or entering z offset and factor values.

  7. Click the Orthorectification drop-down to choose one of the elevation methods:

    Average Elevation from Image Metadata

    The average elevation is read from the project file.

    Average Elevation from DEM

    The average elevation is read from the DEM provided.

    Constant elevation

    Enter the value of the constant (average) elevation for the area covered by the images.

    DEM

    Choose the DEM from the raster dataset, mosaic dataset, image service, or WCS service you want to use for orthorectification.

    If you need to apply a geoid correction to your elevation data, create a mosaic dataset containing the elevation data and use the Arithmetic function to apply the required equation.

  8. Optionally, you may need to set some elevation adjustment parameters if the DEM option was chosen.

    Z offset

    The base value to be added to the elevation value in the DEM. This could be used to offset elevation values that do not start at sea level.

    Z factor

    The z-factor is a scaling factor used to convert the elevation values for two purposes:

    • To convert the elevation units (such as meters or feet) to the horizontal coordinate units of the dataset, which may be feet, meters, or degrees.
    • To add vertical exaggeration for visual effect.

  9. Click the Auxiliary Inputs tab.
  10. Click the Photo File browse button and browse to the ISAT photo file.
  11. Click the Camera File browse button and browse to the ISAT camera file.
  12. Click OK.
  13. Optionally, click the General tab.

    By clicking the Save As button, you can save the changes made to the raster type so it can be reused at another time.

    To use the .art file you save, you can browse to it rather than choosing ISAT in the Raster Type list.

  14. Click OK.
  15. Click the Input drop-down arrow and click File.
  16. Click the Browse button, browse to the ISAT project file, and click Open.

    The text file is added to the Source list.

  17. Optionally, click the General tab.

    By clicking the Save As button, you can save the changes made to the raster type so it can be reused at another time.

    To use the .art file you save, you can browse to it rather than choosing ISAT in the Raster Type list.

  18. Optionally, if you won't be recalculating the footprints, you can check Update Overviews.

    You may want to shrink the footprints. If so, don't check Update Overviews; complete running this tool. Use the Build Footprints tool and specify a value for Shrink Distance. Also, change the maximum and minimum data values to the highs and lows of the bit depth, such as 0 and 255 for 8-bit data. Finally, you can build overviews using the Build Overviews tool.

  19. There may be some additional details you need to define within the Advanced Options section, although they are not always necessary.
    1. If the spatial reference for the input data is different from the mosaic dataset, you will need to define one with the Coordinate system for Input Data parameter.
    2. If the data does not have pyramids or statistics, you calculate them by checking Build Raster Pyramids and Calculate Statistics.
  20. Click OK to run the tool and add the data to the mosaic dataset.

Match-AT imagery

MATCH-AT Trimble Inpho 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.

You can add Match-AT data to a mosaic dataset using the Match-AT raster type.

  1. Create a mosaic dataset.
  2. In the Catalog pane, right-click the mosaic dataset and click Add Rasters.

    The Add Rasters to Mosaic Dataset tool opens.

  3. Click the Raster Type drop-down list and click Match-AT.
  4. Click the Edit Raster Type Properties button.

    The Raster Type Properties dialog box appears. Here you will enter specific information about the DEM and the camera.

  5. Click the Properties tab.

    This tab allows you to specify the properties that will define the elevation model used in the orthorectification of the imagery.

    Tip:

    Make sure the spatial reference system in the exterior orientation file and the DEM are the same; otherwise, you may have to modify the DEM by either checking the Geoid check box or entering z offset and factor values.

  6. Click the Orthorectification drop-down to choose one of the elevation methods:

    Average Elevation from Image Metadata

    The average elevation is read from the project file.

    Average Elevation from DEM

    The average elevation is read from the DEM provided.

    Constant elevation

    Enter the value of the constant (average) elevation for the area covered by the images.

    DEM

    Choose the DEM from the raster dataset, mosaic dataset, image service, or WCS service you want to use for orthorectification.

    If you need to apply a geoid correction to your elevation data, create a mosaic dataset containing the elevation data and use the Arithmetic function to apply the required equation.

  7. Optionally, you may need to set some elevation adjustment parameters if the DEM option was chosen.

    Z offset

    The base value to be added to the elevation value in the DEM. This could be used to offset elevation values that do not start at sea level.

    Z factor

    The z-factor is a scaling factor used to convert the elevation values for two purposes:

    • To convert the elevation units (such as meters or feet) to the horizontal coordinate units of the dataset, which may be feet, meters, or degrees.
    • To add vertical exaggeration for visual effect.

  8. Click the Auxiliary Inputs tab.
  9. Click the Camera browse button, browse to the camera file, and click Open.

    This is an optional parameter and must be specified if the camera information is not in the project file.

    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.

  10. Click OK.
  11. Click the Input drop-down arrow and click File.
  12. Click the browse button, browse to the Match-AT project file (.prj), and click Open.

    The project file is added to the Source list.

  13. Optionally, click the General tab.

    By clicking the Save As button, you can save the changes made to the raster type so it can be reused at another time.

    To use the .art file you save, you can browse to it rather than selecting Match-AT in the Raster Type list.

  14. Optionally, if you won't be recalculating the footprints, you can check Update Overviews.

    You may want to shrink the footprints. If so, don't check Update Overviews; complete running this tool. Use the Build Footprints tool and specify a value for Shrink Distance. Also, change the maximum and minimum data values to the highs and lows of the bit depth, such as 0 and 255 for 8-bit data. Finally, you can build overviews using the Build Overviews tool.

  15. There may be some additional details you need to define within the Advanced Options section, although they are not always necessary.
    1. If the spatial reference for the input data is different from the mosaic dataset, you will need to define one with the Coordinate system for Input Data parameter.
    2. If the data does not have pyramids or statistics, you calculate them by checking Build Raster Pyramids and Calculate Statistics.
  16. Click OK to run the tool and add the data to the mosaic dataset.

MOD

The MOD raster type is scanned or digital aerial imagery that has been photogrammetrically processed and stored as a .MOD metadata file. MOD files are generated by block adjustment packages such as PAT-B and the legacy ISM DiAP system. The .MOD file contains the interior and exterior orientation parameters required to accurately project the associated images on a map.

When using this raster type, you must edit the raster type properties by clicking the Raster Type Properties button Properties and selecting MOD.

You can add MOD data to a mosaic dataset using the MOD raster type.

  1. Create a mosaic dataset. See Create a mosaic dataset for details.
    1. For Coordinate System, click the Select Coordinate System button Select Coordinate System, and select the projected coordinate system that matches the MOD files spatial referencing system.

    The mosaic dataset is created, added to the geodatabase, and loaded as a layer in the Contents pane.

  2. In the Catalog pane, right-click the mosaic dataset and click Add Rasters.

    The Add Rasters to Mosaic Dataset geoprocessing tool opens.

  3. Type the name of your mosaic dataset. Click the Raster Type drop-down list and select MOD.
  4. Click the Raster Type Properties button Properties.

    This opens the Raster Type Properties dialog box. Here you will enter specific information about the path to the images and, optionally, add a DEM.

  5. In the Raster Type Properties dialog box, click the Processing option.
  6. Click the Orthorectification drop-down to choose one of the elevation methods:

    Average Elevation from Image Metadata

    The average elevation is read from the project file.

    Average Elevation from DEM

    The average elevation is read from the DEM provided.

    Constant elevation

    Enter the value of the constant (average) elevation for the area covered by the images.

    DEM

    Choose the DEM from the raster dataset, mosaic dataset, image service, or WCS service you want to use for orthorectification.

    If you need to apply a geoid correction to your elevation data, create a mosaic dataset containing the elevation data and use the Arithmetic function to apply the required equation.

  7. Optionally, you may need to set some elevation adjustment parameters if the DEM option was chosen.

    Z offset

    The base value to be added to the elevation value in the DEM. This could be used to offset elevation values that do not start at sea level.

    Z factor

    The z-factor is a scaling factor used to convert the elevation values for two purposes:

    • To convert the elevation units (such as meters or feet) to the horizontal coordinate units of the dataset, which may be feet, meters, or degrees.
    • To add vertical exaggeration for visual effect.

  8. Under the General section in the Raster Type Properties dialog box, click MOD Parameters.
    1. For Image data path, browse to and select the folder containing the images to be added to the mosaic dataset, and click OK.
    2. For Pixel size (microns), enter the appropriate value in microns, and click OK.

      You can determine pixel size in microns using the following formula:

      25400 / Image Scan Resolution

    3. Click OK to accept your settings and close the Raster Type Properties dialog box.
  9. For Input Data, click the drop-down menu and select Folder.
  10. Browse to and select the folder containing the MOD files, and click OK.
  11. Accept all other defaults and click Run.

    Once completed, the images associated with the MOD files are added to the mosaic dataset and displayed in the Map.

PAR

The PAR raster type is scanned or digital aerial imagery that has been photogrammetrically processed using the legacy Digital Video Plotter (DVP) system and stored as a .PAR metadata file. The .PAR file contains the interior and exterior orientation parameters required to accurately project the associated images on a map.

When using this raster type, you must edit the raster type properties by clicking the Raster Type Properties button Properties and selecting PAR.

You can add PAR data to a mosaic dataset using the PAR raster type.

  1. Create a mosaic dataset. See Create a mosaic dataset for details.
    1. For Coordinate System, click the Select Coordinate System button Select Coordinate System, and select the projected coordinate system that matches the PAR files spatial referencing system.

    The mosaic dataset is created, added to the geodatabase, and loaded as a layer in the Contents pane.

  2. In the Catalog pane, right-click the mosaic dataset and click Add Rasters.

    The Add Rasters to Mosaic Dataset geoprocessing tool opens.

  3. Type the name of your mosaic dataset. Click the Raster Type drop-down list and select PAR.
  4. Click the Raster Type Properties button Properties.

    This opens the Raster Type Properties dialog box. Here you will enter specific information about the path to the images and, optionally, add a DEM.

  5. In the Raster Type Properties dialog box, click the Processing option.
  6. Click the Orthorectification drop-down to choose one of the elevation methods:

    Average Elevation from Image Metadata

    The average elevation is read from the project file.

    Average Elevation from DEM

    The average elevation is read from the DEM provided.

    Constant elevation

    Enter the value of the constant (average) elevation for the area covered by the images.

    DEM

    Choose the DEM from the raster dataset, mosaic dataset, image service, or WCS service you want to use for orthorectification.

    If you need to apply a geoid correction to your elevation data, create a mosaic dataset containing the elevation data and use the Arithmetic function to apply the required equation.

  7. Optionally, you may need to set some elevation adjustment parameters if the DEM option was chosen.

    Z offset

    The base value to be added to the elevation value in the DEM. This could be used to offset elevation values that do not start at sea level.

    Z factor

    The z-factor is a scaling factor used to convert the elevation values for two purposes:

    • To convert the elevation units (such as meters or feet) to the horizontal coordinate units of the dataset, which may be feet, meters, or degrees.
    • To add vertical exaggeration for visual effect.

  8. Under the General section in the Raster Type Properties dialog box, click PAR Parameters.
    1. For Image data path, browse to and select the folder containing the images to be added to the mosaic dataset, and click OK.
    2. Click OK to accept your settings and close the Raster Type Properties dialog box.
  9. In Input Data, click the drop-down menu and select Folder.
  10. Browse to and select the folder containing the MOD files, and click OK.
  11. Accept all other defaults and click Run.

    Once completed, the images associated with the PAR files are added to the mosaic dataset and displayed in the map.

RedEdge

MicaSense RedEdge produces multispectral and high-resolution imagery from a multisensor system. The input files used by this raster type are the .tif files for the bands, one from each sensor including five multispectral bands (blue, green, red, red edge, near-infrared).

When adding RedEdge data to a mosaic dataset, files are filtered to search for the following extensions: *_1.tif, *_2.tif, *_3.tif, *_4.tif, *_5.tif. Additionally, two processing templates are supported: All bands and Multispectral. These templates can process pixels into radiance or surface reflectance using the information from the imagery.

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 adds 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 Frames table schema. To see which fields are recognized for the cameras table, see Cameras table schema.

  1. Create a mosaic dataset.
  2. In the Catalog pane, right-click the mosaic dataset and click Add Rasters.

    The Add Rasters to Mosaic Dataset tool opens.

  3. Click the Raster Type drop-down list and click Scanned Aerial Imagery.
  4. Click the Edit Raster Type Properties button.

    The Raster Type Properties dialog box appears. Here you will enter specific information about the DEM and the camera.

  5. Click the Properties tab.

    This tab allows you to specify the properties that will define the elevation model used in the orthorectification of the imagery.

    Tip:

    Make sure the spatial reference system in the exterior orientation file and the DEM are the same; otherwise, you may have to modify the DEM by either checking the Geoid check box or entering z offset and factor values.

  6. Click the Orthorectification drop-down to choose one of the elevation methods:

    Average Elevation from Image Metadata

    The average elevation is read from the project file.

    Average Elevation from DEM

    The average elevation is read from the DEM provided.

    Constant elevation

    Enter the value of the constant (average) elevation for the area covered by the images.

    DEM

    Choose the DEM from the raster dataset, mosaic dataset, image service, or WCS service you want to use for orthorectification.

    If you need to apply a geoid correction to your elevation data, create a mosaic dataset containing the elevation data and use the Arithmetic function to apply the required equation.

  7. Optionally, you may need to set some elevation adjustment parameters if the DEM option was chosen.

    Z offset

    The base value to be added to the elevation value in the DEM. This could be used to offset elevation values that do not start at sea level.

    Z factor

    The z-factor is a scaling factor used to convert the elevation values for two purposes:

    • To convert the elevation units (such as meters or feet) to the horizontal coordinate units of the dataset, which may be feet, meters, or degrees.
    • To add vertical exaggeration for visual effect.

  8. Click the Frame Camera tab.
  9. Add the cameras table.
  10. Optionally, click the General tab.

    By clicking the Save As button, you can save the changes made to the raster type so it can be reused at another time.

    To use the .art file you save, you can browse to it rather than selecting Scanned Aerial Raster in the Raster Type list.

  11. Click OK to return to the Add Rasters to Mosaic Dataset pane.
  12. For the Input Data parameter, click the browse button and select the frames table.
  13. Optionally, if you won't be recalculating the footprints, you can check Update Overviews.

    You may want to shrink the footprints. If so, don't check Update Overviews; complete running this tool. Use the Build Footprints tool and specify a value for Shrink Distance. Also, change the maximum and minimum data values to the highs and lows of the bit depth, such as 0 and 255 for 8-bit data. Finally, you can build overviews using the Build Overviews tool.

  14. There may be some additional details you need to define within the Advanced Options section, although they are not always necessary.
    1. If the spatial reference for the input data is different from the mosaic dataset, you will need to define one with the Coordinate system for Input Data parameter.
    2. If the data does not have pyramids or statistics, you calculate them by checking Build Raster Pyramids and Calculate Statistics.
  15. Click OK to run the tool and add the data to the mosaic dataset.

Table raster type to support digital cameras

You can use the Table raster type to add any digital standard frame imagery to a mosaic dataset. This approach requires a table containing orientation parameters and other variables. You can also use the Table raster type to migrate a raster catalog to a mosaic dataset.

The following workflow adds UltraCam data into a mosaic dataset.

  1. Create a mosaic dataset.
  2. In the Catalog pane, right-click the mosaic dataset and click Add Rasters.

    The Add Rasters to Mosaic Dataset tool opens.

  3. Click the Raster Type drop-down list and click Table/Raster Catalog.
  4. Click the Edit Raster Type Properties button.
  5. Click the Processing tab.
  6. Click the Processing Template drop-down arrow and click Stretch. The UltraCam data is 16 bit; therefore, you need to define a stretch for the imagery to display properly. Otherwise, it will all appear black.
  7. Click the Input Table Definition tab.

    Here, you will define the field names in your table that match the fields this Table raster type requires.

  8. For the Raster Source field, type Rastersrc.
  9. For the Name field, type Frame.
  10. Click OK to return to the Add Rasters to Mosaic Dataset pane.
  11. For the Input Data parameter, click the browse button and select the .dbf table.
  12. Click OK to run the tool and add the data to the mosaic dataset.

UAV/UAS

The 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 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 dialog box as follows:

  • 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 list.

Vexcel Osprey

The Vexcel Osprey raster type is based on the Vexcel Osprey aerial sensor system, and is designed to be added to a mosaic dataset. It takes as an input the exterior orientation (*.eo, *.txt, and *.csv ) file, and the image path. Use the following as a guide to add Vexcel Osprey data to a mosaic dataset:

  1. Create the mosaic dataset.
    1. In the Catalog pane, locate the geodatabase where you want to save the mosaic dataset. If required, create a new file geodatabase; right-click the Databases folder and select New > File Geodatabase. Name the geodatabase appropriately, and press Enter on your keyboard.
    2. Right-click the geodatabase and select Create Mosaic Dataset.

      The Create Mosaic Dataset tool opens. The output location will be the geodatabase you selected.

    3. Name the mosaic dataset and select a coordinate system that matches the projection center coordinates of the images listed in the exterior orientation file. Optionally, from the Coordinate System window, click the Layers drop-down menu, and you will have the option of matching the coordinate system to any of the layers already in the Contents pane.

    Your empty mosaic dataset will be created once you run the tool. Next, you will need to add the Vexcel Osprey imagery to the mosaic dataset.

  2. In the Catalog pane, right-click the mosaic dataset and click Add Rasters.

    The Add Rasters To Mosaic Dataset geoprocessing tool opens.

  3. Type the name of your mosaic dataset. Select a coordinate system that matches the projection center coordinates of the images listed in the exterior orientation file.

    Optionally, from the Coordinate System window, click the Layers drop-down menu, and you will have the option of matching the coordinate system to any of the layers already in the Contents pane.

  4. Click Run.

    Your empty mosaic dataset is created.

  5. Under the General section on the Raster Type Properties dialog box, click Processing.
  6. Click the Orthorectification drop-down list to choose one of the elevation source options:
    • Average Elevation from Image Metadata—The average elevation is read from the project file.
    • Average Elevation from DEM—The average elevation is read from the DEM provided.
    • Constant elevation—Enter the value of the constant (average) elevation for the area covered by the images.
    • DEM—Choose a DEM from a raster dataset, mosaic dataset, image service, or WCS service to be used for orthorectification.
      Note:

      If you need to apply a geoid correction to your elevation data, create a mosaic dataset containing the elevation data, and use the Arithmetic function to apply the required equation.

    Optionally, you may need to set some elevation adjustment parameters if the DEM option was chosen.

    • Z offset—The base value to be added to the elevation value in the DEM. This could be used to offset elevation values that do not start at sea level.
    • Z factor—The z-factor is a scaling factor used to convert the elevation values for two purposes listed below:
      • Convert the elevation units (such as meters or feet) to the horizontal coordinate units of the dataset, which may be feet, meters, or degrees.
      • Add vertical exaggeration for visual effect.
  7. Under the General section on the Raster Type Properties dialog box, click Vexcel Osprey Parameters.
    1. For Image data path, browse to and select the folder containing the images to be added to the mosaic dataset, and click OK.
    2. For Input image extension, enter an appropriate extension.
    3. Click OK to accept your settings.

      The Raster Type Properties dialog box closes.

  8. On the Add Rasters To Mosaic Dataset geoprocessing tool, for Input Data, ensure File is selected.
  9. Browse to the folder containing the *.eo file, and click OK.
  10. Accept all other defaults, and click Run.

    Next, you will add the Vexcel Osprey imagery to the mosaic dataset.

  11. In the Catalog pane, right-click the mosaic dataset and click Add Rasters.

    The Add Rasters To Mosaic Dataset geoprocessing tool opens.

  12. Type the name of your mosaic dataset. Click the Raster Type drop-down list and select Vexcel Osprey.
  13. Click the Raster Type Properties button Properties.

    The Raster Type Properties dialog box appears. Here, you will enter specific information about the path to the images, format, and optionally add a DEM.

  14. Under the General section on the Raster Type Properties dialog box, click Processing.
  15. Click the Orthorectification drop-down list to choose one of the elevation source options:
    • Average Elevation from Image Metadata—The average elevation is read from the project file.
    • Average Elevation from DEM—The average elevation is read from the DEM provided.
    • Constant elevation—Enter the value of the constant (average) elevation for the area covered by the images.
    • DEM—Choose a DEM from a raster dataset, mosaic dataset, image service, or WCS service to be used for orthorectification.
      Note:

      If you need to apply a geoid correction to your elevation data, create a mosaic dataset containing the elevation data, and use the Arithmetic function to apply the required equation.

    Optionally, you may need to set some elevation adjustment parameters if the DEM option was chosen.

    • Z offset—The base value to be added to the elevation value in the DEM. This could be used to offset elevation values that do not start at sea level.
    • Z factor—The z-factor is a scaling factor used to convert the elevation values for two purposes listed below:
      • Convert the elevation units (such as meters or feet) to the horizontal coordinate units of the dataset, which may be feet, meters, or degrees.
      • Add vertical exaggeration for visual effect.
  16. Under the General section on the Raster Type Properties dialog box, click Vexcel Osprey Parameters.
    1. For Image data path, browse to and select the folder containing the images to be added to the mosaic dataset, and click OK.
    2. For Image Type, click the appropriate option next to the option indicating the orientation of the images to be processed.
      • Nadir images only—The optical axis of the images to be processed are perpendicular to the ground.
      • Nadir and Oblique images—The optical axis of the images to be processed includes some that are perpendicular to the ground (nadir images) and some that are not (oblique images).
    3. Click OK to accept your settings.

      The Raster Type Properties dialog box closes.

  17. In the Add Rasters To Mosaic Dataset geoprocessing tool, for Input Data, ensure File is selected.
  18. Browse to the folder containing the exterior orientation file in formats such as *.eo, *.txt, or *.csv, select it, and click OK.
  19. Accept all other defaults, and click Run.

    The associated images are added to the mosaic dataset and displayed in the 2D map window.

Workflow using the Ortho Mapping or Reality Mapping Workspace Wizard

The Ortho mapping and Reality mapping workspace wizards guide you through the steps of creating a workspace and populating it with a Vexcel Osprey image collection.

  1. On the ArcGIS ArcGIS AllSource main menu, select the Imagery tab, and click New Workspace.
  2. On the Workspace Configuration page, type a name for the workspace.
  3. Ensure that Workspace Type is set appropriately.
    Note:

    With an Advanced license, only an Ortho Mapping workspace option is available. With a Standard or Advanced license, and a Reality for ArcGIS Pro extension license, both an Ortho Mapping and Reality Mapping workspace option are available.

  4. From the Sensor Data Type drop-down list, select Aerial - Digital.

    The Scenario Type and overlap information is automatically updated by the system.

  5. Select the appropriate Scenario Type (oblique or nadir), based on the images being processed, and the products to be generated.
  6. Optionally, check the Allow adjustment reset check box to allow you to revert your workspace to a previous state.
  7. Accept all the other default values, and click Next.
  8. On the Image Collection page, select Vexcel Osprey for Sensor Type.
  9. For project file or folder, click the Browse button Folder in the Input Data window, change the file filter to Vexcel Osprey File, select the exterior orientation file, and click OK.
  10. For Image Data Path, click the Browse button Folder, select the folder containing the images, and click OK.
  11. Set the Workspace Spatial Reference by clicking the Spatial Reference button spatial reference and set the spatial reference to the same coordinate system as that of the coordinates in the exterior orientation file, and click Next.
  12. On the Data Loader Options page, choose an Elevation Source value. If using the Average Elevation from DEM option, it is recommended that you use a local DEM to enhance data loading performance.
    Data Loader Options
  13. Accept all other defaults, and click Finish to create the workspace.

The workspace is created, and the image collection is loaded in the workspace and displayed on the map.

You can now perform adjustments and generate derived products.

Feedback on this topic?

In this topic
  1. ADS
  2. Altum
  3. Use Applanix imagery
  4. AVIRIS
  5. ESRI Frame XML
  6. Frame Camera
  7. Generic RPC
  8. GORI
  9. ISAT imagery
  10. Match-AT imagery
  11. MOD
  12. PAR
  13. RedEdge
  14. Scanned Aerial Imagery
  15. Table raster type to support digital cameras
  16. UAV/UAS
  17. Vexcel Osprey