9 1 release notes

1

Release Notes

ERDAS IMAGINE® V9.1

Leica Photogrammetry Suite ® V9.1

Microsoft Windows XP (32 and 64-bit editions) and 2000

Sun Solaris 10

Introduction This document provides important information about ERDAS IMAGINE V9.1 and Leica Photogrammetry Suite V9.1.

• Essential updates to installation and configuration instructions

• Facts to know, workarounds, helpful hints, and last-minute information we could not include in the documentation

The Installation/Configuration section that follows contains important updated information that is crucial to the successful installation and operation of your software. Please read this section before trying to install or run ERDAS IMAGINE or Leica Photogrammetry Suite.

See the ERDAS IMAGINE Windows Configuration Guide or the ERDAS IMAGINE UNIX Configuration Guide for complete installation and configuration instructions. Do NOT attempt to install ERDAS IMAGINE or Leica Photogrammetry Suite without reading this manual.

More Information For more information regarding ERDAS IMAGINE and Leica Photogrammetry Suite, see the Leica Geosystems Goegraphic Imaging web site at http://gi.leica-geosystems.com.

Release Notes

ERDAS IMAGINE & Leica Photogrammetry Suite V9.12

ERDAS IMAGINE Hardware Requirements for Microsoft Windows

Computer/Processor Intel Pentium 4 or higher, or any 100% compatible computer

Memory 1 GB or higher strongly recommended

Display Super VGA 1024 X 768 X 32 or higher

DirectX 9 or higher

Disk Space 4.5 GB (includes ERDAS IMAGINE 9.1, Geodatabase Support, IMAGINE Example Data, and Global Elevation Data)

Operating System Windows XP Professional SP2 or higher

Windows 2000 Professional SP4 or higher

Windows Server 2003 SP1 or higher (only supported for License Manager)

Windows XP Professional x64 Edition SP1 or higher (requires Intel EM64T or AMD64 processor)

Media Reader CD-ROM drive for software

DVD-ROM drive for example data and print-quality documents

Software OpenGL 1.1 or higher (for IMAGINE VirtualGIS® and Image Drape utility)*

Adobe Acrobat Reader 5.0 or higher (for online documentation)

Microsoft Developer Visual Studio .NET 2003 (required for IMAGINE Developers’ Toolkit)

Internet Explorer 6 or higher using Java 1.4 or higher runtime

Display Devices The ERDAS IMAGINE drape utility, IMAGINE VirtualGIS and Leica Stereo Analyst™ require OpenGL. Microsoft Windows provides a generic OpenGL driver for supported graphics cards. However, an OpenGL optimized graphics card and driver are recommended for these applications.

Peripherals One Microsoft Windows compatible mouse (Intellimouse recommended)

Software security requires one of the following:

o Ethernet card with TCP/IP configured (if not using hardware key), or

o One Centronics parallel port, or

o One USB port

Hardcopy Devices Microsoft Windows supported hardcopy devices. **

ERDAS IMAGINE Hardware Requirements for Microsoft Windows

3Release Notes

* Microsoft Windows provides a generic OpenGL driver for all supported graphics cards, however, an OpenGL optimized graphics card and driver are recommended for these applications.

** HP-RTL drivers are recommended. If printing from a Windows x64 operating system the print server will require a 64-bit print driver.

ArcGIS Interoperability ERDAS IMAGINE 9.1 can be installed on the same computers as ArcGIS versions 8.3, 9.0, 9.1 or 9.2 Pre-release and will not cause conflicts with these versions. ArcGIS 9.2 had not been released at the time of releasing ERDAS IMAGINE 9.1 and consequently it cannot be guaranteed to work, but testing with the Pre-release indicates good potential. Please refer to the LPS System Specifications for limitations which might occur between installations of LPS 9.1 and ArcGIS.

Geodatabase Support There are two methods for providing Geodatabase support in ERDAS IMAGINE 9.1. Both will only provide support to geodatabases of version 9.1 or earlier. ESRI Geodatabases versioned 9.2 cannot be read at this time.

Install (and license) a copy of ArcGIS (V9.0 or 9.1 only), or

Install the IMAGINE Geodatabase Support CD (requires no additional licensing of ArcGIS)

Release Notes


ERDAS IMAGINE Hardware Requirements for UNIX

* Required to run IMAGINE VirtualGIS.

** HP-RTL drivers are recommended. If printing from a Windows x64 operating system the print server will require a 64-bit print driver.

Computer/Processor Sun SPARC workstation

Memory 512 MB. 1GB strongly recommended

Display Any Sun compliant card

Minimum resolution 800 x 600 x 24bit colors

Swap Space 500 MB

Operating System Sun Solaris 10

Media Reader CD-ROM drive

Software OpenGL 1.2.1 or higher (for IMAGINE VirtualGIS and Image Drape utility)

Sun Studio 10 C and C++ Compiler (for IMAGINE Developers Toolkit)

Mozilla 1.7 or higher (bundled with Solaris, required for online help)

Adobe Acrobat Reader 5.0 or higher (for online print-ready documentation)

Display Devices 8-bit

Sun Standard CG3

Sun Standard Turbo GX and Turbo GX+

Sun SX

24-bit

Sun Standard GS with three Sbus slots

Sun CREATOR 3D*

Sun ELITE 3D*

Sun Expert 3D*

Hardcopy Devices ERDAS IMAGINE supports PostScript Level II and HP-RTL output.

Any device that supports these languages should work with ERDAS IMAGINE.**

Leica Photogrammetry Suite Hardware Requirements

5Release Notes

Leica Photogrammetry Suite Hardware Requirements

Computer/Processor Intel Pentium 4 or higher, or any 100% compatible computer. Dual processors will improve performance.

