ERDAS Desktop Products

Installation and Configuration

Guide

November 2012
Copyright © 2012 Intergraph Corporation. All rights reserved.

Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement;
contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret
law, and international treaty, and may not be provided or otherwise made available without proper authorization from Intergraph
Corporation.

U.S. Government Restricted Rights Legend

Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was
developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with
subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal
Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of
the United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS
252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.

Unpublished - rights reserved under the copyright laws of the United States.

Intergraph Corporation - P.O. Box 240000 - Huntsville, AL 35813

Terms of Use

Use of this software product is subject to the End User License Agreement ("EULA") delivered with this software product unless
the licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed
license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use
of this software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives
licensee permission to print a reasonable number of copies of the documentation as defined in the applicable license agreement
and delivered with the software product for licensee's internal, non-commercial use. The documentation may not be printed for
resale or redistribution.

Warranties and Liabilities

All warranties given by Intergraph Corporation about equipment or software are set forth in the EULA provided with the software
or applicable license for the software product signed by Intergraph Corporation, and nothing stated in, or implied by, this document
or its contents shall be considered or deemed a modification or amendment of such warranties. Intergraph believes the
information in this publication is accurate as of its publication date.

The information and the software discussed in this document are subject to change without notice and are subject to applicable
technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.

The software discussed in this document is furnished under a license and may be used or copied only in accordance with the
terms of this license. No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not
supplied by Intergraph or its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL
EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.

Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data.
Users should verify for themselves that the data is accurate and suitable for their project work.

Trademarks

Intergraph, the Intergraph logo, and GeoMedia are registered trademarks of Intergraph Corporation. Microsoft and Windows are
registered trademarks of Microsoft Corporation. Bing is a trademark of Microsoft Corporation. Google Maps is a trademark of
Google Incorporated. Pictometry Intelligent Images is a registered trademark of Pictometry International Corporation. ERDAS,
ERDAS IMAGINE, Stereo Analyst, IMAGINE Essentials, IMAGINE Advantage, IMAGINE, Professional, IMAGINE VirtualGIS,
Mapcomposer, Viewfinder, Imagizer, LPS, and ERDAS APOLLO are registered trademarks and exclusive property of Intergraph
Corporation.

Other brands and product names are trademarks of their respective owners.

Government Reserved Rights. MrSID technology incorporated in the Software was developed in part through a project at the Los
Alamos National Laboratory, funded by the U.S. Government, managed under contract by the University of California (University),
and is under exclusive commercial license to LizardTech, Inc. It is used under license from LizardTech. MrSID is protected by U.S.
Patent No. 5,710,835. Foreign patents pending. The U.S. Government and the University have reserved rights in MrSID
technology, including without limitation: (a) The U.S. Government has a non-exclusive, nontransferable, irrevocable, paid-up
license to practice or have practiced throughout the world, for or on behalf of the United States, inventions covered by U.S. Patent
No. 5,710,835 and has other rights under 35 U.S.C. § 200-212 and applicable implementing regulations; (b) If LizardTech's rights
in the MrSID Technology terminate during the term of this Agreement, you may continue to use the Software. Any provisions of
this license which could reasonably be deemed to do so would then protect the University and/or the U.S. Government; and (c)
The University has no obligation to furnish any know-how, technical assistance, or technical data to users of MrSID software and
makes no warranty or representation as to the validity of U.S. Patent 5,710,835 nor that the MrSID Software will not infringe any
patent or other proprietary right. For further information about these provisions, contact LizardTech, 1008 Western Ave., Suite
200, Seattle, WA 98104.
 Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Preparation for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
ERDAS Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Two-stage Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
ERDAS IMAGINE and GeoMedia 6.x Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Temporary File Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Administrator Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Add-on Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Local Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Existing Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Installing the ERDAS Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Prerequisite to Installing ERDAS Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
ERDAS Products that Require the ERDAS Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Included in Foundation Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
From ERDAS Products DVD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
From Intergraph Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
FlexNet Publisher Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Install Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Installing ERDAS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Install ERDAS Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
ERDAS File Association Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Installation Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Starting ERDAS Software for the first time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Installing Geodatabase Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
IMAGINE Geodatabase Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installing IMAGINE Geodatabase Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Install ArcGIS Engine Runtime Version Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Install IMAGINE Geodatabase Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Uninstalling ERDAS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Using the Install Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Install Condor for Intergraph 2013. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Pre Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
For use with ImageStation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
For use with IMAGINE and LPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Install ERDAS Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Install ERDAS IMAGINE and LPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Install Condor for Intergraph: Pool Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Install Submitting Machines and Processing Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Post Install Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
ImageStation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
IMAGINE and LPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Check Condor Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Using Condor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Table of Contents iii

Table of Contents iii

 In-Progress Job Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
0% Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Remove Jobs from the Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Add a Condor User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Condor Manual Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Jobs fail immediately. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Only one job is running on a processing that has multiple CPUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Jobs are not sent to some Processing nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Cannot submit jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Manual Configuration of Condor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Manual Configuration of the Pool Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Setting up the Credential Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Setting the Application Concurrency Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Manual Configuration of the Submitting Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Enable Access to the Credential Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Manual Configuration of a Processing Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Enable Access to the Credential Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Setting Other Processing Node Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Windows Printing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
No Pre-Rasterize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Pre-Rasterize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Adding Fonts to Annotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Create an .fdb File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Example .fdb Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Font to Symbol Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Adding Thai Font Support to Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Configuring IMAGINE VirtualGIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Stereo Configuration for Windows Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
ERDAS IMAGINE Preference Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

iv Table of Contents
 Preface

About this Manual

The ERDAS Desktop Products Installation and Configuration Guide provides
step-by-step instructions for installing ERDAS Foundation, ERDAS
IMAGINE®, LPS, and ER Mapper software. Sections regarding installing
Geodatabase support and Condor processing engine are also included.

Documentation
This Guide is part of a suite of on-line documentation that you receive with
ERDAS IMAGINE software. The basic document package, On-Line Help
Documentation, is delivered as HTML files.

The documents are found in <IMAGINE_HOME>\help directory where

<IMAGINE_HOME> represents the name of the directory in which ERDAS
IMAGINE is installed. Open the On-Line help system by clicking the Help
button on the IMAGINE Workspace, click on the Help button in a dialog, or by
selecting an item from a Help menu.

Example Data
Sample data sets are provided with the software. This data is separately
installed from the installation download or data DVD. For the purposes of
documentation, <ERDAS_Data_Home> represents the name of the directory
where sample data is installed.

Conventions Used in This Book

In ERDAS IMAGINE, the names of menus, menu options, buttons, and other
components of the Workspace are shown in bold type. For example:

“In the Raster dialog, select the Fit to Frame option.”

Raster is the name of a specific dialog and Fit to Frame is an option within that
dialog.

Terminology
When asked to use the mouse, you are directed to click, right-click, and so on.

• click — designates clicking with the left mouse button

Preface vii

Preface vii
 • shift-click — designates holding the Shift key down on your keyboard and
simultaneously clicking with the left mouse button
• middle-click — designates clicking with the middle mouse button

• right-click — designates clicking with the right mouse button

• hold — designates holding down the left (or right, as noted) mouse button

• drag — designates dragging the mouse while holding down the left
mouse button

Special Characters and Fonts

Certain characters and font styles have special meaning in ERDAS
documentation.

<words>

When you see words enclosed in < >, substitute the proper information for
these words. For example, when you see <IMAGINE_HOME>, replace it with
the name of the drive and directory where ERDAS IMAGINE is installed on
your system.

Prompts

Words that appear in the above font style represent program prompts that
appear on the screen.

Words that appear in the above font style are used to show commands that you
need to enter, and examples of data that you may enter as a response to a
program prompt. A word enclosed in brackets [ ] at the end of a prompt is the
default answer for that prompt. Press Enter key to accept the default answer.

Special Paragraphs
The following paragraphs are used throughout ERDAS documentation:

These paragraphs contain strong warnings or important tips.

These paragraphs lead you to other sections of this manual or other

specified manuals for additional information.

These paragraphs draw your attention to useful information.

Notes give additional instruction.

viii Special Characters and Fonts

 Preparation for Installation
This document provides updates to installation and configuration instructions
for ERDAS products on supported Microsoft Windows® operating systems.

This manual contains important updated information that is

crucial to the successful installation and operation of your
software. Read this user guide before trying to install or run an
ERDAS product.

It is strongly recommended that you have full administrator privileges to

install an ERDAS product on a Microsoft Windows operating system.

This chapter includes these topics:

• System Requirements

• ERDAS Foundation

• ERDAS IMAGINE and GeoMedia 6.x Compatibility

• Temporary File Location

• Administrator Privileges

• Add-on Modules

System Requirements
As with any advanced software, greater system resources result in greater
performance.

System requirements are subject to late changes. See the

Release Notes or visit our website at
http://geospatial.intergraph.com > specific Product > Product
Literature for the latest System Requirements.

ERDAS Foundation
Beginning with the release of ERDAS 2011, a substantial amount of shared
product content has been moved into a single common installer known as the
ERDAS Foundation.

Preparation for Installation 1

Preparation for Installation 1

 Before you can install the latest version of ERDAS IMAGINE, LPS,
ERDAS ER Mapper or ERDAS APOLLO, you must install the ERDAS
Foundation. See Installing the ERDAS Foundation.

The principal drivers for this change are as follows:

• An accelerating trend of growth in Geodetic Datums of the world, which

are being collected with increasing precision and density, and which are
updated more frequently to reflect seismic and volcanic changes in the
Earth’s surface.
• A firm decision by ERDAS that all of our vertical-datum-aware products
must support the latest Earth Gravitational Model (EGM 2008), at the
highest level of precision.
• A decision that all ERDAS products share a single copy of this large
datum, and all current and future large datum models we choose to
support.

Two-stage Installation
A consequence of these decisions is that many ERDAS products now require
a two-step installation process. First, you must install ERDAS Foundation
[current version], and then you can install any number of ERDAS applications.

This reflects our commitment to fully support high-precision coordinate

accuracy, and to handle coordinate systems consistently across the entire
ERDAS product line.

ERDAS IMAGINE and GeoMedia 6.x Compatibility

