ENVI 5 Service Pack 2 Release Notes

 Revised 18 January 2013

• New Features
• Known Issues
• Problems Fixed

Change request ID numbers are included where applicable to allow us to respond to inquiries more easily.

New Features

• A new Radiometric Calibration tool calibrates image data to spectral radiance, top-of-atmosphere reflectance, or at-sensor brightness temperatures by reading the relevant metadata from the satellite vendor. Calibration options vary by sensor. This tool replaces the Calibrate Landsat, Calibrate WorldView, and Calibrate QuickBird tools; those have been removed from the Toolbox. The Radiometric Calibration tool also provides an option to create a radiance image that can be directly imported into the FLAASH atmospheric correction tool.
• You can interface directly with the Mensuration Services Program (MSP) toolkit with an ENVI plug-in, which is only available through U.S. government channels.
• If you open an OGC WMS raster layer that contains a legend, the legend displays in the Layer Manager. This is available only on Windows operating systems. To create an annotation object from the legend that you can overlay on the image, right-click the layer name and select Load Layer as Annotation. This is useful, for example, in creating a PowerPoint presentation from the view.
• Double-clicking an annotation item or vector layer in the Layer Manager displays the Properties dialog, so you can quickly edit annotation or vector properties.
• You can right-click on an annotation item in the Layer Manager and select Go To Item to jump to the center of the annotation item.
• In the Preferences dialog, asterisks were placed next to field names to indicate which preferences require ENVI to be restarted before the preference takes effect.
• The Apply Gain and Offset tool works with any image that has gains and offsets defined in an ENVI header file (.hdr). It also works with Landsat, QuickBird, and WorldView images.
• The Create Coordinate System String dialog lets you choose a coordinate system, then creates a text file containing a coordinate system string that you can add to an ENVI header file (.hdr) or use with the ENVI application programming interface (API).
• The Image Registration workflow has an option to set the output pixel size. You can specify whether the output pixel sizes (x and y) are the same as the base or warp images, or you can set custom values.
• A patent was issued for "Segmentation-Based Image Processing System" on September 4, 2012. This patented algorithm is the basis for segmentation in Feature Extraction workflows.
• You can create a custom image format with an ENVI header and use the File > Open menu to open it. See the "Custom Image Format" tutorial in ENVI Help for a step-by-step example.
• You can read a custom data file without an ENVI header, or when you want to pass custom metadata into your spatial and spectral readers. You can then add this procedure to the menu under File > Open As > Custom. See the "Custom Open Procedure" tutorial for a step-by-step example. 
• A tutorial is available for working with raster metadata in the ENVI API.
• A TIME property was added to the ENVIRaster object. This property retrieves a reference to a new ENVITime object, which stores the acquisition time of a raster dataset.
• Connections to Esri^® Image Services work on all ENVI-supported platforms. An installation of ArcGIS^® 10 is no longer required.
• The Remote Connection Manager provides an ArcGIS Server option from the Type drop-down menu for connecting to Esri Image Services.
• ENVI reads PNG (Windows operating systems only), TIFF/GeoTIFF, and JPEG files from Esri Image Services and OGC servers.
• ENVI now supports Web Mapping Services (WMS) version 1.3.0.
• Datasets from OGC WMS and WCS servers can be used in all workflows.
• The Server and Port fields are populated automatically when you open a remote dataset in the Remote Connection Manager. The CGI Prefix field has also been removed.
• The following are new standard metadata fields in ENVI header files:
  • acquisition time: Data acquisition time in Coordinated Universal Time (UTC)
  • cloud cover: Percentage of cloud cover within the scene
  • solar irradiance: Top-of-atmosphere solar irradiance per band. Units are W/(m² * µm).
  • sun azimuth: Angle of the sun (in degrees) from due north in a clockwise direction.
  • sun elevation: Angle of the sun (in degrees) above the horizon
• New keywords based on these header fields were added to the ENVI_SETUP_HEAD and ENVI_FILE_QUERY routines for ENVI programmers.
• ENVI reads SPOT-6 imagery with metadata (DIMAP format).
• ENVI reads ALOS AVNIR-2 and PRISM Level-1B2 + RPC data.
• ENVI reads ALOS PALSAR complex data.
• ENVI reads acquisition time, cloud cover, gains, offsets, full-width-half-maximum (FWHM) values, wavelengths, solar irradiance, sun azimuth, and sun elevation from the following sensors:
  • ALOS AVNIR-2 and PRISM Level-1B2 + RPC data
  • ASTER
  • Disaster Monitoring Constellation (DMC) satellites
  • GeoEye-1
  • IKONOS
  • Landsat TM and ETM+
  • OrbView-3
  • Pleiades Primary or Ortho (single or mosaic)
  • QuickBird
  • RapidEye Level-1B
  • SPOT DIMAP
  • WorldView