Memory 1 GB or higher strongly recommended.

Disk Space Consider a large amount of disk space for large projects and a lot of imagery. SCSI disks are generally faster than IDE.

Operating System Windows XP Professional SP2

Windows 2000 Professional SP4 or higher

Windows XP Professional x64 Edition SP1 or higher (requires Intel EM64T or AMD64 processor)

Media Reader CD-ROM drive for software

DVD-ROM drive for example data and print-quality documents

Display Dell 21” P1130 or equivalent

Adobe Acrobat Reader 5.0 or higher (for online documentation)

Internet Explorer 6 or higher using Java 1.4 or higher runtime

Peripherals For advanced data collection select from the following hand controllers:

o Topomouse™

o Immersion 3D Mouse

o Mouse-trak

o Stealth 3D (Immersion)

o EK2000 Hand Wheels

For 3D stereo viewing, select from the following active or passive stereo viewing hardware:

o REAL D (formerly Stereographics) CrystalEyes

o REAL D Monitor ZScreen

o NOTE: PLANAR SD Stereo/3D Monitors have not been officially tested but are reported to work.

Graphics Cards Stereo-enabled graphics cards are needed to view three-dimensional stereo. Note that each card as specific AGP port requirements, and that all cards do not work in all computers. Verify that the card you select is compatible with your computer.

Release Notes


These requirements are subject to change. Please visit our web site at http://gi.leica-geosystems.com for the latest specifications.

ArcGIS Interoperability LPS 9.1 can be installed on the same computers as ArcGIS versions 8.3, 9.0, 9.1 or 9.2 Pre-release and will not cause conflicts with these versions. ArcGIS 9.2 has not been released at the time of release of LPS 9.1 and consequently it cannot be guaranteed to work, but testing with the Pre-release indicates good potential.

Graphics cards tested for stereo viewing:

NVIDIA Quadro FX 4500 (recommended)

NVIDIA Quadro FX 3450/4000

NVIDIA Quadro FX 3500

3Dlabs Wildcat 4 7110

3Dlabs Wildcat III 6110

3Dlabs Wildcat II 5110

ERDAS IMAGINE Release Notes

7Release Notes

ERDAS IMAGINERelease Notes

AutoSync 1• If the resampling output of a raw input image (image which does not have projection associated with it) is not good (for instance, displaying the output file in an IMAGINE Viewer, the result does not look correct), you can fix the problem by manually specifying appropriate pixel size in the Resample Settings dialog box.

2• Sometimes if you select all the tie points in the workstation, IMAGINE AutoSync may become unresponsive. To avoid this, do not select a large number of points (> 1000) simultaneously.

3• When edge matching images, if the edges of the overlapping area do not match well, select the Linear Rubber Sheeting refinement method in the Edge Match Strategy tab. Then use the Create GCP tool in the workstation to collect manual tie points in those areas.

4• Although a second-order polynomial model can be created using as few as six points, and a third-order polynomial model with as few as ten points, such models may terminate the workstation abnormally (especially when the images being matched are very dissimilar in size). If this occurs, reduce the Maximum Polynomial Order or increase the number of points used to solve the model.

5• In the Contrast Adjustment dialog, the Apply to AOI and Apply to Image File options are not supported by IMAGINE AutoSync. To use these options, load the image into an IMAGINE Viewer.

6• Sometimes APM does not generate tie points close to the edges of images, even when you set the Starting Column and Starting Line to 1 in the APM Strategy tab. If you need tie points around the edges (for example, if you are using the Linear Rubber Sheeting model), use the Create GCP tool in the workstation to collect manual tie points close to the edges.

7• If an Unknown function: Unknown exception thrown error displays while attempting to run APM on two images with a large overlapping area, and no tie points are found, increase the numbers in the Column Increment and Line Increment fields on the APM Strategy tab and run APM again.

8• If the resolution between two images is too different (for example, 1 meter to 28 meters), and the overlapping area is small, APM may not find enough tie points, or the tie points may be incorrect.

9• If the overlapping area between two images is small (less than 2000 x 2000 pixels), APM may not find enough tie points (or any tie points) using the default APM parameters. If this occurs, decrease the numbers in the Column Increment and Line Increment fields on the APM Strategy tab. If using the defaults, lower them from 256 to 128. You can also decrease the number in the Starting Line and Starting Column fields to 64 or lower. Then run APM again.

Release Notes


10• Some TIFF imagery contain tags that cause them to appear to have proper georeferencing information. To ignore this information when processing the imagery in IMAGINE AutoSync, turn off the Georeferencing fallbacks preference within the TIFF Image Files preferences. IMAGINE AutoSync will then treat the images as raw imagery.

11• In the Georeference workflow, when you select the Clip to Reference Image Boundary option in the Resample Settings dialog, the output extents produced may be larger than the reference image extents if the input and output images are in different projections.

12• IMAGINE AutoSync requires the first pyramid layer (layer 1) of an image. You must set the Image Files (General)/Initial Pyramid Layer Number preference in the IMAGINE preferences to 1 in order to generate pyramid layers that IMAGINE AutoSync can use. If no pyramid layers are present, or if the existing pyramid layers are not usable, IMAGINE AutoSync will delete the existing pyramid layers and generate new pyramid layers to perform APM.

13• If a message dialog displays while running APM in the IMAGINE AutoSync Workstation, sometimes clicking the left mouse button or the OK button does not close the dialog. If this occurs, press the space bar on the keyboard instead.

14• In the workstation, if you preview the output image and change the band combination, the output image may be distorted. In this case, when you change the band combination in the Preview Output view, IMAGINE AutoSync displays the images using their original geometric models. If this occurs, calibrate/resample the input images, view the output in the View Output view, and change the band combination there.

