This guide lists the airborne and satellite-borne optical and radar sensors supported in ERDAS IMAGINE, as well as transform models.

Use these tables to select the correct options in the Set Geometric Model dialog.

To georeference data, you may select a 2D transform model to warp the input image to your reference data.

To orthorectify data, a general 3D transform model or appropriate sensor model should be selected to allow for the specification of an elevation file or constant elevation value.

Descriptions of the sensor systems are located in Optical Satellite Data, Radar Satellite Data, and Image Data from Aircraft in the Producer Field Guide.

To learn how to rectify imagery see Rectifying an Image and Orthorectify without GCPs.

Vertical Datum Alignment

Most 3D Transform models automatically adjust in real-time any vertical datum mismatch between the DEM and the respective model, beginning with ERDAS IMAGINE 2010.

A few models require vertical datum alignment as described in Vertical Datum Alignment.

SAR Data

If your data was collected from a Synthetic Aperture Radar (SAR) satellite system, see Synthetic Aperture Radar (SAR) Data table (below).

2D Transform Models

Model Name | ERDAS IMAGINE Listing | Comments |

Affine Transformation | Affine | To perform an affine transform using GCPs, use a 1st order Polynomial transform. Affine is the same transformation as a 1st order Polynomial transform. |

Polynomial | ||

Rubber Sheeting | ||

Projective Transform | The Projective Transform model has a 2D or 3D transform option. | |

Reproject | Reproject Model is used to convert an image from one projected coordinate system to another. See Reprojection Model Properties. |

3D Transform Models

Model Name or | ERDAS IMAGINE Listing | Supported Metadata | Comments |

ALOS PRISM | ALOS PRISM - Orbital Pushbroom | *VOL*, *LED*, *TRL*, & *SUP* | |

ALOS RPC | ALOS RPC | *RPC* | Requires RPC (rational polynomial coefficients) |

ASTER | ASTER - Orbital Pushbroom | Image header | |

CARTOSAT RPC | CARTOSAT RPC | *RPC.TXT, *MET.TXT | Requires RPC (rational polynomial coefficients) |

DEIMOS-1 | DEIMOS RPC | *.rpc | Requires RPC (rational polynomial coefficients) |

Direct Linear Transform (DLT) | Direct Linear Transform (DLT) | Appropriate for use with single perspective imagery such as aerial photography. | |

DPPDB | DPPDB | *.NTF | |

EROS A | EROS - Orbital Pushbroom | *.pass and/or *.tqr | |

EROS B | EROS - Orbital Pushbroom | *.pass and/or *.tqr | |

FORMOSAT2 | FORMOSAT2- Orbital Pushbroom | METADATA.DIM | |

Frame Camera | Camera | ASCII | scanned aerial frame |

GeoEye-1 | GeoEye/OrbView - Orbital Pushbroom | For NCDRD: *.ntf For others: *.pvl *.eph & *.att or *.imd, *.geo, *.eph & *.att | |

GeoEye-1 RPC | GeoEye RPC | *.pvl, *rpc.txt, or *.ntf | Requires RPC (rational polynomial coefficients) |

GOKTURK/RASAT RPC | GOKTURK/RASAT RPC | *RPC.TXT | Requires RPC (rational polynomial coefficients) |

IKONOS RPC | IKONOS | *.ntf, *rpc.txt *rpc_org.txt, metadata.txt | Requires RPC (rational polynomial coefficients) |

IRS-1C Pushbroom | IRS | Image header | |

IRS-1D (PAN and LISS sensors) | IRS | Image header | |

KOMPSAT RPC | KOMPSAT RPC | *.rpc | Requires RPC (rational polynomial coefficients) |

Landsat ETM+ | Landsat | Image header | Polynomial-based pushbroom model |

Landsat MSS | Landsat | Image header | Polynomial-based pushbroom model |

Landsat TM | Landsat | Image header | Polynomial-based pushbroom model |

NITF RPC | NITF RPC | *.NTF | Requires RPC (rational polynomial coefficients) |

Orbital Pushbroom | Orbital Pushbroom | ||

Orbview-3 | GeoEye/OrbView - Orbital Pushbroom | *.pvl | |

Orbview-3 RPC | ORBIMAGE RPC | *.pvl, *rpc.txt, or *.NTF | Requires RPC (rational polynomial coefficients) |

Pleiades | Pleiades | *.xml | Requires RPC (rational polynomial coefficients) |

Pleiades RPC | Pleiades RPC | *.xml | Requires RPC (rational polynomial coefficients) |

Projective Transform | Projective Transform | The Projective Transform model has a 2D or 3D transform option. | |

