| CLASSIC-68552 |
In FLAASH, the "Automatically Save Template File" and "Output Diagnostic Files" parameters in the Advanced Settings page were not written to the template file. |
| CLASSIC-68551 |
ENVI Classic did not recognize projections in TIFF files that the ENVI API could. |
| CLASSIC-68537 |
ENVI Classic issued a READU error with ENVI_EXTRACT_DEM_DOIT. |
| CLASSIC-68483 |
ASCII XYZ output had six columns rather than three. |
| CLASSIC-46337 |
ENVI Classic did not correctly orient georeferenced ASAR imagery. |
| |
Documentation included an invalid formula for calculating the kappa coefficient. |
| ENVI-70530 |
ENVI issued an OSELECTED error when closing a file, if bands were selected in the Data Manager. |
| ENVI-70524 |
ENVI issued an error and crashed when running ENVI Classic tools if the Display Errors on Screen preference was set to No. |
| ENVI-70516 |
ENVI issued an error when editing 2D polygon shapefiles. |
| ENVI-70514 |
The Series/Animation Manager menu item was disabled even when series layers were selected in the Layer Manager. |
| ENVI-70513 |
ENVI crashed when the Band Animation dialog was closed during playback. |
| ENVI-70511 |
The ALSAT-2A filter function was invalid. |
| ENVI-70510 |
ENVI did not connect to WMS version 1.1.0 servers. |
| ENVI-70505 |
Stacked plots did not match the order of the plot legend. |
| ENVI-70502 |
Auto Input via Z-profile failed in Spectral Analyst. |
| ENVI-70500 |
Users could not edit Y-axis ranges when plots were stacked in the Spectral Profile. |
| ENVI-70495 |
ENVI issued an error and crashed when applying an ROI threshold mask to rasters. |
| ENVI-70490 |
Building a mask took a long time when using a thresholded ROI. |
| ENVI-70489 |
Band names of SPOT RGB images were incorrect in Layer Manager. |
| ENVI-70486 |
Users could edit headers for data that was in a read-only directory. |
| ENVI-70483 |
ENVI did not recognize RPC information from WorldView-2 data. |
| ENVI-70482 |
Reprojecting ADS40 images with RPC information resulted in non-square pixels. |
| ENVI-70478 |
Two rasters with the same prefix and additional dots in the filenames would both close if users closed one raster. |
| ENVI-70474 |
ALOS-2 Level 1.5 data in CEOS format were not correctly georeferenced. |
| ENVI-70473 |
ENVI::OpenRaster did not recognize ENVI .enp (pyramid) and .hdr (header) files. |
| ENVI-70467 |
Bands were still listed in the Data Manager after closing a file. |
| ENVI-70462 |
ENVI crashed when opening some WorldView-3 tiled files. |
| ENVI-70460 |
Users could not manually change the threshold in the Image Change workflow. |
| ENVI-70459 |
The Open Recent file list did not include files that were dragged and dropped into the display. |
| ENVI-70458 |
The Open Recent file list did include all files opened through multiple file selection. |
| ENVI-70456 |
ENVI did not open any more files after loading more than 20 NITF files with C8 or M8 image compression. |
| ENVI-70452 |
Spectral profiles created from ENVI Classic tools did not maintain X and Y plot ranges. |
| ENVI-70446 |
Axis titles were not preserved in plot windows. |
| ENVI-70445 |
ENVI did not allow saving an image or chip to JPEG format with a quality level. |
| ENVI-70439 |
Time series animation stopped while image frames were loading. |
| ENVI-70437 |
ALOS PALSAR documentation was incorrect about real and imaginary components. |
| ENVI-70434 |
GLT reprojection was slow for large images. |
| ENVI-70433 |
ENVI issued an EFFECTIVEBANDWIDTHS error when opening some GeoEye-1 datasets. |
| ENVI-70431 |
ENVI issued an error when exporting an ENVIQUACRaster to a Geospatial PDF file in the ENVI API. |
| ENVI-70428 |
ENVIMetaspectralRaster did not inherit gains and offsets from input rasters. |
| ENVI-70427 |
Starting ENVI runtime or ENVI+IDL caused an error after installation, requiring a reinstallation. |
| ENVI-70422 |
The code example for ENVIRasterMetadata listed the wrong number of bands for the selected raster. |
| ENVI-70417 |
The Polarization Signature Viewer was hidden behind the main ENVI application window. |
| ENVI-70407 |
ENVI did not read some SkySat metadata files. |
| ENVI-70405 |
The Spectral Subset section of the input file selection dialog did not apply the Bad Bands List by default. |
| ENVI-70404 |
ENVI issued a memory allocation error when calculating statistics for all ROIs. |
| ENVI-70401 |
ALOS-2 Amplitude, I, and Q imagery displayed as an RGB composite instead of black and white. |
| ENVI-70400 |
The Spectral Hourglass Wizard did not honor spectral subsets in the classification process. |
| ENVI-70399 |
ENVI issued an error when loading vector images on top of GLT-projected images. |
| ENVI-70394 |
The Metadata Viewer was still open after its respective image was closed. |
| ENVI-70393 |
Users could open multiple Metadata Viewer dialogs per image. |
| ENVI-70392 |
Red and green band names and wavelengths were incorrect in the Data Manager for WorldView-2 four-band datasets. |
| ENVI-70389 |
SPOT-7 PMS three-band products were missing some metadata. |
| ENVI-70388 |
Documentation was incorrect for Parallelepiped Classification. |
| ENVI-70383 |
Some ENVI dialogs still had a Queue button, which is no longer functional. |
| ENVI-70375 |
ENVI issued an error when starting the Build Mask tool. |
| ENVI-70368 |
Documentation was incorrect for the VALUE keyword in ENVI_REPORT_ERROR. |
| ENVI-70360 |
IKONOS wavelength values did not match published values. |
| ENVI-70354 |
The Data Manager listed incorrect wavelengths for NPP VIIRS SDR datasets. |
| ENVI-70348 |
ROI layers with hundreds of ROIs did not display correctly. |
| ENVI-70346 |
DEM Extraction failed with WorldView-3 panchromatic datasets. |
| ENVI-70344 |
The Rule Classifier dialog was hidden behind the main ENVI application. |
| ENVI-70343 |
ENVI did not clearly define what wavelength units it recognized. |
| ENVI-70342 |
GeoTIFF imagery did not open with standard map information. |
| ENVI-70341 |
ENVI did not tile TIFF images correctly with some GeoEye-1 tiled datasets. |
| ENVI-70338 |
Output header files from running ENVIQUACTask did not honor the DATA_IGNORE_VALUE. |
| ENVI-70335 |
Users could not restore an ENVIROIMaskRaster in the ENVI API. |
| ENVI-70333 |
The FLAASH output directory was not created unless users pressed the Enter key. |
| ENVI-70332 |
The FLAASH Spectral Polishing Width returned to a previous value unless users pressed the Enter key. |
| ENVI-70327 |
Shapefiles with an arbitrary projection created with ENVI LiDAR did not display correctly over an arbitrary-projected DEM. |
| ENVI-70326 |
ENVI could not create an RGB composite from two bands. |
| ENVI-70304 |
ENVISpectralIndexRaster yielded different results for the Red Green Ratio Index than did ENVI_VEG_INDEX_DOIT. |
| ENVI-70284 |
WorldView-3 was not included in the Spectral Resampling pre-defined filter function list. |
| ENVI-70273 |
The Series/Animation Manager played back twice as slow when a pyramid file was present. |
| ENVI-70230 |
The Overlay Classes tool did not work correctly. |
| ENVI-70206 |
The default linear stretch value was not honored in header files. |
| ENVI-70201 |
ENVI returned unexpected results when using Band Math with negative pixel values. |
| ENVI-69939 |
ENVIImageIntersectionTask issued an error message with single-band BIP input rasters. |
| ENVI-69893 |
ENVI crashed while building pyramids for tiled GeoEye data in DigitalGlobe format. |
| ENVI-68463 |
The Edit ENVI Header tool used an old coordinate system selection dialog. |
| ENVI-68135 |
The Decision Tree Classification help topic was updated to remove unsupported special variables. |
| ENVI-68029 |
Some TIFF files displayed with a custom stretch that could not be changed. |
| LIDAR-69036 |
Certain building perimeter shapefiles would not display in ENVI. |
| LIDAR-69012 |
Datasets were not recognized as open if CreateLidarFromSubrect method was used. |
| LIDAR-69003 |
LiDAR was incorrectly displaying AgerPoint files with extra bytes stored after the last point record. |
| LIDAR-68994 |
Vector files were not displayed properly when products were generated at 50 cm resolution. |
| LIDAR-68992 |
RGB values were not correctly recognized in projects created from a .txt file. |
| LIDAR-68989 |
Projects with a file path longer than 256 characters were incorrectly indentified as being read-only. |
| LIDAR-68862 |
The LiDAR API was not saving the spatial reference for LAS file output. |