15• In the workstation, if you click the Set Same Scale button on the toolbar, and some of the viewers display black panels, it is usually because the images have different scales. To manually zoom or change the panels to have similar scales, right-click on a black panel and select Default Zoom from the menu.

16• In the edge matching workflow, if you are using the Linear or Non- Linear Rubber Sheeting model with Apply Refinement to Whole Image, and sections of the output image are cut off, turn off the GCP Editor/Rectify Outside Convex Hull preference in the GCPs preferences.

17• While adding image files to an input list, make sure that the same file is not added multiple times.

18• If the two images to-be-autosynced have the same projection, but different pixel size units (feet vs. meter, for instance), you need to reproject one of them to make it have the same unit as the other. You can use the IMAGINE Reproject Images tool to do that.

19• In the Projection tab, the Same as Input Image option is available even if none of the input images have projection information.


9Release Notes

20• When specifying the Cell Size in the Resample Settings tab, ensure that the cell size is appropriate for the selected projection and input image resolution.

Data Import/Export 21• Calibrated images in UTM lose precision after being exported to NITF. ERDAS IMAGINE uses the NITF IGEOLO field to persist the geographic position of the image, This field is only accurate to one arc second. Images should be reprojected to geographic prior to export if a higher degree of accuracy is required.

UNIX ONLY 22• When selecting an input file (.THF) in a file chooser for ADRG importer you may see a message "THF and other non - img files not supported (yet)". In this case just use ADRG (direct-read) for import instead.

Fourier 23• When performing a Fast Fourier Transform on an image bigger than 2 GB, the temporary files could be left behind without being deleted. Please delete it manually.

GIS Analysis 24• The Matrix function has a 63 character limit on filenames for input files when creating attribute names. If your filename is more than 63 characters you just need to rename it.

GLT_Viewer 25• The NITF standard defines a native subsampled (pyramid) layer format, `rset`. ERDAS IMAGINE currently produces subsample (pyramid) layers for all file types in `rrd` format only. ERDAS IMAGINE will work correctly with either rset-formatted or rrd-formatted pyramid layers for NITF files. If you want to exchange your NITF files with other systems, however, you should always provide your pyramid layers in `rset` format.

There is a mechanism built into the NITF libraries to automatically create `rset` pyramids upon opening the image. To turn this feature on, set Preferences -> NITF -> RSET Generation to "Always".

Even with this preference set, the Viewer may prompt you to create pyramid layers. You can turn off this prompt by setting Preferences - > Viewer -> Compute Pyramids Layers Upon Image Open to "No".

If rrd-formatted layers already exist, the NITF library will recognize these layers as subsample layers (even though they are in `rrd` format) and it will not automatically create the rset-formatted layers. If you have rrd-formatted layers, you must delete them before `rset` layers can be created. Go to the directory with your image and delete the file with the same base name as your image, but with a ".rrd" extension. For instance, if your image is named "colors.ntf", delete the subsample layer file "colors.rrd".

26• If you wish to change the zoom in a Viewer pane that is currently roaming, be sure to pause the roaming first. If the motion is not paused before you change the zoom, the roaming direction may change or stop.

Release Notes


IEE 27• On some computers, the IEE Web Client does not initialize after selecting themes. First check whether the computer has a Java Virtual Machine (JVM). On the Internet Explorer Tools menu, open Internet Options. Under the Advanced tab, look for a group labeled Java. If this group doesn`t exist, please install Java JRE 1.4.1.

If this doesn`t resolve the issue, check Path environment variable by opening the System properties from the Control Panel. Under the Advanced tab, click the Environment Variables button. Find the Path variable in the system variables. If you examine the path and find a reference to a version of Java that is different from the version used by the browser, replace it with the location of the proper version of Java.

If this does not resolve the issue, Java has been set up in a way that conflicts with the IEE Web Client. Uninstall the current version of Java and install Java JRE 1.4.1.

28• When opening an IEE layer, features will not extract to the current viewer extents. Use the inquire cursor to get the coordinates of the viewer extent before creating a new IEE layer. These coordinates can be specified in the IEE creation dialog.

29• When zooming in close to a small area the text symbology may become unreadable on certain sets of data when the map extents set in the database cover the entire world or a similarly large area. If this becomes an issue, you can have your DBA manually adjust the map extents of the dataset to a smaller area, such as a state or country.

30• The Oracle Map Definition tool provided with IEE is a product of Oracle, and is not supported by either Oracle or Leica Geosystems.

All IEE Viewer-based and Web clients must be restarted after using the Oracle Map Definition tool to make changes to styles, themes, or maps.

31• When creating a new IEE layer, once you have connected to the database you will be unable to connect again if you go back to the login screen. In this case, you must cancel out of the layer creation dialog and create a new IEE layer.

32• In IEE, the zoom and pan tools will not show the correct icon until it has been used once. An easy way to keep track is to remember to change back to the selection tool when you are done using a zoom or pan tool, instead of leaving it in whatever mode you were just in.

33• If a Feature Query string in a theme is too long, you will receive the error "String index out of range: -1" when you try to edit it. The theme will display correctly but you will not be able to edit it. In order to edit the theme, the query string must be shortened.

34• The AOI tools are incompatible with IEE layers, and will not function properly when an IEE layer is open in the same Viewer.


11Release Notes

35• While using the IMAGINE Enterprise Editor, some windows such as Theme Control may lose focus and disappear behind the viewer window, and are not visible on the Windows taskbar. To retrieve these windows, you must either use Alt-Tab to change the focus, or minimize and/or move the other windows. If a new window is opened and does not display, you must retrieve the windows and close them. If entering information in a window causes exceptions to be reported in the session log, you must retrieve and close all of that kind of window and open a new one to continue data entry.

