VISAT Wish List
Export/Import for information stored in the *.DIM file
Very often I need to apply the same color map, contrast stretch, bit masks, pins etc. on several datasets. Currently I have to repeat the procedure of adding the info for every dataset. It would be very convenient if I could:
- Set the color map, contrast stretch, bit masks, pins etc. in one dataset
- Export the settings into e.g. a text file
- Import the settings into a new dataset
Sampsa Koponen
Pin display Improvements
Enable scaling of pins and text lables. It would be good if the size of the pins and text labels could be defined and changed by the user.
Kerstin Stelzer
VISAT Product Reader
Product Reader for Landsat products. Landsat Images are available in different formats:
- CEOS
- FAST
- HDF
- GeoTIFF
- NLAPS
The CEOS, FAST, HDF and NLAPS files are all BSQ (Band Sequential), with one file for each band. Landsat 5 MSS data from ESA comes in CEOS format, BIL (Band Interleaved), with one file for all bands. Preferred format is FAST format (TBC).
Landsat format specification: http://landsat.usgs.gov/resource.html Kerstin Stelzer Available since BEAM 4.0
All product formats which VISAT can read, should be better promoted. For instance a list of all formats can be shown in the open dialog. Michael Paperin Fixed since BEAM 4.1
Product Reader for DIMAP products (e.g. SPOT images) -> example data would be availble for testing ;o) Kerstin Stelzer
VISAT Contrast Stretch / Color Palette Window Improvements
The setting of the histogram stretch of each of the bands used in RGB Contrast Stretch should be preserved. When opening the RGB with the same bands again, the contrast stretch should be applied. Currently, I can optimize the RGB contrast stretch (e.g. on virtual red, blue and green). When I close the image window, this information is lost. Carsten Brockmann
VISAT should support log-scaled color palettes for bands with a log-normal ditribution of pixel values such as for ocean color properties. [~HajoKrasemann]
It should be possible to apply current contrast stretch/color palette to other bands of the same or other data products with a single click. [~MichaelSchaale]
The Contrast Stretch / Color Palette Window should display percentage of suppressed pixels and pixels in use, e.g. as tooltip text or as label between the sliders. Especially for RGB images, it makes more sense to display percentage instead of sample values under the sliders. Norman Fomferra
Support discrete palettes and automatically generated value ranges (e.g. equal distance, percentiles, ...) Carsten Brockmann
VISAT Bitmask Overlay Window Improvements
Changing color or tansparency of a bitmask definition should be stored during a VISAT session, so that the settings
are available for other products. Michael Paperin
VISAT Spectrum Window Improvements
It should be possible to set axis properties in spectrum view diagram (tick mark distance, texts, unit, ...) and to apply these setting for multiple products [~RolandDoerffer]
It should be possible to view the spectra of more than one, spatially compatible products in the spectrum window. [~RolandDoerffer]
VISAT Statistics Dialog Improvements
The scatterplot dialog should support user-defined colors assigned to specific frequency. The scatter plot diagram should also support log-scaled axes [~RolandDoerffer]
Make statistics dialog non-modal so that it is possible to change the selected band without closing the dialog. Available since BEAM 3.5 Norman Fomferra
Diagrams in statistics dialog (histogram, profile plot) should better fit the curves into the window, e.g. select better axes and subdivisions. Michael Paperin
VISAT Pixel Data Extraction
All data of a certain pixel, either selected with the mouse or by a pin, shall be optionally exported for multiple, spatially compatible data products. [~RolandDoerffer]
VISAT Band Arithmetic
All bitmask expressions should be replaced by more general band arithmetic expressions. E.g. bitmask definition dialog, ROI definition dialog and all processors. Norman Fomferra Available since BEAM 3.3
The band arithmetic should predefine the bands x and y which represent the current pixel position. x and y should be used in expressions like other bands. Norman Fomferra Available since BEAM 3.3
It would be nice to have access to the values provided by the Scaling_Factor_GADS (e.g. sun spectral flux) for the band arithmetic Uwe Krämer
It would be nice to have some kind of notepad where snippets of expressions can be stored. Michael Paperin
Access to the expression history should be realised by selecting from some kind of a list. Michael Paperin
VISAT ROI Improvements
It should be possible to create a ROI by selecting points in the scatter plot. Carsten Brockmann
A ROI should additionally be defined by a set of pixels instead of only by a logical combination of criteria. Carsten Brockmann
It should be possible to export and import the pixels of a ROI as a list of geographic coordinates.[~DanielDye]
VISAT Product Subset Dialog Improvements
The VISAT subset dialog can now have floating point steps because we could use the new pixel resampling methods for computation of the subset product. Norman Fomferra
Subset dialog should also display and accept geographic coordinates as input Norman Fomferra
Subset dialog should be able to use an existing product subset as template for a new subset. This way it would be very easy to create e.g. a MERIS l1b subset an then open the same subset for the related MERIS L2 scene. So that the image views can be synchronized. Michael Paperin
Edit Data Product Components and Component Properties in VISAT
It should be possible to add and remove bands and metadata nodes to a data product. It should also be possible to change the name, description and other properties of the data product iteself, of its bands, its metadata, etc. Norman Fomferra Mostly available since BEAM 3.3
It should be possible to edit the BAND_WAVELENGTH property, so that new bands can be added to the spectrum view (e.g. when radiances are transformed into reflectances using band math). Carsten Brockmann Available since BEAM 3.4
Other VISAT features
More general information (e.g. orbit-number) about an opened product shall be always visible. For instance in the header bar of a scene view. Michael Paperin
The pixel position indicator (shown when the mouse cursor moves over an image view) shall be synchronized and shown over other image views from bands from the same data product. [~HelmutSchiller], Marco Zühlke, Michael Paperin
VISAT should allow to draw simple shapes, e.g. arrows, and write text on the image view. Michael Paperin
VISAT should have the capability to overlay iso-lines of any band in an image view. Michael Paperin
VISAT should be able to display vector data. For instance a temperature grid and a radiance band. Michael Paperin
It should be possible to apply image filters to the displayed images, e.g. a median filter in order to reduce noise. Available since BEAM 3.5 [~RolandDoerffer]
It should be possible to use different coloring schemes for different pixel types, e.g. RGB for land pixels and a color table based image for water pixels in order to display chlorophyll concentrations. [~RolandDoerffer]
It would be nice if VISAT could export the displayed world-map as an image. Michael Paperin
It should be possible to display point data originating from simple plain text (CSV) or Excel files. This is especially usefull for lists of in-situ sites for validation.
Realisation: A simple descriptor file (key-value pairs) shall be used to describe the separator character, the supressed columns, and the columns containing the map coordinates, the map units, the map coordinate reference system (incl. the Datum e.g. WGS84), column data types. Columns other than coordinates shall be displayed in a properties window used for inspecting the points. Descriptor files are stored permanently and become part of a VISAT installation. Norman Fomferra
It would be nice if VISAT could display points and polygons in the world-map, e.g. for diagnostic data sites. Kerstin Stelzer Ralf Quast
General BEAM Wish List
Improved DEM Support
It should be possible to use high resolution DEM such as the 1 arcsec. SRTM DEM from GLCF (see http://glcf.umiacs.umd.edu/data/srtm/) [~AndreasVater] (05.04.2005, andreas@rsrg.uni-bonn.de)
BEAM should download only those tiles from a server which are required for resolving the current scene. Norman Fomferra
The list of available DEMs should be available from the server. This service should be implemented as dedicated DEM-tile-providing WebService. Norman Fomferra
Autoselection of DEM tiles for active product. [~HugoGonzales]
The orthorectification should have an option to output the elevation from the DEM and the actual, corrected lat/lon values for each pixel in separate bands. [~LuisGuanter]
VISAT RGB Improvements
Multiple user defined RGB profiles per product type Norman Fomferra Available since BEAM 3.4
Initial gamma and contrast stretch settings for RGB images should also come from the RGB profiles (see VISAT preferences dialog). Norman Fomferra
RGB profiles saved by the expression editor in VISAT should be re-useable by pconvert. At present you have to manually change red=/blue=/green= to r=/g=/b= in order for pconvert to load the profile. [~MattJPritchard]
BEAM auto update
VISAT performs an up-to-date check since version 3.1 and informs users about the availability of a new version. VISAT should be able to automatically update the current installation in the case that a new software build is available. Technically, this can be resolved by an application loader which does not bind beam.jar at start-up time. A WebService could be established to handle version comparison and update procedures. Norman Fomferra
Installing new version
When installing a new BEAM version, the existing extensions and user settings of the previous version should be taken over. Michael Paperin
New options for pconvert
An option at the command line let the user define a color palette for the output image. Available since BEAM 3.5
Also pconvert should allow to define the output file name additionally to the output directory. [~StevenHubbard]
BEAM Plug-in Permissions
Currently a BEAM plug-in can do anything what is possible with Java, e.g. delete files, terminate the current process, establish internet connections and so forth. Plug-ins should not have the permission to do such things. Technically, the BEAM PlugInLoader should use a special URLClassLoader with overridden URLClassLoader.getPermissions method. Norman Fomferra
MODIS Bow-Tie Effect
BEAM should be able to compensate the MODIS bow tie effect in MODIS Level-1b and 2 data products. Available since BEAM 3.5 Norman Fomferra
Support for huge level-3 data products
The level-3 binning and mosaic processors of BEAM should be able to write data products organized in tiles. VISAT should then be able to recognize such tiled images and should display them at different detail levels dependent on the current zoom factor.
Norman Fomferra
MapTransform Issues
The GeoTIFF export in BEAM currently hard-codes the supported map-projections. Map-projections registered by plug-ins cannot be recognized in the GeoTIFF export function. Norman Fomferra
We need a MapTransformException thrown by the inverse and forward methods of MapTransform in order to signal inability to transform a given coordinate. Norman Fomferra
The actual map-projection transformation (ProductProjectionBuilder class) can be optimized by performing the coordinate transformation only every n-th pixel. A fast linear interpolation can then be used to compute the in-between pixels. Norman Fomferra
It should be possible to compute the RMSE (Root Mean Square Error) of the geo-coordinates of a projected data product.
[~AntonioAraujo]
Processors
A simple processor to transform MERIS L1b radiances into TOA reflectances. Available since BEAM 3.5 Carsten Brockmann
Support for ATSR-1/2 products in ENVISAT format
Need support for ATSR-1/2 products in ENVISAT format, which are structurally the same as the equivalent AATSR products but with modified product naming convention.
Instead of
- ATS_TOA_1Petc.N1
- ATS_NR__2Petc.N1
We now need (for atsr-1) - AT1_TOA_1Petc.E1
- AT1_NR__2Petc.E1
and for atsr-2 - AT2_TOA_1Petc.E2
- AT2_NR__2Petc.E2
(Sorry, had trouble encoding the double underscore in the NR name)
Thanks, [~MattJPritchard]
Available since BEAM 4.1.
Importing/Opening gzipped products
It would be very useful if BEAM could open/import products that are gzipped. Is this feasible using zlib? (Similar to the /compress switch for file i/o in IDL?) [~MattJPritchard]
Available since BEAM 4.1 for ENVISAT products.
Collocation Tool
It would be great if band subsetting would be possible within the Collocation tool -> only subset of bands (of both input products) will be included in new collocation product. Kerstin Stelzer
Linear Spectral Unmixing
Apply data processing only on ROI. Kerstin Stelzer