GCPIMPORT

Description

GCPIMPORT imports ground control points from a GCP segment into a CATALYST Professional OrthoEngine project file.

Parameters

Name	Type	Length	Value range
InputText: Input OrthoEngine project file *	Text port	1 -
InputGCP: Input Ground Control Points segment or layer	GCP port	0 - 1
Image ID	String	0 -
OutputText	String	0 -

* Required parameter

Parameter descriptions

InputText: Input OrthoEngine project file

Specifies the path and file name of the input OrthoEngine project file into which GCPs will be added.

InputGCP: Input Ground Control Points segment or layer

Specifies the input GCP segment to import into the input OrthoEngine project along with the image layers.

If DBGC is left blank then the last GCP segment is read from the image file.

Specifies the name of the PCIDSK file which contains the GCP layer to use for the Image ID parameter.

Image ID

Specifies the image identification name in the input project file into which the GCPs are imported.

The image identification name is typically the image base name when an OrthoEngine project is created. For example, when you add an image from "C:\pci\Demo\S129.pix" to a project, the image identification is set to "S129". However, if you set this parameter with a file name extension and its full path, the base name is automatically extracted; therefore, "C:\pci\Demo\S129.pix" and "S129" are both accepted.

The following formats are acceptable:

• S129
• S129.pix
• C:\Projects\Demo Data\S129.pix

If a directory or file name pattern is specified for MFILE, this parameter can be empty; the file names are extracted and then used as the Image IDs.

If a text file is specified for MFILE, the image IDs are read from the text file; or the file names are extracted and then used as the Image IDs.

OutputText

Specifies the path and file name of the output OrthoEngine project file that contains the imported GCPs. If not specified, this parameter uses OEPROJI (InputText) by default.

If specified the output OrthoEngine project file must not exist.

Details

GCPIMPORT imports ground control points (GCP) to an OrthoEngine project file (.prj). Each GCP in a project has a unique identifier referred to as a GCP ID. If the ID of the incoming point exists already in the project, and its geocoded x and y position is the same as an existing GCP, it will be imported and read as a stereo GCP. If the geocoding position differs, the point will still be imported, but the ID will be made unique by appending a sequential number, for example, G001_1.

The GCP segment's elevation datum must match the input OrthoEngine project's elevation datum, except if there are no GCPs in the project, in which case the project's elevation datum is set to the same as the GCP segment's.

Any GCP segment that cannot be imported is skipped and the reason is written to the report.

This function is equivalent to manually collecting GCPs for the working image in OrthoEngine, where you import GCPs from a text file, browse to a PCIDSK file, and select a GCP segment.