JPEG_2000_X 36• To improve performance (mostly speed) for JPEG2000 exporter the default exporter dialog box setting should be changed to the following:

Tile Size: Whole Image Progression Order: PCRL Number of Decomposition Levels: 6 Number of quality layers: 20 Lossless: NO

Map Composer 37• This release note is intended for users of the print feature and the Map Composer feature of ERDAS IMAGINE. Recent changes in behavior of these features may cause problems when printing older maps generated using Map Composer.

In printing some maps generated using versions of Map Composer older than 9.0 or printing some multi-layered image stacks from within the ERDAS IMAGINE Viewer, lower-layer images may not print. These images may seem to have simply disappeared in the printed output.

Should this behavior occur, the "Background Transparent" setting of the higher image layers should be checked. Layers with "Background Transparent" not set will block out images below them, making it appear as if the images below have disappeared.

In IMAGINE 8.7.2 and earlier, regardless of this setting, the background raster images would show through in printed output. This was a result of ERDAS IMAGINE implicitly assuming a transparent background for each layer. Beginning with ERDAS IMAGINE 9.0, this behavior has been fixed. Now, only raster images with the Background Transparent option set will allow image layers below to be visible.

Should some unlikely set of circumstances continue to present transparency-related problems in multi-layer image stacks, it should be remembered that images may always be merged into a single layer using the Mosaic feature of ERDAS IMAGINE.

38• When creating a Map composition using multiple calibrated images, you must either:

a) load each image separately ensuring that the first image is loaded with Orient Image to Map System checked in the File Selector, or

b) set your Orient Image To Map System preference to "Yes" in the Viewer category of the Preference Editor

Release Notes


64-BIT WINDOWS ONLY 39• To be able to print from Map Composer you will need 64-bit print drivers. If your printer is a network device served from a print server you may require your IT department to update the drivers on the print server.

Mosaic 40• When loading the L2 images into the Mosaic tool, you must check the Compute Active Area option in the Image Area Options tab of the Add Images window. Otherwise, the L2 images will not be laid out correctly.

If only a small portion of the image contains image data (i.e., is not background values), clicking the Set... button and selecting the Edge radio button as the Boundary Search Type may save a lot of computation time.

41• Color correction settings files for images with spaces in the file name cannot be loaded by Mosaic. You may open the .txt file in a text editor and add double quotation marks around the image name to allow the file to be used (e.g. "image name.ext").

42• The Color Correction Exclusion Area file in Mosaic Direct and Mosaic Wizard may only be an AOI file.

43• If you are intending to reuse .mos file for presetting options for feathering in Mosaic Direct you will need to confirm these settings for Feathering with "return" in Mosaic Direct `Intersections` tab.

44• When mosaicking big images (for example, 500 MB each), avoid using Compute Active Area by Edge to specify the valid image regions since this will make everything (compute active area, dodging, color balancing, histogram matching, mosaicking, and so on) slow. Instead, use Compute Active Area by Corner (and Crop Area, if needed).

Online Help 45• The help buttons in some of the Advanced Hyperspectral dialogs do not connect to any help page. Use the Help Button on the main "Hyperspectral Tools" menu and navigate further to the specific help associated with the required tool.

46• The index for the on-line help system is displayed with atypical indentation. The primary words are indented one level while secondary words are not indented. When browsing the index alphabetically, please remember to use the indented column of words.

64-BIT WINDOWS ONLY 47• If you use 64-bit Internet Explorer, all HTML files will display correctly but the Java-based functionalities of the Online Help (such as Search) won`t work.

To be able to correctly use the ERDAS IMAGINE Online Help, you must install the Windows 32-bit version of JRE1.5 update 6. This is available from the following location:

http://java.sun.com/j2se/1.5.0/download.jsp

You must also use a 32-bit version of Internet Explorer, which works fine with IMAGINE`s Online Help and the JRE.


13Release Notes

Oracle Raster

UNIX ONLY 48• Currently you cannot export directly JPEG2000 files into Oracle Spacial GeoRaster on Unix. Please use different file type.

49• If using a polygon to select images using the Oracle GeoRaster spatial selection tool in the file chooser, the selected images are the ones which intersect the minimum bounding rectangle of the polygon and not the polygon itself.

Signature Editor 50• The output file chooser from Signature Editor displays incorrect file types when you attempt to specify a classification result file name. To work around this problem, simply type *.img, or *.tiff, or *.stk in the file chooser to get the proper output file extension.

Spatial 51• If you cancel a preview function in Ehlers Fusion, the following error is displayed:

"FileIdentifyAndOpen failed (2:The specified file does not appear to exist) ..."

This happens because Ehlers Fusion contains several internal stages. Each stage prepares a file to be used as input for the next stage. Currently, no stage can detect that its previous stage has been canceled.

Once the process is interrupted, you should close the dialog and start it again.

Spectral Analysis 52• Selecting `Anomaly Detection`, `Target detection`, `Material Mapping`, `Project Wizard` or `Spectral Analysis Workstation` produces some repeated message lines in the session Log. For example, when selecting `Spectral Analysis Workstation` the message could be:

`16/11/05 13:40:46 C:/Program Files/Leica Geosystems/IMAGINE and LPS 9.0/bin/ntx86/imagespectrometry.exe general 16/11/05 13:40:47 imagespectrometry(1532): Redefining existing symbol vertline3! 16/11/05 13:40:48 imagespectrometry(1532): Redefining existing symbol vertline3!`

The behavior does not affect the user workflow.

53• When performing Material Identification task, please make sure that the spectrum range of each record in the chosen material list overlaps with the spectrum range of the analysis image. To do so, drag and drop each record to a Spectrum Plot and check if you can see the graph of it. If you cannot, it means the spectrum range of that record is outside of the spectrum range of the imagery and that record should be removed from the material list before you start running the task.

