We're updating the issue view to help you get more done. 

original BandNames from coverageViews are lost, being replaced by ColorModel based names

Description

Previously, when configuring a coverageView on a ImageMosaic of NetCDFs, the coverageBandDetails panel were filled with the coverage band names.

Right now, the band names are replaced by a representation of the color component.
As an instance, GRAY_INDEX, RED_BAND, GREEN_BAND, BLUE_BAND.

I think this is a consequence of
https://osgeo-org.atlassian.net/browse/GEOS-7767

Attached, a screenshot showing the old behavior (left side), and new behavior (right side).
Steps to replicate:

1) Have GeoServer running with NetCDF extension available
2) Configure an ImageMosaic store on top of the attached sample mosaic (need to be unzipped)
3) create a new coverageView, by moving the NO2 and O3 bands as output bands and save
4) Look at the band names in the Coverage Band Details panel.

Since introduced valid management of Alpha_band when dealing with coverageView, I wonder if we should check the input data type and color model to preserve original naming when dealing, as an instance, with NOT RGB / NOT Byte data (which will don't have alpha in the mix)

I have also noticed that an RGB-IR coverage (being configured without using coverageView) and footprint enabled has bands RED_BAND, GREEN_BAND, BLUE_BAND, ALPHA_BAND. I think this is another effect of

Environment

None

Status

Assignee

Andrea Aime

Reporter

Daniele Romagnoli

Triage

None

Fix versions

Affects versions

None

Components

Priority

Medium