Beginning with the ERDAS IMAGINE 2013 release, the software contains
GeoMedia product core components. Due to this integration, the GeoMedia-
based functionality within ERDAS IMAGINE 2013 and higher release is not
compatible with GeoMedia 6.x (or earlier) version products. If you install
ERDAS IMAGINE 2013 or higher onto the same computer as GeoMedia 6.x,
both products will work, however certain functionality within ERDAS IMAGINE
will be disabled.

Upgrading GeoMedia 6.x to GeoMedia 2013, or installing only ERDAS

IMAGINE 2013, will enable full functionality.

If you install ERDAS IMAGINE 2013 first, you should not attempt to then install
GeoMedia 6.x products. If you need to install both products, you must install
the GeoMedia 6.x product first. This may require you to follow this installation
procedure:

1. Uninstall ERDAS IMAGINE 2013 product

2. Install GeoMedia 6.x product

2 Two-stage Installation
 3. Reinstall ERDAS IMAGINE 2013 product

This should not affect your ability to install fixes, updates and add-on modules
once the initial GeoMedia 6.x and ERDAS IMAGINE 2013 products have been
laid down.

Temporary File Location

Sometimes processes in an ERDAS product create temporary files. On a
system with multiple disk drives, the drive that contains the default directory
(c:\temp) may not have enough space. Be sure to set the Temporary File
Directory in the User Interface and Session category of the Preference
Editor to a directory with sufficient disk space (the actual amount you need
depends on the size of the files and applications you use).

Some temporary files may not be deleted automatically, causing the temporary
directory to become overloaded. If this happens, exit the ERDAS software and
delete the files in the temporary directory.

If the Temporary File Directory in the Preference Editor specifies a

nondirectory file or a nonexistent directory, no error message is reported and
the c:\temp directory is created and used for temporary files.

Refer to the “Microsoft Windows System Guide” for information on

configuring spool directories.

Exception
IMAGINE Subpixel Classifier does not use the Temporary File Directory
preference. Temporary files are stored using the Microsoft Windows operating
system environment variable TMP. You will need between 100 MB and 250
MB of free disk space to hold temporary files, depending on the size of the
image being processed.

If you wish to change the TMP environment variable, first exit running ERDAS
programs. If needed, create a new folder where the temporary files will reside.
Navigate to the System control panel.

Under some Microsoft Windows operating systems, select the Advanced tab
and then select Environment Variables.

Create or select the TMP User Variable. Modify the value to reflect your
desired temporary file location. Select Set and then Apply. Exit the control
panel.

Administrator Privileges
• To install an ERDAS product on a Microsoft Windows operating system, it
is strongly recommended that you have full administrator privileges.

Temporary File Location 3

 • The Administrator must create a user account for each user, giving each
user a username and password for logging into the system. A unique
home directory for each user is highly recommended in order to make use
of user-specific preference capabilities.
• The first time you run a new installation of an ERDAS product on a
Microsoft Windows operating system, you must be logged in as a user
with full administrative privileges.

Refer to the “Microsoft Windows System Guide” for information on setting

up user accounts.

Add-on Modules
LPS module is integrated into the ERDAS IMAGINE installer. You can use the
Photogrammetry options directly in the IMAGINE ribbon Workspace.

The ERDAS installation process may offer optional add-on modules.

Running any of these integrated or add-on modules requires purchasing a

license for them.

Local Installation
A local installation copies all necessary files and configures a machine to run
an ERDAS product independently. It copies executable files to disk. All of the
modules and components reside only on the designated machine; network
access is not required.

Existing Installation
You can also incorporate add-on modules into an existing installation of
ERDAS software.

In some cases, the module is included in the list of module components you
select during installation. For example, you can choose IMAGINE Objective
from the components list. If you have selected an add-on module during
installation, then you can also incorporate its license file as you do the license
file for other ERDAS software.

If you did not choose any add-on modules at the time of installation, you can
start the installation process again. This time, select only the modules you wish
to install. You can also enter the license file separately.

4 Add-on Modules
 Installing the ERDAS Foundation
ERDAS Foundation is a bundle of several components which are utilized in all
ERDAS products. This includes providing support for EGM 2008 (Earth
Gravitational Model) geodetic datum in all ERDAS vertical-datum-aware
products. Rather than require you to download multiple, redundant copies of
this large datum (and other capabilities) for each product you install, ERDAS
Foundation is a uniform, prerequisite installer that delivers a single copy of
EGM 2008 and several other large files used across the ERDAS product lines.

For more information on the ERDAS Foundation, visit

http://geospatial.intergraph.com/service/support/Installation/ERDAS_Fo
undation.aspx.

This chapter includes these topics:

• Licensing

• Installation Process

Prerequisite to Installing ERDAS Products

Installation of an ERDAS product is now a two-step process. Before an ERDAS
product can be installed, the current version of ERDAS Foundation must be
installed. The ERDAS product installer will refuse to install until the Foundation
is present. After the Foundation is installed on a system, any number of
ERDAS products may then be installed on the same system using a single
installation of ERDAS Foundation.

• ERDAS Foundation installation must precede installation of other ERDAS

products
• Only one installation of the ERDAS Foundation is required on any system;
then multiple ERDAS products may be installed on that system
• To avoid coordinate processing failures, you must install the ERDAS
Foundation before you can install any ERDAS Products that require it
• You must not remove (uninstall) the ERDAS Foundation before you have
removed all ERDAS products that rely upon it

ERDAS Products that Require the ERDAS Foundation

ERDAS products that require prior installation of the ERDAS Foundation are:

• ERDAS IMAGINE

• ERDAS LPS

• ERDAS APOLLO

Installing the ERDAS Foundation 5

Installing the ERDAS Foundation 5

 • ERDAS ER Mapper

Exceptions
Some ERDAS products do not require prior installation of ERDAS Foundation:

• ERDAS APOLLO Essentials

• ERDAS APOLLO Data Manager

• Condor for ERDAS

• ERDAS Extensions for ArcGIS

• ECW JPEG2000 SDK

• Example Data

• ORIMA

• PRO600

Included in Foundation Installer

The ERDAS Foundation installer includes:

• EGM 2008 geodetic datum

• Other sizable geodetic datums used to perform coordinate

transformations
• FlexNet Publisher Licensing

• Microsoft Runtime libraries (for example, MSVCRT) required by

applications

While FlexNet Publisher is bundled into ERDAS Foundation, you are still able
to install FlexNet Publisher standalone. If you install FlexNet Publisher and
then later decide to install ERDAS Foundation, FlexNet Publisher will not be
reinstalled (although it may be upgraded to the version included within ERDAS
Foundation).

Licensing
The FlexNet Publisher licensing application is installed when you install
ERDAS Foundation and includes On-Line documentation.

For Help topics, How to Generate Licenses, Rehosting, and questions,

visit www.intergraph.com/sgi/license.

6 Included in Foundation Installer

 Installation Process
The ERDAS Foundation is available on the ERDAS products DVD and may
also be downloaded from the Intergraph website
www.geospatial.intergraph.com.

From ERDAS Products DVD

Simply click on the ERDAS product you wish to install. If the current ERDAS
Foundation is required and not present, the DVD loader will automatically start
installation of ERDAS Foundation.

If a current ERDAS Foundation is discovered on the system, the ERDAS

product installation will start.

From Intergraph Website

ERDAS products are distributed in individual zip files from the Intergraph
Geospatial website. Therefore, if the current ERDAS Foundation is required
and not present, download the ERDAS Foundation installer zip file.

Unzip the files and execute by double clicking on "Setup.exe".

FlexNet Publisher Licensing

If a current version of FlexNet Publisher Licensing is required and not present,
the ERDAS Foundation installer will automatically start installation of FlexNet
Publisher Licensing.

Installation Process 7
 If ERDAS-Net Licensing application is discovered on the system, ERDAS
Foundation installer will install the current version of FlexNet Publisher
Licensing, and will not disturb any existing installation of ERDAS-Net
Licensing.

For Help topics, How to Generate Licenses, Rehosting, and questions,

visit www.intergraph.com/sgi/license.

Install Steps
1. Once Licensing is reconciled, the InstallShield Wizard begins the process
to install ERDAS Foundation. Click Next button.
2. Set the path and location where you want ERDAS Foundation to be
installed.
3. Once the installation path is set, click Install button to begin the
installation. Various processes will run during actual installation.
4. When installation is complete, click Finish button.

After ERDAS Foundation is installed on a system, proceed with installation of

any number of ERDAS products on the same system.

8 Install Steps
 Installing ERDAS Software
This section contains the steps for completing a local installation of ERDAS
software on a supported Microsoft Windows operating system.

A local installation is one in which the ERDAS program files are run from the
machine on which they are installed.

If you attempt to install ERDAS software on a supported Microsoft Windows

system without Administrator privileges, a dialog opens instructing you that you
are not able to install the software with the current privileges. Log out, then log
back in as a user with administrative privileges and then install IMAGINE.

This chapter includes these topics:

• Install ERDAS Software

• ERDAS File Association Manager

• Installation Tips

• Starting ERDAS Software for the first time

Install ERDAS Software

Follow these instructions to install ERDAS software.

You should close all running applications before installing ERDAS software.

1. Start Microsoft Windows.

2. Log in as a user with full administrative privileges.

You must be logged in as a user with full administrative privileges to

successfully install ERDAS software.

3. Double-click Setup.exe from the website installation file, or insert the

ERDAS installation DVD into the DVD drive.
The ERDAS Welcome dialog opens. Click Next.

Installing ERDAS Software 9

Installing ERDAS Software 9

 The License Agreement dialog opens. Please read the license agreement
in its entirety.
4. If you agree to the terms and conditions set forth in the Software License
Agreement, select the I accept the terms in the license agreement radio
button. If not, select the I do not accept the terms in the license agreement
radio button and click Cancel to exit the installation program.
5. If you accept the terms in the License Agreement, click Next in the License
Agreement dialog.
The Destination Folder dialog opens to specify the name of the directory
in which the IMAGINE files will be installed. All files required to run
ERDAS software are installed in this directory.
6. If you would like to change the installation directory, click the Change...
button to open the Change Current Destination Folder dialog.
7. Click to select or type the directory in which you would like to install
ERDAS software.
8. Click the OK button to return to the Destination Folder dialog.
9. Click the Next button.
The Select Features dialog opens to select the ERDAS software modules
you want to install.