Stereo Analyst 54• When you delete a Stereo Analyst for ERDAS IMAGINE Feature project, the entire project folder is deleted including the Shapefile. If you wish to retain the Shapefile for other use, you must move or copy it into another folder before deleting the Feature project.

Release Notes


55• When assigning Left, Middle and Right Mouse Buttons for the Immersion Mouse Emulation Mode, it is necessary to hold the mouse button down at the same time that the assign button is pressed on the button mapping dialog. The assignment will not over-write existing command assignment which will continue to be displayed in the button mapping dialog, however when the mouse is toggled to Mouse Emulation Mode, the assigned system mouse buttons will work.

For both Immersion and Topomouse, when exiting ArcGIS, the Left mouse button assignment only will be persisted. Should the Middle and Right mouse button assignments be required, they should be set at the start of the editing session.

Texel Mapper 56• Thumbwheels for Image Options dialog box of Stereo Analyst`s Texel Mapper are disabled even when Enable Editing checkbox is selected. To make it enabled just switch to Perspective Correction Tool and then switch back to Image Options dialog box.

Utilities 57• When you cancel changes to a scheduled batch job, the batch job schedule is deleted. You must re-schedule the job.

64-BIT WINDOWS ONLY 58• Tasks scheduled in batch will not run correctly if you attempt to modify them after scheduling them. The system will display an error message saying that the batch task cannot be saved, and the task will stay in the WAITING state. Instead of editing the task, delete it and reschedule a new one.

Viewer 59• If you are intending to print any non IMG 16-bit image from inside the Viewer or Map Composer you will need to calculate statistic first and then print the image to get correct output.

60• This release note addresses known issues with the Swipe and Flicker tools of ERDAS IMAGINE 9.0 Viewers. When using the Swipe and Flicker tools, the option to use the Auto Mode may be selected to perform the function in question without user interaction. While this mode is enabled, it is possible to roam around the image while the selected operation is taking place. This action may cause the viewer to terminate abnormally.

This crash may be prevented by enabling Virtual Roaming under the View menu of the Viewer in question. Further, should the roaming action be performed while Auto Mode is disabled, no crash will occur.

61• Whenever an image, having no pyramid layers, is opened in the Viewer and zoomed out beyond 1:2 pixel ratio, a message pops up asking whether to draw only the footprint of the image. When you try to click on one of the two options of the message box, it appears as if the message box is not responding. If this happens, click on your desktop and then click on the message box again.

Leica Photogrammetry Suite Release Notes

15Release Notes

62• When using the counter tool in the IMAGINE GLT Viewer, if you have multiple view panes open, clicking "Cancel" on the counter tool`s Save dialog causes the counter tool pane to grow and cover the first image view. Further, it is sometimes not possible to shrink the counter tool pane after this happens.

As a workaround, try the following:

1. Click the "Display One Viewer" button in the GTL toolbar. This will not remove your other image pane(s), but it will hide them.

2. Now the counting tool pane is draggable. Drag it back to a reasonable size. Your first pane should show.

3. Bring back your other pane(s) by clicking the appropriate button in the GLT toolbar (such as "Display Two Viewers").

63• The swipe tool for GLT viewer with multiple layers will freeze if the visibility of more than one layer is turned off. The problem can be avoided by temporarily unloading the extra layers not used in the swiping operation.

64• This release note concerns a rare problem seen when reading SDE Raster files. Occasionally, when opening an SDE Raster file, the following error message error message will appear:

"ArcSDE Error: stream in progress"

When the error message is dismissed, normal operation will resume. This message may be safely ignored.

65• SOCET TIN format files are not generally accessible in IMAGINE. Attempts to access SOCET TIN format files may result in the following:

"SOCET Grid Format is missing necessary pixel file (.dte file)".

and other error messages.

VirtualGIS

UNIX ONLY 66• On the solaris platform, VirtualGIS cloud layers can not offset the texture using the thumbwheels. There currently is no workaround and users must accept the default setting until a fix is released.


FPES 1• Images used in FPES must be in 24 bit RGB or 8 bit Grey for brightness and contrast adjustment using the options on the Image Adjustments palette including the Automatic Dynamic Range Adjustment settings. You may transform images in other formats using IMAGINE.

Release Notes


2• The Preference or Property dialog closes if data input is confirmed using the keyboard Enter key. Data input is lost in most cases. Do not press the Enter key to confirm data input. Use the mouse pointer to select the next field for data input. To leave the dialog, click on either OK, Cancel, or Compute + OK.

3• The message `Out of memory` may be displayed when color settings are made in Graphic Properties if the font size is set to `Large` or `Extra Large`.

To eliminate the problem, open the Control Panel from the Windows START menu. Open the Display Properties dialog and select the Appearance tab. Set the Font size to Normal.

4• The graphic window, property view, or data view may not be updated after computation.

Select Project -> Redraw or click the `Refresh the list` icon to redisplay graphics.

GPro 5• To achieve the best performance, it is recommended that you install the software in the following order:

1. LPS 9.1

2. ORIMA DP for LPS, version 9.1

3. GPro 3.2

6• When loading GPro 3.2 on the Application Server used for High Performance Computing (HPC) you must install it directly to the actual local folder on the hard disk where GPro 3.1 was installed and not to the mapped network drive. Installing GPro 3.2 to the mapped network drive may not successfully update LPS and cause the software to malfunction.

For instance, if you have C:\directory\subdirectory mapped to Q:, you must install GPro 3.2 to C:\directory\subdirectory and not to Q:.

7• When you run the, "Copy To" function, the process will report a failure and none of the project or flight files will be copied to the destination location. The workaround for this is to just copy the files manually and edit the INFO, SUP files to point to the new location.