• If available, these metadata fields are listed in the Metadata Viewer when you open an image. If you save images from the above sensors to ENVI raster format, these metadata fields are written to the ENVI header file as standard metadata.
• The Metadata Viewer lists user-defined metadata, in addition to standard metadata.
• Landsat filenames and metadata formats changed in August 2012. ENVI now reads Landsat files before and after this date. Choose a *_MTL.txt, *_WO.txt, or .met file, depending on the date and data provider (USGS or GLCF).
• The NITF Metadata Viewer contains a new field called "NITF Security Banner," and the Status Bar has an option to display the NITF Security Banner for NITF files.

Known Issues

ID	Description
	Pyramid files may contain incorrect metadata
Pyramid files (.enp) created prior to the Service Pack 2 release for images from sensors/formats listed under File > Open As may contain incorrect metadata. Workaround: Delete any .enp files before re-opening the data to ensure ENVI reads the metadata correctly.
	Windows 7 requires Internet Explorer 9 to display ENVI Help
On 64-bit installations running Windows 7 and Internet Explorer 8 or older, the Help browser opens but does not show content. Workaround: Install Internet Explorer 9.
54292	ENVI and ENVI Classic Help fail to launch from screen-level help links on Windows Vista
When clicking on a Help button in ENVI on Windows Vista systems with Internet Explorer, Help fails to launch. Workaround: From Internet Explorer, click the Alt key to display the toolbar, select Tools > Internet Options > Security tab, disable the checkbox Enable Protected Mode, and restart Internet Explorer.
60965	ENVI Classic cannot read or write Esri GRID files with ArcGIS 10
Workaround: Start ENVI (not ENVI Classic) and open Esri GRID files with the menu option File > Open As > IP Software > ESRI GRID. ENVI cannot write files to GRID format.
65466	ENVI cannot load images from the Layer Manager when SELinux is enabled
When installing CentOS 5, the default SELinux setting is "Enforcing." With this setting, the following error appears when you attempt to open an image: Failed to open image. This may be due to SELinux settings. Please see the Release Notes for ENVI, or contact your System Administrator. Workaround: Change the SELinux setting to "Permissive" or "Disabled" by setting SELINUX=permissive or SELINUX=disabled in /etc/sysconfig/selinux and rebooting.
65885	ENVI 5.0 cannot produce the same saturation stretch results as 4.8
In previous versions, a saturation stretch could be created on an image based on the displayed results. In ENVI 5.0, performing a saturation stretch from the display does not produce the same saturation stretch image as before. Workaround: Open and display the image, apply a 2% stretch, and save the result to a new file. Apply the saturation stretch to this new image. Note: This also affects the RGB to HSV type transforms and HSV image sharpening.
68278	SVM classification fails on some Macintosh systems
Support Vector Machine (SVM) classification fails in ENVI Classic and Example-Based Feature Extraction (ENVI) on 64-bit Mac OS X 10.8 systems.
68347	ENVI will not start if the custom code directory contains XML files
If the Custom Code Directory preference is set to a directory containing an XML file, ENVI will not start. Workaround: Do not add any XML files to this directory.

Problems Fixed

ID	Description
39052	FLAASH failed if the processing tile contained all zeros.
44570	FLAASH output dimensions must be an integer factor of the original dimensions.
56861	FLAASH: AISA data failed to process with error "Attempt to subscript SIG with VEGADR is out of range."
57139	FLAASH did not process images with no visible bands.
62179	FLAASH issued a READU error message during tile processing.
67684	FLAASH issued an error message when running Adjacency Correction.
42781	Co-occurrence texture names in ENVI did not match those in the Haralick reference.
50789	Co-occurrence filter measures did not return the correct correlation values.
57764	Co-occurrence filter measures were incorrect, not following the Haralick reference.
64772	Small dialogs truncated or hid filenames.
66780	The Mosaic file import process sent windows behind the main display.
67106	Users could not select regions of interest (ROIs) for Dark Subtraction.
67243	The Vegetation Index Calculator did not recognize wavelengths assigned to some sensors.
61072	ENVI could not read recent Landsat TM files processed by NLAPS.
67356	ENVI could not read new Landsat metadata after 21 August 2012.
67378	An error message appeared when running the Neural Net classification tool.
67627	Importing ground truth data crashed ENVI in Example-Based Feature Extraction.
67646	The Apply Gain and Offset tool returned incorrect results for Pleiades-1 data.
67701	ENVI::CreateRasterSpatialRef and ENVIRasterSpatialRefStandard were creating/reporting the value of TIE_POINT_PIXEL for the upper-left pixel as (1,1). This was incorrect and has since been updated to (0,0).
68049	Gains and offsets were incorrectly set from the BANDSB TRE in NITF files.
68265	The MAX and MIN spectral attributes were switched in Feature Extraction workflows.