10 Install ERDAS Software

 For an explanation of the icons, which indicate install status, click
the Help button.
10. Click to select the ERDAS software modules you want to install.
To deselect a module (make sure a module is not installed), you must:
• Click on the desired module icon to open the menu options.
• Select X This feature will not be available.
• Ensure that X is showing next to the module.
11. Click the Next button at the bottom of the Select Features dialog.
The Ready to Install the Program dialog opens.
12. Click the Install button to begin the actual installation.
During installation, a status bar tracks the progress of the installation.
When the status bar reaches 100%, the Performing one time
configuration tasks dialog opens.
When the configuration tasks are finished, the InstallShield Wizard
Completed dialog opens.
13. Click Finish in the InstallShield Wizard Completed dialog.

ERDAS File Association Manager

At the end of installation process, the ERDAS File Association Manager dialog
opens. You can associate selected file types to be associated with ERDAS
IMAGINE application. You can also open this dialog, also known as File
Registration Handler, later from within IMAGINE Workspace if needed.

ERDAS File Association Manager 11

 14. Make the file associations and click Close. The installation is complete.

Installation Tips

DVD Autorun
If your preference settings deactivate the DVD autorun, you can open this
dialog by selecting Start > Run from the Microsoft application bar and entering
<DVD>:\autorun.exe in the text box (where <DVD> represents the drive letter of
your DVD drive).

12 Installation Tips
 Example Data Installation
Installing ERDAS software does not install the Example data used in the
workflows. Example data is available from the Intergraph website -
www.geospatial.intergraph.com.

IMAGINE Developers Toolkit

IMAGINE Developers’ Toolkit is a stand-alone toolkit for a development
environment. It is downloadable from the Intergraph website at
http://www.geospatial.intergraph.com.

Why Certain ERDAS Modules Rely Upon 8dot3 Shortcuts

ERDAS IMAGINE and LPS 9.2+ versions of installation detect a rare 8dot3
setting which caused 9.1 and earlier installation versions to fail. In version 9.2
and later, the installer detects this situation and warns you during installation.
To avoid this warning/failure, make sure the following are true.

• MS NtfsDisable8dot3NameCreation registry entry is set to all zeroes (non

8.3 file or folder names cannot be created)
• Any folder names in the installation folders do not have a shortcut (non
8.3 format)
• Certain files (files with names similar to the install folder) are not present
in the installation path

The registry entry causes the second and third situation, but you must correct
the registry and also correct the file or folder names after your reset the
registry. Resetting the registry only corrects subsequent non 8.3 file or folder
format situations. You must reboot to activate the registry change.

Refer to the ERDAS Support webpage: geospatial.intergraph.com > Support >

Technical Support > Support > Knowledgebase > search for “8dot3” and “Error
193” for more information.

Starting ERDAS Software for the first time

1. After you install ERDAS software, start it from the Microsoft desktop.

If you have not yet completed the licensing option, the Welcome dialog
prompts you for your license information.

The FlexNet Publisher licensing application is installed when you install

ERDAS Foundation and includes On-Line documentation.

For Help topics, How to Generate Licenses, Rehosting, and questions,

visit www.intergraph.com/sgi/license.

Starting ERDAS Software for the first time 13

14 Starting ERDAS Software for the first time
 Installing Geodatabase Support
This section contains the steps for installing support for ArcGIS®
Geodatabases in ERDAS IMAGINE. With IMAGINE, you will have common
access to ArcGIS vector data sources.

If you have ArcGIS, ArcMap, ArcCatalog installed on your system, there

is no need to install Geodatabase Support. IMAGINE will automatically
interact with ArcGIS.

System requirements for ArcGIS interoperability are listed in the

current version of IMAGINE System Requirements document.
Visit our website at http://geospatial.intergraph.com > specific
Product > Product Literature for the latest System Requirements.

This chapter includes these topics:

• Installing IMAGINE Geodatabase Support

IMAGINE Geodatabase Support

ERDAS IMAGINE introduces the use of Esri ArcObjects environment to better
interact with the latest generation of ArcGIS software and data formats. The
use of ArcObjects means that ERDAS IMAGINE is better able to act as an
“extension” to ArcGIS, providing advanced image processing and remote
sensing capabilities, while transparently interacting with Esri data formats such
as the Geodatabase.

The following is a list of the types of read-only operations which exist within
ERDAS IMAGINE and which therefore can now be applied to the data sources
accessed in the Geodatabase.

• Display vectors on top of an image

• Include vectors in a map composition

• Display attributes associated with vectors in a table or the Form View

• Apply attribute-based symbolization to features

• Use features (points, lines, polygons) in supervised classification

• Use features in Spatial Models

• Use features in the Surfacing Tool

• Use features to define Areas of Interest (AOIs) to geographically

constrain any type of process that supports AOIs.

Installing Geodatabase Support 15

Installing Geodatabase Support 15

 The following types of edits would only apply to the Simple Personal
Geodatabase.

• Edit features (if the feature source is editable)

• Edit attributes (if the feature source is editable)

• Add/Create columns (if the feature source supports this)

Installing IMAGINE Geodatabase Support

Follow these instructions to install IMAGINE Geodatabase Support.

If you attempt to install Geodatabase Support on a Microsoft Windows system

without Administrator privileges, a dialog opens instructing you that you are not
able to install the software with the current privileges. Log out, log back in as a
user with administrative privileges and then install Geodatabase Support.

You should close all running applications before installing ERDAS IMAGINE
Geodatabase Support.

Install ArcGIS Engine Runtime Version Application

1. Start Microsoft Windows.
2. Log in as a user with full administrative privileges.

You must be logged in as a user with full administrative privileges to

successfully install ERDAS IMAGINE Geodatabase Support.

3. Double-click Setup.exe from the website installation file, or insert the

ERDAS installation DVD into the DVD drive.
4. Launch the installation wizard.
The ERDAS Geodatabase Support Install Shield Wizard dialog opens.
5. Click Install.
The Welcome dialog opens.
6. Click Next. The License Agreement dialog opens.
7. If you agree to the terms and conditions set forth in the License
Agreement, select the appropriate radio button and click Next. If not, click
Cancel to stop the installation.
If the installation has not been cancelled, the Select Installation Type
dialog opens.
8. Click Complete to install all application features. Advanced users may
click Custom if desired to choose specific application features to install
and installation location. Click Next.
The Destination Folder dialog opens to specify the directory in which the
ArcGIS Engine Runtime files will be installed.

16 Installing IMAGINE Geodatabase Support

 9. If you would like to change the installation folder, click the Browse button
to locate the desired folder. Click Next to continue.
The Python Destination Folder dialog opens. Python programming
language is required to support certain core Geoprocessing tools.
10. If you would like to change the Python destination folder, click the Browse
button to locate the desired folder. Click Next to continue.
The Ready to Install dialog opens, listing the destination folders of the
applications.
11. Click Next to begin installation.
When installation is complete, the successful installation notice opens.
12. Click Finish to close the installation program.

Install IMAGINE Geodatabase Support

Once the latest version of ArcGIS Engine Runtime is installed, then install
IMAGINE Geodatabase Support.

1. The Welcome dialog opens. Click Next.

The License Agreement dialog opens. Please read the license agreement
in its entirety.
2. If you agree to the terms and conditions set forth in the Software License
Agreement, select the I accept the terms in the license agreement radio
button. If not, select the I do not accept the terms in the license agreement
radio button and click Cancel to exit the installation program.
3. If you accept the terms in the License Agreement, click Next in the License
Agreement dialog.
The Destination Folder dialog opens to specify the name of the directory
in which the IMAGINE files will be installed. All files required to run
ERDAS software are installed in this directory.
4. If you would like to change the installation directory, click the Change...
button to open the Change Current Destination Folder dialog.
5. Click to select or type the directory in which you would like to install
ERDAS software.
6. Click the OK button to return to the Destination Folder dialog.
7. Click the Next button.
The Ready to Install the Program dialog opens.
8. Click the Install button to begin the actual installation.
During installation, a status bar tracks the progress of the installation.
When the installation is finished, the InstallShield Wizard Completed
dialog opens.
9. Click Finish in the InstallShield Wizard Completed dialog.

Install IMAGINE Geodatabase Support 17

18 Install IMAGINE Geodatabase Support
 Uninstalling ERDAS Software
When uninstalling ERDAS software, it is important to remember to uninstall all
of the modules and fixes in the reverse order from how they were installed. This
can be a confusing process, because you may not remember what that order
of installing was.

To help with the uninstallation process, you can now use the ERDAS Install
Manager. This dialog shows all of the ERDAS software that is installed on your
system, and the order in which each of the modules was installed.

This chapter includes these topics:

• Using the Install Manager

Using the Install Manager

1. Open the Install Manager from the Microsoft Windows Start menu or
screen. Select the ERDAS IMAGINE version program if needed.
The ERDAS IMAGINE Install Manager opens.

The Modules Installed list displays all of the ERDAS modules that have
been installed on your system.
2. Select a product or fix from the Modules Installed list. The selected
module is described in the Module Description field.

Uninstalling ERDAS Software 19

Uninstalling ERDAS Software 19

 If the selected module was the last module installed in that group, the Remove
button is enabled.

3. Click the Remove button to uninstall the selected module.

4. Continue removing modules until you have uninstalled the module that you
wanted to remove.
5. If necessary, you may now reinstall any of the modules that were removed
but that you would like to keep on your system.

20 Using the Install Manager

 Install Condor for Intergraph 2013
Condor, a free, open-source distributed processing engine, is the product of
the Condor Research Project at the University of Wisconsin-Madison (UW-
Madison). Condor’s unique mechanisms effectively harness wasted CPU
power from otherwise idle desktop workstations and dedicated Processing
nodes. It is ideally suited for the High Throughput Computing (HTC) that
ImageStation, ERDAS IMAGINE and ERDAS LPS require.