8• When you run ORIMA triangulation from within GPro and perform the adjustment normally, you can write out the new orientation files. When you then exit ORIMA triangulation, an abnormal termination may occur. At this phase in the processing, the files written by ORIMA are already usable and the use of GPro can continue normally after restarting GPro.

9• If the MM data directory is read only (i.e. in shared directory of other computers), MMControl will not able to add a volume.

10• When using LPS APM through GPro, it is not recommended that you combine strips with over 30% variation in the flying heights into the same block.


17Release Notes

For best performance, strips within an LPS block should all have similar flying heights.

Image Equalizer 11• In GeoTIFF files created by ImageEqualizer, there is missing information for some TAGs such as ModelTiepointTag, GTModelTypeGeoKey, and ProjLinearUnitsGeoKey.

LPS/ArcGIS Interactions

12• If, after the installation of LPS 9.1, you install ArcGIS 9.0 or updates to ArcGIS 9.0, you will need to run the GIO Application Repair Utility in order to restore LPS 9.1 to full operation.

You may encounter similar problems using ArcGIS 8.3 in conjunction with LPS 9.1. This combination is not formally tested or supported, and therefore it is not known what effects (desirable or undesirable) might result from running the GIO Application Repair Utility.

ArcGIS 9.2 ONLY 13• If you install any product related to ArcGIS 9.2 (ArcGIS Desktop, ArcGISEngine, or the Standalone ArcReader) and you do not set up licensing, the Terrain Editor will terminate abnormally when you load a Stereo Pair.

The Terrain Editor will function correctly if you configure a license for ArcGIS Desktop or ArcGISEngine. However if you set up a floating license for Desktop, the Terrain Editor will consume that license, even when you are not running Desktop.

A solution for this problem will be released after the final release of ArcGIS 9.2.

14• Many features of LPS will not work correctly if you install or uninstall ArcGIS (or service packs to ArcGIS) versions 9.0 or earlier. Run "Repair GIO Applications" to restore LPS to full functionality.

ArcGIS 9.0 ONLY 15• It is not possible to display the default world image in ArcGlobe 9.0 with LPS 9.1 installed on the same system, even if you manually run the GIO Application Repair Utility.

A solution to this problem will be published after the release of ArcGIS 9.2. In the interim, you may be able to work around the problem by manually registering the ArcGIS version of RDO.DLL:

1. Run the Windows Explorer and navigate to the ESRI Raster directory. The default location for this directory on some systems is "c:\Program Files\Common Files\ESRI\Raster" 2. Click the Windows Start button and select Run. 3. Type "regsvr32.exe" in the "Open:" field. Be sure to include a space at the end. 4. Drag and drop RDO.DLL from the Raster folder into the "Run" dialog. 5. Select OK in the "Run" dialog.

Note that you may need to repeat this procedure if you uninstall LPS or run the GIO Application Repair Utility.

LPS Automatic Terrain Extraction

16• In order to create accurate DTMs, exterior orientation must be solved correctly. At least two GCPs having X, Y, and Z coordinates and one vertical (Z) GCP are needed to solve the exterior orientation for each block.

Release Notes


17• Automatic Terrain Extraction results could be less than perfect if there are big terrain variations coupled with low flying height, or if there are not many unique features, such as in areas covered by trees and grass. If this happens, you should perform manual DTM editing.

18• The seed points in ATE are loaded into memory during DTM extraction. Therefore, it is not recommended to use large DTM files with millions of points as the source of seed points.

19• To terminate the DTM split or merge process before completion, user should use ERDAS IMAGINE task panel, select "Session\Active Process List...", highlight "dtmsplitprocess" (for split) or "dtmmergeprocess" (for merge) in the dialog, and then click "kill" button.

