SATMODEL

Description

SATMODEL computes the math model of one or more satellite images using Toutin's model and stores the result in a segment in the image file.

Parameters

Name	Type	Caption	Length	Value range
MFILE*	String	Input file name, directory, or text file	1 - 192
DBGC	Integer	Input GCP segment	0 - 1
ORBIT	Integer	Input orbit segment	0 - 1
MMSEG	Integer	Math model segment or layer	0 - 1
MAPUNITS	String	Map units	0 - 16	PIXEL, UTM, LONG/LAT, and others
REPORT	String	Report mode	0 - 192	Quick links

* Required parameter

Parameter descriptions

MFILE

Specifies the name of a folder, image file, or text file that contains the input raw images to be processed. Wildcards (*) can be used.

MFILE can be set using any of the following options:

a specific data file name or directory path and file name; for example, "irvine.pix" or "c:\data\irvine.pix"
a specific file name pattern or all of the files in a folder; for example, "c:\data\*.pix" or "c:\data"
an existing text file that contains references to multiple files with, optionally, different parameter settings on a per file basis; for example, "c:\list.txt"

If a directory name is specified or if multiple file names are entered, all images in MFILE should be processed using the parameters set for SATMODEL.

If a directory is specified, then the DBGC, MMSEG, and ORBIT parameters are set to a single value for all input images. If a text file is specified, the files listed in the text file are processed with the listed parameters. In this case, the DBGC, MMSEG, and ORBIT parameters are read from the text file for each image, and those parameters can be left blank.

If one file is specified for MFILE, then the model computed will be an independent model (one image).

If the text file option is used, the following general rules apply:

Specify a .txt extension for the file containing multiple files and different parameter values.
List each set of parameters on its own line in the given order.
Specify string parameters within quotation marks.
Do not specify numeric parameters within quotation marks.
A quotation mark preceded by a backslash is used as part of the string. For example, 'ab\"c' is used as: ab"c.
Use an exclamation mark (!) before writing a comment in the text file.
Use semi-colons to delimit the parameters.
Leave the position between the semi-colons empty (";;") if you do not want to specify a value. Alternatively, if there are no remaining parameters to be specified on the end of a line, you may leave it blank.
Parameters in a text file may or may not be specified in the function:
- If a parameter is specified in the function and in the text file, the value provided in the text file is used.
- If a parameter is not specified in the text file, the parameter can be set in the function.

DBGC

Specifies the ground control point (GCP) segment or layer in the input raw image to use to compute the model.

If a directory is specified for MFILE, this segment number will be applied to all images. If a text file is specified, DBGC is read from the text file, and this parameter can be left blank. If no value is specified, the default four-corner coordinates in the orbit segment will be used as GCPs to compute an approximate model for non-RADARSAT-2 images. For RADARSAT-2 images, the orbit and RFModel segments associated with the data will be used to compute Toutin's hybrid model.

ORBIT

Specifies the orbit segment or layer in the input image to use to compute the model.

If a directory is specified for MFILE, this segment number will be applied to all images. If a text file is specified, ORBIT is read from the text file, and this parameter can be left blank. If no value is specified, the last orbit segment will be used automatically.

MMSEG

Specifies the math model segment or layer to store the model.

If a directory is specified for MFILE, this segment number will be applied to all images. If a text file is specified, MMSEG is read from the text file, and this parameter can be left blank. If no value is specified, a new segment is created.

MAPUNITS

Specifies the projection string for the output model.

The standard definitions are as follows:

PIXEL: pixel and line
UTM: Universal Transverse Mercator
SPCS: State Plane Coordinate System
LONG/LAT: longitude and latitude
METER: image along-row and along-column meters
FOOT: image along-row and along-column feet

For a complete list of supported projections and Earth models, see Understanding map projections. The format of the map units string is described in Output units.

If this parameter is not specified, the map units of the specified GCP segment are used. If no GCP segment is specified, the UTM unit stored in the orbit segment is used.

REPORT

Specifies where to direct the generated report.

Available options are:

TERM: generates a report on the terminal (default)
DISK: generates a report on file "IMPRPT.LST"
OFF: turns off report generation
<filename>: appends a report to the specified file

Details

SATMODEL computes the math model of one or more satellite images using Toutin's model. This includes bundle adjustment of multiple scenes, using ground control points (GCPs) or tie points, or both.

The input is either:

A single image with orbit segment and possibly a GCP segment.
An OrthoEngine project file that contains images with orbit information and GCPs or tie points, or both.

The output is a refined math model for each image, saved either to a math model segment in the image file or to the OrthoEngine project file, depending on the input.

If MFILE is a text file, the files and parameters listed in the text file are used. For SATMODEL, the parameters in the text file must be delimited by semi-colons and must appear in the following order, where DBGC, ORBIT, and MMSEG are optional:

[FILE][DBGC][ORBIT][MMSEG]

If the DBGC (InputGCP) parameter is not specified, SATMODEL uses the four corner points and scene center point stored in the ORBIT (InputORB) segment as GCPs; however, these points are not available for every format.

If DBGC (InputGCP) is not specified and these points are not available, SATMODEL exits with an error. The corners points are only an estimate and are not accurate. Use them only when accurate GCPs cannot be obtained.

Example

Generate a satellite model for a SPOT image.

EASI>MFILE="17029_pan.pix"
EASI>DBGC=3
EASI>ORBIT=2
EASI>MMSEG=
EASI>MAPUNITS=
EASI>REPORT="TERM"
EASI>r SATMODEL

Environments	PYTHON :: EASI :: MODELER
Quick links	Description :: Parameters :: Parameter descriptions :: Details :: Example :: Related