A Condor cluster (pool) includes a Pool Manager, Submitting machine, and

Processing nodes. Condor for Intergraph installs and configures Condor for
use with ImageStation, IMAGINE, and LPS. The installer also performs the
appropriate configuration for each of these machines.

This document describes the setup and operation of an example Condor

cluster for use with ImageStation, IMAGINE, and LPS. This is one example of
many possibilities; any specific configuration is outside the scope of this
document.

A Condor installation requires appropriate IT expertise to identify appropriate

hardware, set up, and configure. Use Condor only if you have the necessary
IT expertise. Intergraph does not support Condor issues beyond direct
interaction with its software.

These topics are included:

• System Requirements

• Pre Installation Steps

• Installation and Configuration

• Post Install Steps

• Using Condor

• Add a Condor User Account

• Condor Manual Documentation

• Troubleshooting

• Manual Configuration of Condor

System Requirements
A Condor cluster (pool) consists of a Pool Manager, a Submitting machine and
several Processing nodes. The Pool Manager is the central machine for the
cluster and needs to be a stable machine. Workstations that satisfy the system
specification of the target applications can be used as Submitting machines.
Processing nodes should be dedicated machines in order to maximize speed.

Pool Manager

• Windows Server 2008 R2 or Windows Server 2012

Install Condor for Intergraph 2013 21

Install Condor for Intergraph 2013 21

 Submitting machine

• No additional requirement over and above what is required by

ImageStation and/or ERDAS IMAGINE and LPS.

Processing node

• No additional requirement over and above what is required by

ImageStation and/or ERDAS IMAGINE and LPS.

Data Storage

• Separate RAID (one for input, one for output), though not required will
help improve performance.

Network

• A reliable LAN with speed of 1Gb or better

Pre Installation Steps

Before installing Condor, perform the following tests to ensure that the
machines are configured properly.

On All Machines

• Start the command prompt and at the command prompt enter

ipconfig.
• Note the IP address (or IPv4 address, if you are using Windows 7) that
is reported.

Pool Manager

• From the Pool Manager, ping the Submitting machine and the
Processing nodes by their DNS name
• Confirm that the reported IP address matches with the IP address the
machines reported

Submitting machine

• From the Submitting machine, ping the Pool Manager by its DNS
name
• Confirm that the IP address matches with the IP address the machines
reported

Processing Nodes

• Ping the Pool Manager by its DNS name

• Ping the Submitting machine by its DNS name
• Confirm that the IP address matches with the IP address the machines
reported

Data locations

22 Pre Installation Steps

 • Input data has to be on a network drive and accessible by the
Submitting and Processing nodes. Confirm this by browsing to the
input data locations from the Submitting and Processing nodes.
• Verify Submitting and Processing nodes have write access to the
output data folders.
• If mapped drives are going to be used, ensure the mapped drives are
accessible from all the machines in the Condor pool.

Installation and Configuration

For use with ImageStation

ImageStation Automatic Elevations (ISAE) and ImageStation Automatic
Elevations Extended (ISAE-Ext) support distributed processing using Condor.

ISAE must be installed on the Submitting and Processing nodes to process

jobs. Before installing Condor for Intergraph, install ISAE on the machines.

Refer to ISAE install guide for information on how to install ISAE.

For use with IMAGINE and LPS

ERDAS IMAGINE and LPS support a concept of shared installation, where the
Full ERDAS IMAGINE software will be installed on a single central machine
and will be shared with other machines. On the other machines, a network
version of ERDAS IMAGINE will be installed. The Network installer establishes
a link to the full ERDAS IMAGINE install.

A Microsoft Windows server machine is recommended to be used as the

central machine to allow multiple machines have access to it without
concurrency access limit. Since Condor Pool Manager is a Windows server
machine, it can also serve as the central machine for installing the full ERDAS
IMAGINE.

Before installing Condor for Intergraph, install ERDAS IMAGINE and LPS on
the Pool Manager. It has to be installed on a shared drive that can be accessed
from all machines in the pool.

Install ERDAS Foundation

• Create a mapped drive: ERDAS Foundation has to be installed on a
mapped drive that can be accessed by the Submitting and Processing
nodes.
• Typical install location: <Mapped drive>:\Program Files (x86)\Common
Files\Intergraph\ERDAS Foundation 2013
• Avoid path that has parenthesis () if you have 32-bit machines in your
pool

Installation and Configuration 23

 Install ERDAS IMAGINE and LPS
• Create a mapped drive: ERDAS IMAGINE and LPS have to be installed
on a mapped drive that can be accessed by the Submitting and
Processing nodes.
• Typical install location: <Mapped drive>:\Intergraph\ERDAS IMAGINE
2013
• Avoid path that has parenthesis () if you have 32-bit machines in your
pool

Refer to ERDAS Desktop Products Installation and Configuration Guide

for steps on how to install ERDAS Desktop products.

Install Condor for Intergraph: Pool Manager

Now you are ready to install Condor for Intergraph. Because the Pool Manager
is the most important part of the Condor pool, you must install that first. Next
install the Submitting machine and finally the Processing nodes.

1. If you are not already logged on the machine designated as the Pool
Manager, login to the machine with Administrative privileges.
2. Start the Condor for Intergraph Installation Wizard. Condor for Intergraph
requires Condor 7.8.x and if it not already installed on the machine, the
installer will first install Condor 7.8.3.
3. Click the Install button. The installer will check if Condor is already
installed and if it finds the machine has the minimum required version of
Condor, it will inform you and skip this step. Otherwise Condor 7.8.3 will
be installed.
4. If you are presented with the message Condor for Intergraph will use your
current version of Condor 7.8.3, then close the dialog.
The Welcome dialog opens.
5. Click Next in the Welcome dialog.
6. The License Agreement dialog opens. Read the contents of the Intergraph
Desktop software license and Limited Warranty Agreement.
7. If you agree to the terms and conditions set forth in the Software License
Agreement, select the I accept the terms in the license agreement radio
button and click Next.
The Destination Folder dialog opens to specify the name of the directory
in which the Condor files will be installed.
8. If you accept the default install directory, click Next button, otherwise click
Change button if you want to change the installation directory.
The Custom Setup dialog opens.

24 Install Condor for Intergraph: Pool Manager

 9. Choose the options to install. The ERDAS IMAGINE Network installation
is not required on the Pool Manager. Deselect the option and click Next
button.
The Condor Configuration dialog opens.

Install Condor for Intergraph: Pool Manager 25

 10. Select one of the two Condor configuration methods.
• If you want the installer to also configure Condor, choose the option
Have this installer configure Condor for me and click the Next
button. The Condor Install Type dialog opens.
• If you would rather configure Condor yourself, select the option I will
manage the Condor configuration myself, and refer to Manual
Configuration of Condor section for instructions.

26 Install Condor for Intergraph: Pool Manager

 11. Select the role of the machine in the Condor cluster. Since you are
installing on the Pool Manager, select Condor Pool Manager and click
Next button.
The General Condor Option dialog opens.

Install Condor for Intergraph: Pool Manager 27

 12. Enter the following information.
Domain The installer finds and displays the local domain name.
Pool Name Name for the Condor Pool. The default is Intergraph.
Pool Password Select and enter a password for the pool. The
password cannot contain spaces. Then retype the password to confirm.
Note your entries as you will use the same entries for the Processing
node and Submitting machine installations. Use the same capitalization
for the Processing node and Submitting machine installations.
Click Next button to open the Pool Manager Settings dialog.

28 Install Condor for Intergraph: Pool Manager

 13. Enter the following information.
Process Credential User ID Enter the user ID of the user who will be
submitting jobs. This user must have user access privilege on the domain
and administrative privileges for all machines in the Condor cluster.
Process Credential Password Enter the password for the User ID
account you just specified above. Retype to confirm the password.
Click Next button to open the Pool Manager Concurrency Limits dialog.

Install Condor for Intergraph: Pool Manager 29

 14. Enter the following information.
Number of IMAGINE/LPS Processing Engine Licenses Number of
concurrent processes to be run. This value should be at most equal to
number of ERDAS Engine licenses you have.
Number of ImageStation ISAE-DP Licenses Number of concurrent
processes to be run. This value should not be greater than the number of
ISAE-DP licenses you have.
Number of ImageStation ISAE-Ext DP Licenses Number of
concurrent processes to be run. This value should not be greater than the
number of ISAE-ExtDP licenses you have.
Click Next button to open the Ready to Install the Program dialog.
15. Click Install button to begin the installation. When the installation is
finished, the InstallShield Wizard Completed dialog opens.
16. Click Finish to complete the installation process. You have now finished
installing and configuring Condor for Intergraph on the Pool Manager.

Install Submitting Machines and Processing Nodes

1. Log on to each machine designated as a Submitting machine/ Processing
node with the user ID you specified when installing Condor on the Pool
Manager.
Follow the steps below to install and configure Condor for Intergraph.

30 Install Submitting Machines and Processing Nodes

 2. If Intergraph Licensing Administration tool is not installed on the machine,
install the tool and specify the license source.

Refer to the Intergraph Licensing Administration tool install guide for

information on how to install the tool and specify license sources, or visit
www.intergraph.com/sgi/license.

3. Follow steps 1 - 8 of Install Condor for Intergraph: Pool Manager.

After those steps are completed, the Custom Setup dialog opens.

4. Choose one of the following:

• Installation for ISAE/ISAE-Ext If you are installing and configuring
Condor for use with ISAE and/or ISAE-Ext, ERDAS IMAGINE Network
installation is not required. Deselect ERDAS IMAGINE Network
installation option, click Next button, then go to step 5.
• Installation for ERDAS IMAGINE and LPS If you are installing and
configuring Condor for use with ERDAS IMAGINE and LPS, ERDAS
IMAGINE Network installation is required. Select the option and click
the Next button. The ERDAS IMAGINE Network Installation Folder
Locations dialog opens.

Install Submitting Machines and Processing Nodes 31

 5. Enter the following path and location information.