QuickBird | QuickBird/WorldView - Orbital Pushbroom | For NCDRD: *.NTF For others: *.ATT, *.EPH, *.GEO, *.IMD, & *.XML | |

QuickBird RPC | QuickBird RPC | *.NTF or *.RPB | Requires RPC (rational polynomial coefficients) |

RapidEye RPC | RapidEye RPC | *.NTF or *_RPC.XML | Requires RPC (rational polynomial coefficients) |

RESOURCESAT-1 RPC | RESOURCESAT RPC | *RPC.TXT | Requires RPC (rational polynomial coefficients) |

SkySat RPC | SkySat RPC | *_RPC.TXT | Requires RPC (rational polynomial coefficients) |

SPOT-1, 2, 3, 4, Level 1A or 1B | Spot | Image header | Polynomial-based pushbroom model |

SPOT 5 | Spot5 - Orbital Pushbroom | METADATA.DIM | |

SPOT 6 | Spot6 - Orbital Pushbroom | *.xml | |

THEOS1 | THEOS1 - Orbital Pushbroom | METADATA.DIM | |

VisionMap Sensor Model | Support | *.DAT, *.SUP, *.TIF, *.XML | Requires Community Sensor Model (CSM) configuration |

WorldView-1 WorldView-2 | QuickBird/WorldView - Orbital Pushbroom | For NCDRD: *.NTF For others: *.ATT, *.EPH, *.GEO, *.IMD, & *.XML | |

WorldView-1 RPC WorldView-2 RPC | WorldView RPC | *.NTF or *.RPB | Requires RPC (rational polynomial coefficients) |

SPOT 5 DIM format data older than 2002 is not supported.

GeoEye-1 NITF NCDRD Format

GeoEye-1 -- When using the NITF NCDRD format for Orbital Pushbroom and the .PVL, .EPH, and .ATT files are present in the same directory as the NITF file, the sensor model metadata is read from these files in both IMAGINE Photogrammetry and ERDAS IMAGINE.

GeoEye-1 -- When using the NITF NCDRD format in the Multipoint Geometric Correction workspace, if only the .NTF file is present, an error is shown saying that metadata display is not supported. This error can be ignored; the model has been correctly initialized internally. To view the metadata, use Image Metadata or the NITF Metadata Viewer.

VisionMap Sensor Model

The VisionMap sensor model is implemented as a Community Sensor Model (CSM) plugin, and it must be configured before first use. You can configure the VisionMap sensor model using the ERDAS CSM Plugin Configuration Manager. The library (DLL) for the VisionMap sensor can be found in the following location:

<IMAGINE_HOME>\usr\lib\Win32Release\communitysensormodels

Select Visual Studio 2010 from the Runtime library list when configuring a library because it might not behave properly if configured with other options.

Synthetic Aperture Radar (SAR) Data

Synthetic Aperture Radar (SAR) data from these satellite sensors can be processed using such tools as change detection, orthorectification, interferometry, filtering, and calibration available in Radar modules.

For most of these sensors, a direct read capability (raster DLL) allows visualization and analysis of imagery without importing.

For sensors without a dedicated importer or direct read DLL, use the SAR Metadata Editor to create and attach the metadata files needed to support Radar processing and information extraction.

Satellite Sensor Name | ERDAS IMAGINE Listing | Supported Metadata |

Alaska SAR Facility | SAR (Synthetic Aperture Radar) | *.L |

ALOS PALSAR | SAR (Synthetic Aperture Radar) | PASL *.lea, PASL *.SLC, LED* |

COSMO-SkyMed | SAR (Synthetic Aperture Radar) | CSKS*.h5 |

Envisat | SAR (Synthetic Aperture Radar) | *.N1* |

ERS-1 | SAR (Synthetic Aperture Radar) | LEA_01.001 |

ERS-2 | SAR (Synthetic Aperture Radar) | LEA_01.001 |

KOMPSAT5 | SAR (Synthetic Aperture Radar) | CSKS*.h5 |

RADARSAT-1 | SAR (Synthetic Aperture Radar) | LEA_01.001 |

RADARSAT-2 | SAR (Synthetic Aperture Radar) | product.xml |

RISAT | SAR (Synthetic Aperture Radar) | CSKS*.h5 |

TanDEM-X | SAR (Synthetic Aperture Radar) | tdx1*.xml |

TerraSAR-X | SAR (Synthetic Aperture Radar) | tsx1*.xml |

See Radar Interferometry User Guide and Operational Radar User Guide for workflows on processing radar data using Radar modules.