20• To generate DTM report, the accuracy of resulting DTM needs to be checked using check/control/tie points, which requires the DTM points be built into a TerraModel TIN. However, if the number of DTM points is over 8 million, such a TIN can not be built, so the DTM report won`t be generated.

21• When using a mapsheet to split a DTM, the input DTM and the output DTM must not be in LSR projection.

22• Automatic Terrain Extraction (ATE) uses area-based point matching. If image contrast is very poor, the calculated correlation coefficient will be low and the point matching results will not be reliable. To avoid this problem, make sure that you choose bands with greater contrast. You can either look at the image histogram to identify the image with better contrast, or increase the contrast of the image by stretching the image (with Histogram Equalization in IMAGINE Image Interpreter) before running ATE.

23• Generating a DTM from a block with the same name as an existing DTM, but with a different extent will not update the graphic display extent of the DTM. To update remove the DTM from the block, save the block and add the DTM back to the block

24• If an excluded area defined by an AOI with a known elevation is located at image boundary and thus connected to background area, the "default" background value will replace the given elevation.

To avoid this abnormal behavior, the background value should be set as a fixed value instead of "default".

25• DTMs generated in SS TIN format in geographic coordinates must be in Radian units.

LPS Project Manager 26• The mouse pointer does not switch back from the hourglass style to a normal cursor when the export of a project to FPES/FCMS is finished. This ‘stuck’ cursor can also be seen in otther applications that employ the Viewplex. This is usually the case if the cursor is moved into the graphic window (Viewplex) while a process is running. Move the mouse pointer out of the graphic window to switch the cursor back to normal style.


19Release Notes

27• The preference "Resampling Method for DEM" originally located in the category "LPS" has been moved to the category "Raster Processing" so that both LPS and IMAGINE users can access it.

64-BIT WINDOWS ONLY 28• In order to install LPS 9.x on Windows XP64, it is necessary for you to install the .NET 1.1 Framework (including Service Pack 1) from Microsoft.

29• If you have installed the ADS40 data on a path different from the default directory, you will not be able to open the SUP file in a viewer for viewing or attach it to a block file. You will get the one or all of the following error messages:

The session log will also show any/all of the following error messages

ERROR: #136 from RasterFileHandle::FileLayerNamesGet ERROR: Error gettting layer names ERROR: #2945 from eimg_LayerGetNames ERROR: eimg_LayerGetNames failed ERROR: #8675 from FileOpen ERROR: FileOpen failed ERROR: FileIdentifyAndOpen failed (2:The specified file

does not appear to exist) for o:/ADS/v_Project/images/S-8b-L10951RGBF16A.ads

ERROR: #1706 from eflt_DefaultGetLayerInfo ERROR: Error return from eimg_LayerGetNames ERROR: FileLayerNamesGet failed for C:/Program

Files/Leica Geosystems/IMAGINE and LPS 9.0/examples/ads/v_project/S-8b- L10951RGBF16A.sup

ERROR: #146 from GetFileSensorTypeName ERROR: GetFileSensorTypeName failed

The cause of this error is the path to the data location in the .SUP files is not a valid path. If you have installed the ADS40 example dataset at a location other than the default location, the data paths in the SUP files must be corrected before using the data.

In order to correct the data paths in .SUP files, open the .SUP files located in the <LPS_DATA_INSTALL_FOLDER>\ADS\v_Project folder, in a text editor and edit the path to the following entries:

IMAGE_FILE_NAME ORIGINAL_ORIENTATION ADJUSTED_ORIENTATION ORIGINAL_CALIBRATION LEVEL_0_NAME

For example if you have installed the example to D:\LPS_data\examples and the default path for IMAGE_FILE_NAME is

IMAGE_FILE_NAME 1 "C:\Program Files\Leica Geosystems\IMAGINE and LPS 9.0\Examples\ads\v_project\images\S-8b-L10951RGBF16A.ads"

You would change it to

Release Notes


IMAGE_FILE_NAME 1 "D:\LPS_data\Examples\ads\v_project/images/S-8b- L10951RGBF16A.ads"

After changing the paths you can open the sup file in viewer or attach them to a block file.

30• Some orbital pushbroom data such as ASTER, EROS, and SPOT5 do not have elevation information in their metadata. You should set an Average Elevation in the Block Property Setup dialog so that some reasonable default elevation value displays in the Terrain Editor when GCPs are not available in a block.

MosaicPro 31• We recommend you create ortho images before running MosaicPro. If you have to use DTMs to calibrate the images for mosaicking, it is preferable to use DEMs because large TINs could easily exhaust computer memory.

32• When creating a mosaic based on a block file, please ensure that the block file remains available at the same location. If the block file must be moved, the mosaic project should be recreated.

33• MosaicPro might terminate abnormally when handling very large projects with hundreds or thousands of images because of the memory limitation for a process. If this happens, the workaround is to split the large project into several smaller ones.

34• The Bicubic Spline resampling method cannot be used when mosaicking images from a block file.

35• When replacing images with the "Online" column in the cell array of MosaicPro, the properties of new images such as the file sizes and coordinate systems should be same as the original to ensure the correct workflow.

36• You may encounter several problems loading a block file that has images offline in MosaicPro, unless you specify the correct image names one at a time. To avoid this problem, use the LPS blocktool to re-attach offline images before adding the block file to MosaicPro.

37• To ensure optimal results with MosaicPro, the background areas of the input ortho images should be eliminated through the option "Compute Active Area" with certain crop percentage such as 20%.

38• Seam polygons generated by "Most Nadir Seamline" option sometimes have holes in the raster display and in the final results. When this happens, use "Geometry-based Seamline" or other options to re-generate seam polygons.

39• When a Digital Elevation Model (DTM) is used as the elevation source in LPS MosaicPro, it should not be removed or relocated if the saved mosaic project (MOP file) shall be opened and used again. If the DTM is not a raster, such as TM TIN, LTF or 3D Shape file, the block file should be kept as well.


21Release Notes

ORIMA 40• ORIMA cannot be launched if it is installed in a directory that has spaces in its name. ORIMA should always be installed in a directory with NO spaces in its name.

41• When Write Orientation is performed in ORIMA, the adjusted ODFs (orientation data files) are created and the Viewplex is put into adjusted orientation mode, which means the adjusted orientation and optionally adjusted calibration values are used by the sensor model. A subsequent use of either Move To Ground or Measure Multiple commands will reset the orientations used by the sensor model to original values. This reset is temporary and only valid inside ORIMA. All other applications will use the adjusted orientation values. Therefore, for visual quality control, images must be loaded using the Load Images command from ORIMA or the image loading features of Viewplex. GPro and Terrain Editor can also be used.

42• When using ADS40 projects in ORIMA, be sure that ADS40 images and the accompanying ODF (orientation data) files are in the location specified by the support file. If not, ORIMA may terminate abnormally.

43• When using LPS APM through GPro, it is not recommended that you combine strips with over 30% variation in the flying heights into the same block.

For best performance, strips within an LPS block should all have similar flying heights.

44• When using ADS40 images in automatic point measurement (APM), we suggest the following workflow:

First use the No Transfer, New Points Only option on each sub-block in the block file. Then, use the Transfer Only, No New Points option to transfer points between those sub-blocks. This is the default workflow for GPro, and it is recommended for LPS and ORIMA as well.

The Transfer With New Points option is not supported for ADS40 imagery. Therefore, if a sub-block already has tie points and you choose the Transfer With New Points option instead of the Transfer Only, No New Points option, APM will not execute the operation. If you need to measure control points, do it after APM. If you need point densification, first delete the old points and then run a new APM process.

45• ORIMA performs a case-sensitive comparison of image names present in an LPS Project file (block file) with the image names present in the GPS file. The image names are always lowercase in an LPS Project file. The image names in a GPS file can be mixed case. This causes a mismatch between the images and the GPS IDs and subsequent operations in ORIMA might fail.

The workaround to this is to change the names of all the images in the GPS file to be lowercase.

Release Notes


Ortho Process 46• SOCET SET GRID files cannot be added to the LPS Project Manager Block Project Tree View (which displays Images, Orthos, and DTMs associated with the block file). You can convert the grid files into IMAGINE .img format using the SOCET SET GRID importer and then add the .img to the block file in LPS Project Manager.

47• The Mosaic preference Treat Map Sheet Corners As Pixel Centers is effective only when a Map Series file (.msh file) is used to define the output map area(s). For other methods, such as ASCII Sheet File, Polygon Vector File, the coordinates of the defined corners of the mosaic output image are used to define the center of the corner pixels, instead of the outer boundary of the corner pixels.

PRO600 48• If a large number of MicroStation design file elements are edited in a single operation, then the operation may take more time than expected. This is because in its default configuration, the PROLPS Driver module of PRO600 monitors all design file changes, so that the graphics on the ViewPlex stereo display can be updated accordingly.

Situations where this delay might be encountered include standard fence and selection set operations (e.g. changing element symbology or deleting several elements), as well as tools that import data to the design file (e.g. importing DTM data using PRODTM).

The delay can be avoided by temporarily turning off the online update of the design file graphics on the stereo display, using the "SI Online" checkbox in the PROLPS Driver status window. Once the editing operation is complete, the online update can be re-enabled, and the graphics re-synchronised to the new design file state by selecting "Overlay | Refresh" from the driver status window menus.

Stereo Point Measurement

49• When using unsolved blocks, irrespective of the specified overlap % in Stereo Point Measurement tool, all images will be displayed in the image list cellarray on the Image Selection tab. This behavior may be avoided by setting the status of the initial exterior orientation parameters to "Fixed" in the Frame Editor.

Terrain Editor 50• Turning off pyramid display can slow down the rendering process of DTMs in TerrainEditor. This can also cause Terrain Editor to freeze or terminate unexpectedly if large DTMs are loaded and the view is zoomed out to an extent to display a large number of points (the process runs out of memory at this point). The current solution is to set up an upper limit of 100,000 points: if points on screen are less than this number, the user is free to turn the pyramid display on or off; if points on screen are more than this number, the pyramid display will be automatically turned on.

51• To add breaklines to a DTM with highly densified points in TE, some breaklines may go wrong and cannot be imported. The user will be warned with the number of breaklines not imported.

The workaround is to merge the DTM and breaklines in "DTM Split/Merge Tool" before loading to TE.


23Release Notes

52• You may use image pair criteria to set up the display of image pairs. The settings from one block file affect all block files opened thereafter. If no image pairs display in Terrain Editor for a certain block file, you may reduce image pair overlap percentage to display image pairs from Terrain Editor by selecting Edit -> Settings - > Image Pair Criteria.

If Ignore Disabled Items is checked, inactive images are not considered for image pairing. For a large block file with numerous images, enable Suppress Image Pair Calculation to speed up display.

53• Contours of DTMs may sometimes appear to intersect. The reason for the intersection is because the Z values of some points are incorrect. Applying the Remove Spike operator removes the problematic points.

54• In rare cases, When launching Terrain editor, a message dialog will come up with the message "unable to initialize viewer" or "Moniker can not open file". Dismiss the dialog and re launch Terrian Editor

55• For LTF and Raster DTMs, the select all points, selects points that are in the view extent only. To select all points in the DTM, zoom out to view the full extent of the DTM.

56• Contours of DTMs displayed at pyramid layer is based on the points in the pyramid layer, not on the actual points, and may not be exactly the same as the one from the actual points. To view actual contours, zoom in until the DTM is displayed in full resolution. A more accurate thinning-based method will be developed as a post-release fix.

57• Calculating intersections and evaluating overlap between all possible pairs of images for blocks containing many (more than 75 or so) active images can be slow. GPro and ORIMA do not make use of the image pairs calculated as a block project is opened, so the GPro installer sets the default project option to bypass image pair calculation. If you want to see the full list of feasible image pairs while running Terrain Editor on a system which also has GPro installed, and are willing to incur the slower project opening cost, you can restore the original LPS preference setting by editing the ASCII text file Project.pdf found in the <LPS_HOME>/defaults folder.

Open Projects.pdf in any text editor, find the following:

build_pair_refs("Build pairs"): "false"

and replace "false" with "true" to see the full list of feasible image pairs.

58• The seed points written to the output DTMs are not clipped to the DTM extent. Use LPS TE to delete those unwanted points.

59• If there are duplicate breaklines in your DTM file, delete selected breaklines operation deletes only one of the duplicates. You will have to select the undeleted breaklines and apply the delete operator again.

Release Notes


60• When working with LTF or raster DTMs, TE sometimes does not refresh properly. If this happens, use the refresh button on the TE tool bar.

61• TE may not respond when zooming out 64 times or more in tri-view mode for very large LTF or raster DTMs. There are ways to reduce the chance of stalls: 1) Use a display layout other than tri-view; 2) USe a smaller point threshold for pyramid display in "Terrain Display Settings".

Copyright © 2006 Leica Geosystems Geospatial Imaging. All rights reserved. ERDAS IMAGINE, IMAGINE VirtualGIS and Stereo Analyst are registered trademarks; IMAGINE Geospatial Light Table and IMAGINE GLT are trademarks. SOCET SET is a registered trademark of BAE SYSTEMS Mission Solutions. Other brand and product names are the properties of their respective owners.

9 1 release notes

Documents