ERDAS IMAGINE 2013 Software Location Enter or browse to the
shared installation location of ERDAS IMAGINE software.
ERDAS Foundation 2013 Software Location Enter or browse to the
shared installation location of ERDAS Foundation 2013 software.
Shared Output Data Location Enter or browse to the shared location
for the Output data.
Click Next button to open the Condor Configuration dialog.

32 Install Submitting Machines and Processing Nodes

 6. Select one of the two Condor configuration methods. If you want the
installer to also configure Condor, choose the option “Have this installer
configure Condor for me”.
Click Next button to open Condor Install Type dialog.

Install Submitting Machines and Processing Nodes 33

 7. For each installation, select which role each machine will be assigned, that
is, Condor Submitting Machine or Condor Processing Node.
Click Next button. The General Condor Options dialog opens.

34 Install Submitting Machines and Processing Nodes

 8. Enter the following information.
Domain The installer finds and displays the local domain name. You
can change the Domain name.
Pool Name Enter the same name you entered for the Pool Manager.
Pool Password Enter the same password you entered for the Pool
Manager.
Click Next button. The Submitting Machine and Processing Node settings
dialog opens.

Install Submitting Machines and Processing Nodes 35

 9. Enter following information.
Pool Manager Hostname Machine name of the Pool Manager.
Number of CPUs to Advertise This option is available on Processing
nodes only. Enter the number of concurrent processes you want to run on
the machine.
Number Available This option is available on Processing nodes only.
Displays the number of CPUs the machine contains. Use this as a guide
for determining how many processes to run concurrently.
Click Next button to open the Ready to Install the Program dialog.
10. Click Install button to begin the installation. When the installation is
finished, the InstallShield Wizard Completed dialog opens.
11. Click Finish to complete the installation process. You have now finished
installing and configuring Condor for Intergraph for one Submitting
machine or Processing node.
12. Repeat the Install Submitting Machines and Processing Nodes steps for
each machine.

36 Install Submitting Machines and Processing Nodes

 Post Install Steps

ImageStation
1. On the Submitting and Processing nodes machines, start ISAE and/or
ISAE-Ext application.
2. Verify the installation has succeeded and the machines have access to
licenses.

This simply verifies that the machine can get ISAE and/or ISAE-
Ext licenses. Run an ISAE and/or ISAE-Ext job if you want to
verify that you have ISAE and/or ISAE-Ext processing licenses.

IMAGINE and LPS

1. On the Submitting and Processing nodes machines, start IMAGINE and
LPS applications, as well as the applications that will be running processes
using Condor.
2. Verify the installations have succeeded and the machines have access to
licenses.

This simply verifies that the machine can get IMAGINE licenses.
To verify that you have license for a specific application, start and
run the application.

Check Condor Status

1. Log on to the Submitting machine.
2. Open the command line tool and type: condor_status
The command lists the Processing nodes in the pool. The Machines
configured as Processing nodes should be listed.

Using Condor
For ISAE and ISAE-Ext applications, click the Submit Distributed button to
submit jobs to Condor.

For IMAGINE and LPS applications, you use Condor as follows:

1. Click the Batch button from any process that contains a Batch option.
2. From the Batch Command Editor, click Submit button. In the Submit
dialog, choose the Start Distributed Processing option.

Post Install Steps 37

 Refer to the Batch Command Editor On-Line Help for instructions.

In-Progress Job Status

When you set up a job and start processing using Condor Run, you can check
the status of the in-progress jobs.

1. Log on to the Submitting machine.

2. Open the command line tool and type:
condor_q
• Lists all the processes submitted to the pool from all the active Pool
Managers
• “Idle” indicates that the job will be sent to a machine as soon as one is
available
• “Held” indicates a potential problems. Use Condor_q-analyze for
more information
condor_q -run
• Lists only the currently running processes
condor_status
• Shows the status of the machines in the pool

ERDAS IMAGINE and LPS applications report operation progress status to the
active Process List dialog, where operation progress can be tracked.

0% Status
If the progress bar reads 0% and does not start, remember that the machine
speed, network bandwidth, disk read/write speed, and job size affect the speed
of starting a job. It can take several minutes for a job to start.

If the job never starts, use Condor_Status to check the status of the
machines. Also, use Condor_q to make sure the jobs are not held.

Remove Jobs from the Queue

Use the Condor_rm-all command to remove all jobs from the queue.

Add a Condor User Account

Follow these steps to give others permissions to use Condor pool.

1. Log on to the Pool Manager machine.

2. Open the command line tool and type:

38 In-Progress Job Status

 condor_store_cred add -u username@domain -p password
Where:
username = new user
password = password for the new user
3. Look for the message “Operation Successful”.

Condor Manual Documentation

A Condor Manual that provides extensive documentation for both users and
system administrators is available at the following website:

http://research.cs.wisc.edu/condor/manual

Troubleshooting

Jobs fail immediately

If jobs fail quickly after they are sent to a Processing node, it may be caused
by a lack of license for processing the job. Verify that you have enough number
of licenses to run the specified number of jobs in parallel.

To change the number of concurrent jobs, edit the Pool Manager machine’s
condor_config.local file.

In the condor_config.local file:

ERDASENGINE_LIMIT – specifies the maximum number of concurrent

ERDAS IMAGINE jobs
ISAE_DP_CONCURRENCY_LIMIT – specifies the maximum number of
ISAE jobs
ISAE_EXT_CONCURRENCY_LIMIT – specifies the maximum number of
ISAE-Ext jobs

These should be less than the number of licenses you have purchased. Edit
the entries appropriately and run condor_reconfig in the command prompt.

If licensing is not the issue, it may be that there be a problem with the input
data. Verify that the input data can be accessed from the Processing node.

Only one job is running on a processing that has multiple CPUs

By default, Processing nodes are configured to run one job at a time. This can
be changed during installation.

Condor Manual Documentation 39

 See Install Submitting Machines and Processing Nodes – Step 8.

To change this after installation, locate condor_config.local file in the Condor

installation directory and edit the NUM_CPUS to the number of jobs you want
to run concurrently and restart Condor by entering condor_restart in the
command line.

You may re-run the Condor for Intergraph installer in Condor Configuration
modify mode, and re-enter Number of CPUs to Advertise.

ISAE-Ext uses large memory therefore it is not advised to run multiple

jobs on one machine.

Jobs are not sent to some Processing nodes

