OEMDLEXPORT

Description

If necessary OEMDLEXPORT computes the block adjustment for a CATALYST Professional OrthoEngine project file you specify. It reads the math-model computation appropriate to the model in the project file, and then exports it to new linked PIX files in the output folder you specify.

Parameters

Name	Type	Caption	Length	Value range
OEPROJI *	String	Input OrthoEngine project file	1 - 192
TFILE	String	Output text file name	0 - 192
OUTDIR *	String	Output folder	1 - 192
OEPROJO	String	Output OrthoEngine project file	0 - 192
MFILE	String	Input file name, directory, or a text file	0 - 192
ADJORDER	Integer	RPC adjustment order (0, 1, 2)	0 - 1	0 - 2
REPORT	String	Report mode	0 - 192	Quick links

* Required parameter

Parameter descriptions

OEPROJI

The name of the OrthoEngine project file from which to compute the block adjustment. Images in the file must have math-model information. The computed model will be a block adjustment of all images in the project file.

The updated math model is saved automatically to a math-model segment of each image in the project. If the image files are not in PCIDSK format, a linked PCIDSK file with the same base file name is created in the specified output folder to store the math-model segment. You can use this linked PCIDSK file as input data for other functions.

Only active photos are used during the bundle adjustment (calculation of the math models) and exported.

TFILE

The name of the output text file. If specified, the file name of the the exported PIX files are written with the following information and format:

            ['PATH\FILE.PIX'];[DBIC];[MMSEG]

The format of the information in the text file is delimited by semicolons and is in the same order as that of the MFILE parameter specifications (to view the specifications, follow the link to ORTHO under Related functions at the end of this topic). Therefore, you can specify the value of the TFILE parameter as input for the MFILE parameter in ORTHO; however, do not specify a value for the DBIC parameter; this is required to reset all of the channels during processing.

An example of the format of the information written to the output file is:

            'S129.pix'; ; 4
            'S130.pix'; ; 4

If no path is specified in the project file, the working folder is used as the path information in the text-file output. If the text file already exists, it is appended with the new entries.

Photos that fail to be exported are not added to the TFILE.

This parameter is optional.

OUTDIR

The path of a folder to which to write the output files with math-model segments. If the folder does not exist, or if the path specifies a file or an empty string, processing stops, and an error message is displayed.

If there is an existing output file in the folder, it is overwritten with the new information.

OEPROJO

The name of the output OrthoEngine project file to create that references the export linked PIX files.

If the output OrthoEngine project file exists, it is overwritten.

If this parameter is left blank then an output OrthoEngine project file is not created.

Inactive photos are kept and written to the output OrthoEngine project file.

Photos that fail to be exported are not written to the output OrthoEngine project file.

The output OrthoEngine project file is essentially a copy of the input OrthoEngine project file except that the OrthoEngine photos point to the output linked PIX files created instead of the original files.

This parameter is optional.

MFILE

Specifies the name of a folder, image file(s), or a text file containing the list of images to be exported from the input OrthoEngine project file. If an image is inactive, but is listed in the MFILE then the image is exported, meaning that the MFILE images ignore the active/inactive state of the image. By default, this parameter is optional. If not specified then all the images listed in an OrthoEngine project file will be exported.

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 directory path name; for example, "c:\data"
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, for example, "c:\list.txt"

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.

ADJORDER

If RPC data is supplied with the data, this value specifies the RPC adjustment order to be used in the RPC model refinement. Valid values are 0, 1 or 2.

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

If an image in your input OrthoEngine project file is out of date, OEMDLEXPORT recalculates a block-bundle-adjusted math model. Otherwise, if all of the images in your project file are up to date, then the math model is used as is. Having images as up to date as possible minimizes having to recalculate the math model, which can be time-consuming.

Recalculating a block-bundle math model consists of using the collective information (GCPs, TPs, RPCs, exterior orientation, orbit information, and so on) in the OrthoEngine project file you specify. How the math model is calculated is based on the math model specified in the project file.

After the math model is resolved OEMDLEXPORT exports the up-to-date model to a binary math-model segment for each image in the OrthoEngine project file. The binary math-model segment is stored in linked PCIDSK files, which correspond to each image in the project. You can use the segment to orthorectify the images.

Note: If the specified OrthoEngine project includes any inactive images, they are excluded from processing.

Example

Export the math model of an OrthoEngine project file named airphoto_model.prj.

        EASI>OEPROJ="airphoto_model.prj"
        EASI>TFILE="out.txt"
        EASI>OUTDIR="output"

        EASI>r oemdlexport

OEMDLEXPORT computes the model that will be a block adjustment of all images in the project file. The updated math models are saved automatically in the math-model segment of each image in the project. The images processed and the corresponding number of the math-model segment are written to an output text file out.txt.

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