63637
ENVI 5.5 Release Notes
ENVI 5.5 Release Notes
This article contains release notes for ENVI 5.5. See the following sections:
System Requirements
Platform |
Hardware |
Operating System |
Supported Versions |
Windows |
Intel/AMD 64-bit |
Windows |
7 SP1, 8, 10 |
Macintosh |
Intel 64-bit |
OSX |
10.10, 10.11 |
Linux |
Intel/AMD 64-bit |
Linux |
Kernel 2.6.32, glibc 2.12 |
Supported versions indicate that ENVI was either built on (the lowest version listed) or tested on that version. You can install and run ENVI on other versions that are binary-compatible with those listed.
The 64-bit Windows installer contains 32-bit binaries so that you can launch ENVI in 32-bit mode on 64-bit Windows systems. This ensures interoperability with ArcGIS®. You can find the 32-bit versions of ENVI in the Windows Start menu under Programs > ENVI 5.5 > ENVI for ArcGIS® and Programs > ENVI 5.5 > Tools > ENVI Classic 5.5 (32-bit).
ENVI 5.5 works with ArcGIS versions 10.2 through 10.5.
An X-Windows manager is required for Macintosh. ENVI was tested using XQuartz 2.7.11.
For optimal performance, your video card should have a minimum of 1 GB RAM and should support OpenGL 2.0 or later. Also be sure to install the latest drivers for your video card.
ENVI Help requires an HTML5-compatible browser.
New Features
This software release includes the new and enhanced features listed below.
Supported Data Types
ENVI supports the following sensors and data types:
- KOMPSAT-3A
- PeruSat-1
- WorldView-4
ENVI Modeler
The ENVI Modeler is a visual programming tool that you can use to create custom task-based workflows in ENVI. It combines the power of the ENVI application programming interface (API) with a simple and intuitive user interface to help you build workflows without any knowledge of ENVI programming. You can easily batch-process data, run tasks remotely on a Geospatial Services Framework (GSF) server, and generate IDL and Python programs from models. See the Visual Programming with the ENVI Modeler topic in ENVI Help. Start the ENVI Modeler by selecting Display > ENVI Modeler from the ENVI menu bar.
ENVI Py
The ENVI Py Engine is a standalone Python API that enables you to run any ENVITask. You can query for available tasks, retrieve task information, and run ENVI and IDL tasks on the desktop. See the Help that comes with the ENVI Py Engine for details.
To run ENVITasks through ArcGIS® Pro or ArcMap™, you need to install ENVI Py for ArcGIS Pro or ENVI Py for ArcMap. When integrated with ArcGIS, you can run ENVITasks that use data types supported by ArGIS. The supported data types are:
Bool |
Long64 |
Boolarray |
Long64array |
Boolean |
String |
Byte |
Stringarray |
Bytearray |
Uint |
Double |
Uintarray |
Doublearray |
Ulong |
ENVIURI |
Ulongarray |
Float |
Ulong64 |
Floatarray |
Ulong64array |
Int |
ENVIVector |
Intarray |
ENVIRaster |
Long |
ENVIAgCrops |
Longarray |
|
All array types can only be one dimension. See the ENVI Py for ArcGIS Help for details.
Data Processing
New broadband indices are available for use with the Spectral Indices tool and API. See the Broadband Greenness help topic for details.
- Green Chlorophyll Index
- Green Leaf Index
- Green Optimized Soil Adjusted Vegetation Index
- Green Soil Adjusted Vegetation Index
- Modified Soil Adjusted Vegetation Index 2
- Triangular Greenness Index
- Wide Dynamic Range Vegetation Index
The Lignin Cellulose Absorption narrowband index is also new. See the Dry or Senescent Carbon help topic for details.
A Search Window Size parameter was added to the RPC Orthorectification Using Reference Image and Generate GCPs from Reference Image tools. Increasing its value will reduce misalignment between the input raster and the reference raster.
Programming
Asynchronous Framework
The IDL Asynchronous Job Classes were extended for ENVI purposes, introducing classes to run ENVITask asynchronously:
- ENVIAsyncBridgeTaskJob: Allows the user to specify a single ENVITask that will executed inside an IDL_IDLBridge.
- ENVIAsyncSpawnTaskJob: Allows the user to specify a single ENVITask that will executed by the ENVITaskEngine.
Backward-Compatibility Notes
The INPUT_POINTCLOUD_URI property was changed to INPUT_POINTCLOUD in ENVIColorPointCloudTask.
The INPUT_RASTER_URI property was changed to INPUT_RASTERS in the following ENVITasks:
- ENVIBuildRasterSeriesTask
- ENVIBuildTimeSeriesTask
The INPUT_RASTERSERIES_URI property was changed to INPUT_RASTERSERIES in the following ENVITasks:
- ENVIRegridRasterSeriesTask
- ENVIRegridRasterSeriesByIndexTask
- ENVIRegridRasterSeriesByIntersectionTask
- ENVIRegridRasterSeriesByUnionTask
If you wrote a custom script with these tasks before ENVI 5.5, it will no longer work. You must update your script to use these new properties.
New Objects
Object |
Description |
ENVIParameterENVITask |
This function creates a new ENVITask parameter object. |
ENVITaskFromGSF |
ENVITask uses the ENVITaskFromGSF routine if a valid Geospatial Services Framework (GSF) URL is used instead of a task name. This routine communicates with the GSF server to request the definition of the requested task. It also configures the task's properties and parameters, based on that information. It provides a uniform API for running tasks remotely the same way they can be run locally. |
New ENVITasks
Task |
Description |
ENVIBuildGridDefinitionFromRasterTask |
Create a grid definition based on the spatial reference of another raster. |
ENVIBuildLayerStackTask |
Create a layer-stacked raster from a set of rasters that will be regridded to a common spatial grid. |
ENVICreateSubrectsFromROITask |
Create an array of subrects based on regions of interest (ROIs). |
ENVIEditRasterMetadataTask |
Set specific metadata values for an input raster and produce a new raster with the edited metadata. Metadata items that are not set with the task will remain intact. |
ENVIExportRasterToNITF20Task |
Export a raster to NITF 2.0 format. |
ENVIExportRasterToNITF21Task |
Export a raster to NITF 2.1 format. |
ENVIExportRasterToNSIF10Task |
Export a raster to NSIF 1.0 format. |
ENVIExportRasterToTIFFTask |
Export a raster to TIFF format. |
ENVIExtractRasterFromFileTask |
Open a single raster from an input uniform resource indicator (URI). |
ENVIGenerateFilenameTask |
Specify an output directory for task processing, including a prefix, file extension, and numbers. |
ENVILabelRegionsTask |
Separate an image into regions, which are groups of contiguous pixels that share the same value. Then label all of the regions with a unique index. |
ENVILinearSpectralUnmixingTask |
Perform Linear Spectral Unmixing. |
ENVIMatchedFilterTask |
Perform a matched filter supervised classification. |
ENVIMixtureTunedMatchedFilterTask |
Perform a mixture tuned matched filter (MTMF) supervised classification. |
ENVIPixelPurityIndexTask |
Compute a Pixel Purity Index (PPI). |
ENVIRunTaskTask |
Run a specified task. It returns a clone of the input task. |
ENVISAMImageDifferenceTask |
Perform image change detection using a spectral angle mapper (SAM) technique. |
ENVITopographicFeaturesTask |
Compute topographic features from a DEM. |
ENVITopographicModelingTask |
Perform topographic modeling on a DEM. |
Other Programming Updates
ENVIURI now supports a "force file" sentinel in the form of an exclamation symbol (!). With ENVITasks that have required or optional output rasters, you can set the OUTPUT_RASTER_URI property to an exclamation symbol to create a temporary file.
In previous versions, ENVITasks that produced virtual output required the creation of an output file. Now you can set the OUTPUT_RASTER_URI property to an asterisk symbol (*) to indicate that you want virtual output only without requiring an output file.
A revision
key was added to all task files, so that users can keep track of task definition changes between versions. Because of this update to the task template, the task schema value is now envitask_3.2
.
The following type
key was introduced to task templates: ENVIVirtualizableURI. This data type is a string that references a filename or folder to use, or that virtual output was requested.
The following user interface classes are new for ENVITasks:
- ENVIPointCloud_UI: Select a LAS-format point cloud file.
- ENVIPointCloudSpatialRef_UI: Enter parameters for a spatial reference object that applies to ENVI point clouds.
- IDLRadioButtons_UI: Create a set of buttons for the user to choose from. The buttons can be exclusive (only one item can be selected) or non-exclusive (multiple items can be selected).
The following are new parameter classes for various data types. They inherit from the appropriate IDLParameter* base class. They provide better dehydration and rehydration support for DEFAULT or VALUE parameters in the task template. You can use these objects to create custom data types for ENVITasks:
- ENVIParameterENVIVirtualizableURI
- ENVIParameterENVIVirtualizableURIArray
Fixed Issues
CLASSIC-46388 |
The eigenvector table was not properly labeled. |
ENVI-71084 |
Wavelengths and FWHM values differed between WorldView-3 and WorldView-2. |
ENVI-71127 |
The Dataset Browser did not read lat/lon scale factors. |
ENVI-71129 |
QUAC issued error messages with hyperspectral images in NITF format. |
ENVI-71218 |
ENVI Classic ROIs from an old hyperspectral tutorial would not open in ENVI. |
ENVI-71221 |
ENVI did not clean up .MOD files after running SVM classification. |
ENVI-71242 |
Opening a JPEG file with a world file (JGW) delayed the prompt for selecting a projection. |
ENVI-71249 |
Some ASD spectra were not importing correctly by not applying valid scale factors to raw data. |
ENVI-71254 |
The Metadata Viewer listed incorrect radiance values for Sentinel-2A Level-1C data. |
ENVI-71260 |
The ENVIRasterLayer::Export method did not export more than one image when multiple images were displayed. |
ENVI-71268 |
ENVIEqualizationStretchRaster failed with floating-point rasters. |
ENVI-71273 |
The Class Statistics tool failed with classes that contained no data. |
ENVI-71302 |
ROI statistics calculations ignored data ignore values. |
ENVI-71310 |
ENVIRasterMetadataItemTask changed its return value from 5.3 to 5.4, breaking code examples. |
ENVI-71341 |
1D geometry bands were not applied when opening HDF5 data using the Dataset Browser. |
ENVI-71345 |
Templates were not retaining interleave selection from the Dataset Browser. |
ENVI-71347 |
The "Change Interleave" description in the "Open Hierarchical Data" help topic needed clarification. |
ENVI-71350 |
A preference setting broke band animation. |
LIDAR-69031 |
Importing a reference shapefile issues an error that the shapefile is out of boundaries. |