If you notice that jobs are not sent to some Processing nodes, run the following
command on the Pool Manager:
condor_status -f "%s\t" Name -f "%s\n" ifThenElse(isUnde-
fined(LocalCredd),\"UNDEF\",LocalCredd)

This will produce output something like:

Condor_LM2.ingrnet.com condor_lm1.ingrnet
Condor_LM3.ingrnet.com condor_lm1.ingrnet
Condor_LM4.ingrnet.com UNDEF
Condor_LM4.ingrnet.com UNDEF
• If the second column contains the name of the Pool Manager, then the
Processing node is communicating correctly with the credential
daemon.
• If the second column contains ‘UNDEF’, then the Processing node is
not communicating correctly, and jobs will not submit to this node.

To resolve this, there are various things to try:

1. On the Pool Manager, run condor_restart –all to restart Condor on

all nodes in the pool. The restart may take several minutes to complete on
all machines.
2. If that does not work, run condor_restart directly on the Processing
node or nodes that report UNDEF. Again, the restart may take several
minutes to complete.
3. If that does not work, re-enter the pool password on the Processing node
or nodes that report UNDEF, that is, run condor_store_cred –c add,
followed by condor_reconfig.
4. If that does not work, re-enter the pool password on all machines of the
pool.

40 Jobs are not sent to some Processing nodes

 For steps 3 and 4, you may re-run the Condor for Intergraph installer in Condor
Configuration modify mode on each machine, and re-enter the pool password
that way, rather than use the command line.

Detailed information regarding credential daemon is available in section

6.2.5 The condor_credd Daemon of the Condor Manual
Documentation.

Cannot submit jobs

Condor_submit command will fail if the credentials of the user attempting to
submit a job have not been stored in the credential daemon on the Pool
Manager. In this case, job submittal in IMAGINE or ImageStation applications
will simply fail.

To resolve, submit the job manually using condor_submit manually on

command prompt to see what additional information it reports about the error.

If it indicates a lack of stored credentials, store the user’s credentials using

condor_store_cred add on the Pool Manager.

Manual Configuration of Condor

You can use the Condor for Intergraph installer to re-use an existing
installation of Condor from the University of Wisconsin-Madison, as well as add
Intergraph applications to the Condor pool. By selecting the option I will
manage the Condor configuration myself in the Condor Configuration
dialog of the Installation wizard, the installer will not make any modifications to
your existing Condor configuration.

Intergraph applications do however require some specific configuration values

to be present in order to run successfully in a Condor pool. If you opt not to
have the installer create those values, then you must set them manually
instead, by manually editing the Condor configuration files.

Manual Configuration of the Pool Manager

Setting up the Credential Daemon

ImageStation and ERDAS IMAGINE applications use the Condor credential
daemon to manage user authentication on the Processing nodes. The
credential daemon is not enabled by default in a Condor installation, and hence
must be configured manually. Typically, the daemon will be set up to run on the
Pool Manager machine.

If your Condor pool is not currently configured to use the credential daemon,
follow these steps:

Cannot submit jobs 41

 1. Locate the sample credential daemon configuration file within the Condor
installation:
etc/condor_config.local.credd
2. Using a text editor, copy the content of the sample file to the local Condor
configuration file, which is named condor_config.local.
3. Restart Condor using condor_restart command.
4. Open Windows Task Manager and verify that the condor_credd process
is now running.
5. Create the Pool password using the command:
condor_store_cred –c add
6. The command will prompt you to enter the password.

The same password will later need to be entered on all other

machines within the pool.
7. For all users who will have the ability to submit jobs, add their credentials
using the command:
condor_store_cred add –u <username>@<domain>
8. The command will prompt you to enter each user’s password.
9. Run the command condor_reconfig to force Condor to re-evaluate its
configuration.

Setting the Application Concurrency Limits

ImageStation and ERDAS IMAGINE employ concurrency limits on the Pool
Manager to ensure that Condor will not attempt to run more jobs than the
number of licenses you have purchased.

To set the concurrency limits, follow these steps:

1. Locate and open for edit the local Condor configuration file, which is
named condor_config.local.
2. Depending on which application is employed, select one of the following:
• If you will use the Condor pool to process IMAGINE batch jobs or the
LPS eATE application, add the following variable definition:
ERDASENGINE_LIMIT = n
Where n should be set to the number of ERDAS Engine licenses that
you have or wish to make available.
• If you will use the Condor pool to process ImageStation Automatic
Elevations (ISAE) jobs, add the variable definition:
ISAE_DP_CONCURRENCY_LIMIT = n
Where n should be set to the number of ISAE DP licenses that you
have or wish to make available.

42 Manual Configuration of the Pool Manager

 • If you will use the Condor pool to process ImageStation Automatic
Elevations Extended (ISAE-Ext) jobs, add the variable definition:
ISAE_EXT_CONCURRENCY_LIMIT = n
Where n should be set to the number of ISAE-Ext DP licenses that you
have or wish to make available.
3. Save your edits to condor_config.local.
4. Restart Condor using condor_restart command.

If you are unsure how many licenses you have available, you can
use the Intergraph License Administration tool to find out.

Manual Configuration of the Submitting Node

Enable Access to the Credential Daemon

The Submitting node must be able to access the credential daemon on the
Pool Manager in order to be able to submit ImageStation and IMAGINE jobs to
the Condor pool.

To enable this access, follow these steps:

1. Locate and open for edit the local Condor configuration file, which is
named condor_config.local.
2. Add the following variable definitions:
CREDD_HOST = <pool manager hostname>.$(UID_DOMAIN)
CREDD_CACHE_LOCALLY = True
SEC_CLIENT_AUTHENTICATION_METHODS = NTSSPI, PASSWORD
SEC_CONFIG_NEGOTIATION = REQUIRED
SEC_CONFIG_AUTHENTICATION = REQUIRED
SEC_CONFIG_ENCRYPTION = REQUIRED
SEC_CONFIG_INTEGRITY = REQUIRED
Where <pool manager hostname> should be replaced with the name
of your Pool Manager machine.
3. Save your edits to condor_config.local.
4. Restart Condor using condor_restart command.
5. Add the Pool password using the command:
condor_store_cred –c add
6. The command will prompt you to enter the password.

This must be the same password as was used on the Pool

Manager machine.
7. Run the command condor_reconfig to force Condor to re-evaluate its
configuration.

Manual Configuration of the Submitting Node 43

 Detailed information regarding credential daemon is available in section
6.2.5 The condor_credd Daemon of the Condor Manual
Documentation.

Manual Configuration of a Processing Node

Enable Access to the Credential Daemon

All Processing nodes must be able to access the credential daemon on the
Pool Manager in order to be able to process ImageStation and IMAGINE jobs.

To enable this access, follow these steps:

1. Locate and open for edit the local Condor configuration file, which is
named condor_config.local.
2. Add the following variable definitions:
CREDD_HOST = <pool manager hostname>.$(UID_DOMAIN)
CREDD_CACHE_LOCALLY = True
SEC_CLIENT_AUTHENTICATION_METHODS = NTSSPI, PASSWORD
SEC_CONFIG_NEGOTIATION = REQUIRED
SEC_CONFIG_AUTHENTICATION = REQUIRED
SEC_CONFIG_ENCRYPTION = REQUIRED
SEC_CONFIG_INTEGRITY = REQUIRED
Where <pool manager hostname> should be replaced with the name
of your Pool Manager machine.
3. Save your edits to condor_config.local.
4. Restart Condor using condor_restart command.
5. Add the Pool password using the command:
condor_store_cred –c add
6. The command will prompt you to enter the password.

This must be the same password as was used on the Pool

Manager machine.
7. Run the command condor_reconfig to force Condor to re-evaluate its
configuration.

Detailed information regarding credential daemon is available in section

6.2.5 The condor_credd Daemon of the Condor Manual
Documentation.

44 Manual Configuration of a Processing Node

 Setting Other Processing Node Variables
Various other configuration variables are required or are optional on the
Processing nodes of the pool.

To set these variables, follow these steps:

1. Locate and open for edit the local Condor configuration file, which is
named condor_config.local.
2. All Processing nodes must be configured to allow jobs to execute using the
credentials of the user submitting the job. To do this, add the following
variable:
STARTER_ALLOW_RUNAS_OWNER = True

This variable is mandatory.

3. Processing nodes having multiple CPUs may be configured to allow only
a subset of those CPUs to be available for running Condor jobs. If you wish
to limit the number of available CPUs, add the following variable:
NUM_CPUS = n
Where n should be less than or equal to the number of physical CPU
cores in the machine.

If this variable is not set, all CPU cores will be available.

4. Save your edits to condor_config.local.
5. Locate and open for edit the global Condor configuration file, which is
named condor_config.
6. Locate and change the values of the following variables, in order to allow
ImageStation and IMAGINE jobs to always start execution immediately
and to not allow them to be suspended:
START = True
SUSPEND = False
PREEMPT = False

These settings are mandatory; ImageStation and IMAGINE jobs

do not support being suspended.
7. Save your edits to condor_config.
8. Run the command condor_reconfig to force Condor to re-evaluate its
configuration.

Manual Configuration of a Processing Node 45

46 Manual Configuration of a Processing Node
 Windows Printing
This chapter provides information about how to set up your map composition
in the Map View for printing.

This document is based on the premise that the printing to be done can be
executed on an HP printer plotter using an HPRTL printer driver.

These topics are included:

• Troubleshooting

• Scenarios

Troubleshooting
Sometimes when you are trying to print a map, system resources are
consumed by the printing process, and the attempt to plot fails. There are
several ways in which a printing failure might manifest itself. Depending on the
type of print device being used, the indications of failure vary. The most
common, of course, is that you do not successfully print the desired map. The
symptoms of failure shown below are common for HP 600 to 3500 plotters.
This includes the 1055 series.

Out of Memory/Data Lost

This is a printer panel message that is displayed when the printing application
overwhelms the printer memory with data. This commonly occurs when
postscript print drivers are used to attempt a print job that sends more data to
the print device than the print device has memory to handle.

In ERDAS software, this situation can also occur if you do not choose to
Rasterize before printing. In the case where the you do not choose to
Rasterize before printing, the map composition should be processed using
the In computer memory option. Commonly, when the system runs out of
memory, the composition is partially printed. It is not unusual that whole
elements of the map composition might be missing.

Nothing Prints
In another example, you send your map composition to print, and the process
initiates successfully. However, as soon as the print job switches from spooling
to printing, the job is deleted from the queue. There are no results to speak of.
The only potential error message is from the OS: Your system is running
low on virtual memory. Please close some applications. This
is dependent on your system’s virtual memory settings.

Windows Printing 47

Windows Printing 47
 It is advisable that you increase the default Microsoft Windows virtual memory
settings. On Microsoft Windows systems, there are initial and maximum size
settings for the virtual memory that are made available to applications. The
default minimum memory is acceptable, but the overall may need to be
increased.

Changing Memory Settings

Increasing overall memory can be accomplished by:

• increasing the maximum on the existing paging file.

• creating an additional paging file (if there is not sufficient free disk space
on the drive or partition where the other paging has been created).

It is also common that, when the Commit Charge value on the Microsoft
Windows Task Manager exceeds ~ 1 GB, nothing prints. Eventually, this
occurs when processing without Rasterize before printing and In computer
memory.

Preferences

Strip Height
The Strip Height is set to 64 by default. This is an acceptable strip height. This
is the height of each strip of data that is sent to the plotter.

Printing Data Transfer Compression

Printing Scale Factor is the scaling factor at which the output data is created.
This scale applies to the output frame size. For example:

none = 1x
low = 2x
medium = 4x
high = 8x

For example, if the image that is being put into a frame is 5000 x 6000 pixels,
and the frame in which the image data is going to be printed is 17” x 20”, and
you are plotting at 600 dpi, then there are 5000 pixels with which to fill 10200
dots.

Scaling is always constrained to the smaller of the dimensions to maintain

geometric fidelity. In the example above, a scaling factor of 2 would be
appropriate. If a scaling factor of one were used, ERDAS IMAGINE would
create a file big enough to fill the output map frame. This is, in essence,
quadrupling the size of the raster data needed to be sent to the plotter.

48 Preferences
 Moreover, a scale factor of two is a good trade-off in that little annotation
degradation occurs. If the Printing Scale Factor is too high, text annotation can
become pixelated.

Spool Data as Raw File Format

In order to print successfully in ERDAS IMAGINE, data must be spooled to the
printer as Raw file format rather than EMF file format.

Follow your printer’s instructions to spool data to the printer as Raw.

Scenarios
You may encounter the following scenarios when printing:

No Pre-Rasterize
These steps work for a moderate size map composition (for example, 24” x 36”
at 600 dpi). The no pre-rasterize scenario does not create a temporary file: all
processing is handled in memory. This scenario can lead to the situation where
nothing prints when the limits of system memory are exceeded. Any time the
Commit Charge exceeds 1 GB, the print job is removed from the queue.

Preparation
ERDAS IMAGINE must be running.

You must have a map composition displayed.

The map composition displayed in this scenario is not supplied

with the examples data.

The following picture shows a Map Composition ready to print:

Spool Data as Raw File Format 49

 Open the Map Composition Dialog
1. In the Map Composer dialog, click the Print icon .

The Print Map Composition dialog opens. The Print Map Composition dialog
opens on the Printer tab. In this tab, you can select a printer you have
configured.

The Printer tab allows you to

select a configured printer that
can print the map composition

50 No Pre-Rasterize
 2. Click the Print Destination dropdown list and choose an appropriate
printer.

In this example, the HP DesignJet

2500CP by HP printer is chosen
as the Print Destination

The Print Destination you select displays in the Print Map Composition
dialog. Now, you can set configuration parameters.

The printer you chose

displays in the Print
Destination window

Click the Change printer

configuration button

3. Click on the Change printer configuration button.

The Properties dialog for the printer you select displays. In this case, the title
of the dialog is HP DesignJet 2500CP by HP.

No Pre-Rasterize 51
 In the Properties dialog,
click on the More sizes
button

4. Click on the More sizes button.

The Paper Sizes dialog opens. In this dialog, you can set the paper size
required for your particular map composition.

Set custom paper

size in this area

5. Click in the Custom paper size section of the Paper Sizes dialog and type
the size of the paper. In this case, the appropriate size is 36” x 26”.
6. Click OK in the Paper Sizes dialog.

You are returned to the Paper Size tab of the Properties dialog.

52 No Pre-Rasterize
 Choose the Landscape
orientation

7. In the Paper Size tab of the Properties dialog, click the Landscape
orientation radio button. This option conserves paper.
8. Click the Layout View tab in the Properties dialog.

The Layout View information displays.

The Layout View tab shows that the width is 36”, and the height is 26”. The
36” dimension runs across the 36” width of the roll of paper.

9. Click the Options tab in the Properties dialog.

The options display. In this tab you make color and paper selections.

No Pre-Rasterize 53
 10. In the Options tab, click the checkbox for Manual color.

You are going to come back to the Color control setting in a moment.

11. Click the Paper type dropdown list, and select the type of paper.

The Quality setting controls the dots per inch (dpi) that is used to plot the map.
There are different quality designations used by different printer drivers. Some
common HP quality designations are:

• Fast (draft) (300 dpi)

• Normal (final) (300 dpi)

• Best (enhanced) (600 dpi)

• Economy (300 dpi)

• Productivity (300 dpi)

• Photo (600 dpi)

54 No Pre-Rasterize
 So far, you have selected the
Manual color radio button as
well as the Paper type

12. Click on the Advanced tab in the Properties dialog.

The advanced options display in the Properties dialog.

Select the process

document setting in this
area

13. In the Process document section of the Advanced tab, click the In
computer radio button.

You need to select the In computer option in order to successfully print the
color calibration pages which follow.

A Hint dialog opens that warns of slower printing. You are going to process the
document in the computer memory when you do not pre-rasterize anyway.

14. Click OK in the Hint dialog.

No Pre-Rasterize 55
 15. Click the Inked Area checkbox.

Your Advanced tab should now look like the following:

Select the In computer

option

Color control
1. Click the Options tab in the Properties dialog.
2. Click on the Color control button in the Options tab.

The Color Control dialog opens.

Select User defined

color correction

Start the Color

Correction Wizard

3. In the Printed color control section of the Color Control dialog, click on
the User defined color correction radio button.
4. Click on the Start Color Correction Wizard button.

The Start Color Correction Wizard dialog opens.

56 No Pre-Rasterize
 Select Use the current
document in your
application

5. Click the Use the current document in your application radio button.

The next Start Color Correction Wizard dialog opens. It provides information
about using the current document as the basis for the Color Correction Wizard.

Click OK

6. Click OK in the Start Color Correction Wizard dialog.

A Job Status dialog opens to show the progress of the document capture.

7. Click OK in the Color Control dialog and the Map Composition dialog.
8. Depending on your preference settings, you may need to click OK in the
Job Status dialog to close it.

The Color Correction Wizard welcome dialog opens.

Click Next to advance to

the next panel of the Color
Correction Wizard

9. Click Next in the Color Correction Wizard dialog.

No Pre-Rasterize 57
 The next Color Correction Wizard dialog suggests a series of steps.

Click Next

10. Click Next in the Color Correction Wizard dialog.

Click Next

11. Click Next when the No transformation message is displayed above the
document preview.

The Brightness is adjusted in this step.

Choose the
Brightness option in
the Select
Transformation
section

The next dialog advises you to prepare the printer. Next, the sample pictures
are going to be printed.

58 No Pre-Rasterize
 Click Next to print
the sample images

12. Click Next to print the sample images.

13. Once you get the sample images from the printer, compare the sample
image printout to the map on your screen.
14. In the Picture Selected section, type the number of the image that best
represents the brightness of the map. In this example, 9 is the best.

15. Click Back twice to define the contrast setting.

Click Back again

In the Color Correction Wizard dialog you can set Contrast:

No Pre-Rasterize 59
 Select the Contrast option

16. Click on the Contrast radio button.

17. Click Next when the No transformation message is displayed above the
document preview.
18. Click Next to print the sample images.
19. In the Picture Selected section, type the number of the image that best
represents the brightness of the map. In this case, 8 is best.

Select the picture you

like best in the Picture
Selected field

20. Click Back twice to define the Color Balance setting.

21. Click Back again.

Click Back

Now, you can select the Color Balance option.

60 No Pre-Rasterize
 Select the Color
Balance radio button

22. Click on the Color Balance radio button.

23. Click Next when the No transformation message is displayed above the
document preview.
24. Click Next to print the sample images.
25. In the Picture Selected section, type the number of the image that best
represents the brightness of the map. In this case, 6 is best.

The picture number 6 is

the best for Color Balance

Click Next

26. Click Next in the Color Correction Wizard dialog.

Now, you have defined all three elements of the Color Correction Wizard:
Brightness, Contrast, and Color Balance.

27. Click on Finish in the Color Correction Wizard.

A dialog opens advising you that the color calibration was a success.

No Pre-Rasterize 61
 28. Click on OK in the Color Calibration Successful dialog.

You are returned to the Properties dialog. If you have the User Defined Color
Correction selected, it uses your color calibration.

29. Click the Advanced tab in the Properties dialog.

30. Click OK in the Properties dialog.

Return to the Print Map Composition Dialog

1. Click the Page Setup tab in the Print Map Composition dialog.

Your Print Map Composition dialog Page Setup tab should look like this:

Click the Page

Setup tab

2. Click the Options tab of the Print Map Composition dialog.

The Options tab looks like this:

62 No Pre-Rasterize
 Click the
Options tab

3. Click the Preview tab of the Print Map Composition dialog.

Finally, your Preview tab should look like this:

Click the Preview

tab

4. Click OK to print your map.

Pre-Rasterize
Another scenario involves the Pre-Rasterize option. If you want to print large
maps or print to higher resolution print devices, it is probably necessary to use
the Pre-Rasterize option in ERDAS IMAGINE in conjunction with an HPRTL
driver. There are similar languages that can be utilized with plotters sold by
other printer manufacturers.

Pre-Rasterize 63
 This map is large. It is 52” x 68”. It is printed at 600 dpi, and would easily
exceed the system limits for successful printing. This map cannot print without
pre-rasterization unless the Printer Data Transfer Compression preference is
set to high. Even then, the raster data that is printed appears highly degraded
as no higher than a compression factor of low or 2 can be effectively used with
this data. Consequently, the Pre-Rasterize option is used in order to print
successfully.

The 52” height of the map corresponds with the 54” width of the paper for the
HP 3500. There are effectively 31200 pixels, or dots, available for plotting at
600 dpi. The image in the map frame is 37000 pixels high. This map would be
best processed with the Printer Data Transfer Compression preference set
to none, but that would also quadruple the amount of data that is sent to the
plotter. So, you are going to use the default Printer Data Transfer
Compression preference low. This generally provides acceptable results.

Preparation
ERDAS IMAGINE must be running.

You must have a map composition displayed.

The map composition displayed in this scenario is not supplied

with the examples data.

1. In the Map Composer dialog, click the Print icon .

The Print Map Composition dialog opens on the Printer tab. In this tab, you
can select a printer you have configured.

64 Pre-Rasterize
 2. In the Print Map Composition dialog, select the printer from the Print
Destination dropdown list.

Select the printer from

the dropdown list

Once you choose your printer, the Rasterize before printing option displays.

Click the Change printer

configuration button

Click to select the Rasterize

before printing option

3. Click the Rasterize before printing checkbox.

4. Click on the Change printer configuration button.

The Properties dialog opens. It has the name of the printer you selected as the
Print Destination.

Pre-Rasterize 65
 Set the page size here

5. In the Application page size section of the Page Size tab, set the paper
size to 54” x 72”.
6. Click on the Layout View tab of the Properties dialog.

Click the Layout View tab

7. Look at the Layout View to verify the parameters.

8. Click on the Options tab of the Properties dialog.

The Options display.

66 Pre-Rasterize
 Select Manual
color
Click the Color
control button
Set the Paper type
and Quality

9. Set the Paper type and Quality.

The Quality should be set to Photo or Best, which is 600 dpi if the highest
quality is desired.

10. Click on the Manual color radio button in the Options tab.
11. Click on the Color control button to check the Color Control settings.

The Color Control dialog opens.

Select the User

defined color
correction radio
button

12. Set the Printed color control to User defined color correction.

This should still be set to the same values used in the previous exercise. If you
did not perform the previous exercise, the procedure for setting the User
defined color correction is fully described there.

13. Click on the Advanced tab.

Pre-Rasterize 67
 14. Click the In Printer radio button.

In the previous exercise, the In Computer radio button was set so that printing
could be done using the no pre-rasterize method in ERDAS IMAGINE.

15. Click OK in the Advanced tab.

The Page Setup tab of the Print Map Composition dialog opens:

16. Verify the parameters on the Page Setup tab.

17. Click the Options tab.

68 Pre-Rasterize
 Click the Options tab

18. Verify the parameters on the Options tab.

19. Click on the Preview tab.

Click the Preview tab

20. Examine the Print Preview.

21. Click OK in the Print Map Composition dialog to print.

Pre-Rasterize 69
70 Pre-Rasterize
 Adding Fonts to Annotation
This section describes how to add new fonts to ERDAS IMAGINE annotation.

The following topics are included:

• Create an .fdb File

• Example .fdb Entries

• Font to Symbol Utility

• Adding Thai Font Support to Microsoft Windows

Create an .fdb File

To add True Type system fonts to the ERDAS IMAGINE annotation package,
you must add the new fonts to a font data base (.fdb) file in any of the
directories specified in the ERDAS_FONT_PATH, which is, by default, the
<IMAGINE_HOME>/etc/fonts directory where ERDAS IMAGINE is installed on
your system.

You can create a new file or edit an existing file. You may use
<IMAGINE_HOME>/etc/fonts/fontlist.fdb as an example, but be aware that the
contents of the fields may look different for the OTL fonts that are distributed
with ERDAS software, and that your file should only have entries for your fonts.

If you create a new file, you can give it any name as long as it is in one of the
directories mentioned above. User-defined directories may be used by adding
them to the ERDAS_FONT_PATH environment variable in the Environment
tab of the ERDAS IMAGINE Properties dialog. Note that a file named “a.fdb” in
the current directory overrides a file named “a.fdb” in the directory from which
you started ERDAS IMAGINE, which in turn overrides a file named “a.fdb” in
the etc/fonts directory.

The first non-comment line of the .fdb file must be “version 3”.

You must have a seven-field entry in your .fdb file for every font you want the
annotation package to know about. All of the name and string fields in the entry
should be in quotes. Only the Font Language Flag field is unquoted.

The following chart lists these fields and the information they specify.

Adding Fonts to Annotation 71

Adding Fonts to Annotation 71

 Table 1: Font Fields

Field Number Field Name Font Information1

One Font Name Use the Font File Name below (without
variations) or use another name of your
choice. This is the name you see in the
scrolling list of available fonts in the Text
Style Chooser, plus any special weight
and/or slant attributes. 2

Two Font File This field is the Font Name as shown in

Name Fonts Control Panel.

Three ASCII This is a printer-downloadable file that

PostScript goes with the selected font. It is the font
File Name file that is included in the EPS file that is
created when you output your Map
Composition to an EPS file. When you
transfer the EPS file to another
application (for example, Microsoft
Word) and print the document, this file is
actually downloaded to your PostScript
printer. If you do not specify a
PostScript file in this field, you are not
able to create a usable file.3

Four Windows When a font is selected, the Microsoft

Font Name Windows font specified here is used in
the annotation text entry fields, where
text is entered or displayed. If you just
want the standard ERDAS IMAGINE
text font to be used, use the word
“default” If you want the font that you are
adding to be displayed in the text entry
fields, use the same name here that you
used for the font file name (Field
Number Two).

Five Font This is the only field that must not be in

Language quotes. It is the flag that indicates
Flag whether the language for which this font
is used is written left-to-right or right-to-
left. If the language is written left-to-
right, use LEFT_TO_RIGHT for this
field. If the language is written right-to-
left, use RIGHT_TO_LEFT for this field.

72 Create an .fdb File

 Table 1: Font Fields (Continued)

Field Number Field Name Font Information1

Six Sample This is the string that you want to use for
String the text style sample in the Text Style
Chooser. For English, something like
“AaBbCc” or Abc123” is commonly
used, but you may wish to use some
other string, particularly for other
alphabets.

Seven Font Server This is the name of the font server to be

Name used to read the font. Use “MSW” for
this field.

1 This information is not an actual description of the fields in the .fdb, files, but instruc-
tions on where to find the information for the True Type fonts you are adding.

2 Weight attributes that are recognized in the Text Style Chooser are “Extra-Bold,”
“SemiBold,” “Bold,” “Heavy,” “Medium,” “Light” and “Thin;” the only slant attribute that is
recognized is “Italic.”

3 This file must be in the <IMAGINE_HOME>/etc/fonts directory. If you do not have a

downloadable ASCII PostScript font file for this font, use the word “none.”

Example .fdb Entries

Below is an example of an entry in an .fdb file for a font that uses a legacy
ERDAS IMAGINE font in the text entry fields.
"Galaxy"
"galaxy.otl"
"galaxy.ps"
"default"
LEFT_TO_RIGHT
"AaBbCc"
"OTL"

Below is an example of an entry for a TrueType font.

"Arial Bold"
"Arial Bold"
"Arialbd.ps"
"Arialbd.ttf"
LEFT_TO_RIGHT
"AaBbCc"
"MSW"

Example .fdb Entries 73

 Below is an example of an entry for a font for which there is no downloadable
PostScript file. This example uses the same font for the text entry fields as for
the annotation itself.
"Suu kyi"
"Suu kyi"
"none"
"Suu kyi"
LEFT_TO_RIGHT
"AaBbCc"
"MSW"

See <IMAGINE_HOME>/etc/fonts/fontlist.fdb for other examples.

Font to Symbol Utility

ERDAS IMAGINE contains a dialog for converting font sets into Symbol
Libraries for use in Annotation layers. Click File button > Configuration >
Font to Symbol.

1. To create a new symbol library, click on a font in the Font list. The CellArray
displays the characters and Symbol Names.
2. Select a row by clicking on the Row number.
3. Rename the Symbol by clicking on the symbol name.
4. If you change the symbol name, you will need to rename the Symbol
Library Category by left clicking in the Symbol Library Category field and
typing in a new name.
5. Click Apply.

The Symbol Library has been created. It references the font set on your system
and is ready to use in Annotation layers.

74 Font to Symbol Utility

 This dialog references the fonts listed on your computer. If you remove
that font, the symbol library will be lost.

If you want to transfer the symbol library, you must also include the
referenced font set.

Adding Thai Font Support to Microsoft Windows

To display and edit Thai characters on annotation layers converted from vector
attributes, the following steps are required for setting the language
environment and adding font support.

You must have Administrator priviledges on your machine before you can
install or change Language Support facilities.

The following instructions are for Microsoft Windows XP.

1. Follow the instructions in Create an .fdb File (page 71) to add True Type
system fonts to the ERDAS IMAGINE annotation package.

We recommend the Arial Unicode MS Font Database file (FDB) for use in
IMAGINE Annotation since it has a complete set of Unicode characters.
The content of ArialUnicodeMS.fdb should look like this:

version 3
"Arial Unicode MS"
"Arial Unicode MS"
"none"
"Arial Unicode MS"
LEFT_TO_RIGHT
"AaBbCc"
"MSW"

2. Install Thai language support and Windows IMEs (Input Method Editors).
For more information about IMEs, see Microsoft Global Input Method
Editors website.

To install language support, select Start > Control Panel and select Regional
and Language Options from the control panel.

Adding Thai Font Support to Microsoft Windows 75

 On the Languages tab, ensure that the checkbox Install files for complex
script and right-to-left languages (including Thai) is checked.

Click the Apply button. Reboot the computer when requested.

To install the Thai language, select Start > Control Panel and select Regional
and Language Options from the control panel.

76 Adding Thai Font Support to Microsoft Windows

 On the Advanced tab, under Language for non-Unicode programs, select
Thai then click Apply and OK. You may use existing files if they are already
installed. Reboot the computer when requested.

Select Start > Control Panel and select Regional and Language Options
from the control panel. Verify the addition of Thai font support to the Microsoft
Windows OS by observing that the Install files for complex script...
checkbox on the Languages tab is disabled (greyed out).

To install the IME, click the Details button on the Languages tab. The Text
Services and Input Languages dialog opens. On this dialog, click the Add
button.

Adding Thai Font Support to Microsoft Windows 77

 Choose Thai from the Input Language dropdown list, then click OK.

Click OK on the Regional and Language Options dialog. You may need to
reboot the system once you have done this.

78 Adding Thai Font Support to Microsoft Windows

 3. Now you may start IMAGINE and open a shapefile containing Thai
characters. Then open the Vector Attribute to Annotation dialog to convert
vector attribute to annotation in Thai font.
4. By selecting the Thai IME, you may type Thai characters into the
annotation layer.

Each time you switch languages, your computer must be rebooted before
the change takes place.

Adding Thai Font Support to Microsoft Windows 79

80 Adding Thai Font Support to Microsoft Windows
 Configuring IMAGINE VirtualGIS
This chapter includes these topics:

• Stereo Configuration for Windows Systems

• ERDAS IMAGINE Preference Settings

Stereo Configuration for Windows Systems

Stereo-In-A-Window system requirements are subject to late
changes. See the Release Notes or visit our website at
http://geospatial.intergraph.com > specific Product > Product
Literature for the latest System Requirements.

A stereo graphics emitter, an emitter cable, liquid crystal glasses, and a stereo-
capable graphics card are required to use the Stereo-In-A-Window option.

Most stereo-capable graphics cards provide a control panel for enabling and
disabling stereo display (see your graphics card’s instructions). The card must
be stereo-enabled before starting IMAGINE VirtualGIS.

Contact StereoGraphics (http://www.StereoGraphics.com) for the specific

cable needed to work with your system and graphics card.

ERDAS IMAGINE Preference Settings

Several ERDAS IMAGINE preferences can be modified to improve the
performance of IMAGINE VirtualGIS. These changes may affect other
applications running within the ERDAS IMAGINE environment.

ERDAS IMAGINE Image Files (Native)

The Memory Map File Size Limit and Memory Map Segment Height
preferences should both be set to 0.000. This disables memory mapping.
Some Virtual Worlds built in the Virtual World Editor could be greater than the
defaults displayed.

Configuring IMAGINE VirtualGIS 81

Configuring IMAGINE VirtualGIS 81

82 ERDAS IMAGINE Image Files (Native)
 Index I
Install ERDAS software 9
Install Manager 19
Symbols
.fdb entries 73
.fdb file, create 71 L
Licensing 6

A
Administrator Privileges 3 M
ArcGIS geodatabase support 15 Memory settings 48
ArcObjects 15

N
C No Pre-rasterize 49
Color control 56
Color Correction Wizard 56
Condor 21
condor_q Condor job status 38
P
condor_q -run Condor current jobs Print scaling factor preference 48
running 38 Printing
condor_status Condor machines status 38 data lost 47
Configuring IMAGINE VirtualGIS for nothing prints 47
Windows 81 out of memory 47
preferences 48
Pre-rasterize 63
scenarios 49
E spool RAW data 49
ERDAS File Association Manager 11 troubleshooting 47
ERDAS Foundation 1, 5
ERDAS IMAGINE and GeoMedia 6.x
compatibility 2
example data vii
R
Rasterize before printing 47

F
File Association Manager 11
S
Foundation, ERDAS 1, 5 sample data vii
Stereo configuration for Windows systems 81
Stereo-In-A-Window 81
Strip height preference 48
G System requirements 1
Geodatabase Support 15

T
H Temporary File Location 3
High Throughput Computing 21

U
uninstalling 19

Index 83
84 Index