CRPROJ

Description

CRPROJ creates a CATALYST Professional OrthoEngine project file based on a list of input images and optional ground control point (GCP) segments.

Parameters

crproj(mfile, dbgc, oeproj, modeltyp, mapunits)

Name	Type	Caption	Length	Value range
MFILE *	str	Input file name, folder, or text file	1 -
DBGC	List[int]	Input ground control points segment	0 - 1	-1 - 4096
OEPROJ *	str	Output OrthoEngine project file name	1 -
MODELTYP *	str	Math model type	2 - 4
MAPUNITS	str	Projection map units	0 -

* Required parameter

Parameter descriptions

MFILE

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

MFILE can be set using any of the following options:

a specific data file name or folder 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 per file; 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 semicolons to delimit the parameters.
Leave the position between the semicolons 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 input GCP segment to add to the new OrthoEngine project along with the image layers.

If a folder is specified for MFILE, this segment number is applied to all images. If a text file is specified for MFILE, DBGC is read from the text file and this parameter can be left empty.

If this parameter is defined, but there exist no segment in an image an error message will be displayed.

If this parameter is set to empty, no GCPs will be imported.

If this parameter is set to -1 and not defined in the text file, then the last GCP segment, if exists, in a file will be imported.

OEPROJ

Specifies the file name for the new OrthoEngine project. The project file will have a .prj file name extension.

MODELTYP

Specifies the math modeling type for the OrthoEngine project.

Supported models are:

ADS: Airborne Digital Sensor
APSC: Aerial Photography (Scanned) Exterior Orientation is calculated from GCPs and tie points (TP) in input image
APSU: Aerial Photography (Scanned) Exterior Orientation is input by user; no GCPs or TPs are required to proceed directly to orthorectification
APDC: Aerial Photography (Digital) Exterior Orientation is calculated from GCPs and TPs in input image
APDU: Aerial Photography (Digital) Exterior Orientation is input by user; no GCPs or TPs are required to proceed directly to orthorectification
SAT: Toutin's Satellite Orbital Model
RFIA: Rational Functions model. Model is extracted from input image using preferred order for the given sensor
RFI0: Rational Functions model. Model is extracted from input image using 0 order RPC adjustment
RFI1: Rational Functions model. Model is extracted from input image using 1st order RPC adjustment
RFI2: Rational Functions model. Model is extracted from input image using 2nd order RPC adjustment
RFG: Rational Functions model. Model is calculated from GCPs in input image
RS: ASAR/RADARSAT-specific model
AV: Low-resolution AVHRR model
POLY: Polynomial model
TPS: Thin Plate Spline model
SPB: Spacecraft pushbroom model
SRS: Spacecraft rolling-shutter model

Note: Although CRPROJ still supports the generic models APS (equivalent to APSC) and APD (equivalent to APDC), it is recommended that you use the more precise models (APDC or APDU for digital camera; APSC or APSU for standard camera).

MAPUNITS

Specifies the projection string for the output model parameters and image products, such as ortho images.

If this parameter is not specified, the projection of the first image added to the project will be used.

Supported values are:

UTM mm r Ennn: UTM Easting and Northing coordinates
LONG/LAT Ennn: Longitude and Latitude coordinates
METER: Units in meters
FOOT: Units in feet
SPCS: State Place Coordinate System

For more information, see TIFF (TIF).

Return Value

Returns: execution status

Type: PCI_INT

The return value is 0. This function returns only if it executes successfully; otherwise, it throws an exception.

Details

CRPROJ creates an OrthoEngine ASCII project file from a list of input images, and optional GCP segments and auxiliary information. You can then use the project file as input for tasks, such as AUTOTIE, and math-modeling tasks, such as SATMODEL, for a block bundle adjustment of a group of images. By creating a project file, you can also open the project in OrthoEngine to manually edit GCPs and TPs.

The input images that have GCPs and one or more GCPs are imported, then those images' status is set to stale. That means that the math model needs to recomputed before orthos can be created.

You can combine CRPROJ with algorithms, such as CPMMSEG (to copy math-model segments based on the model in a project file), MERGPROJ (to combine multiple projects in a single project), and SUBPROJ (to divide a project file into smaller project files).

If the input images are digital air photos and contain Exif tags (.jpg, .tif), CRPROJ imports these tags as metadata. Therefore, when you run CAMIMPORT, the exterior orientation (EO) is computed automatically. The following Exif tags are required for automatic EO computation:

Make
NominalLocation_Longitude
NominalLocation_Latitude
NominalLocation_Height
Acquisition_DateTime

Example

Create an OrthoEngine project file using Toutin's satellite orbital model.

from pci.crproj import crproj

mfile = "spotleft.pix"   # input file name
dbgc = []    # input GCP segment
oeproj = "spotleft.prj"    # output OrthoEngine project file
modeltyp = "SAT" # use Toutin's satellite orbital model
mapunits = "UTM 11 D000" # output map unit.

crproj (mfile, dbgc, oeproj, modeltyp, mapunits)

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