Band names in Petascope

[Piero Campalani]

Originated from ​here

Currently, band names are streamlined to RasQL queries without any intervention.

This raises the question: why band names are stored in petascopedb then?

This can be misleading when petascopedb (in ps_range_type_component table) declared labels which differ from the labels in RASBASE.

Thus, Petascope should either:

• translate any band label to its numerical index (eg .red to .0);
• drop this info in petascopedb and read band labels via RasQL

I personally recommend the first solution, for better flexibility and performance.

[Dimitar Misev]

I'm also in favor of the first solution, especially considering #132

[Marcus Sen]

Yes, setting up band names in the underlying rasdaman collections is cumbersome and option 1 seems most flexible.

[Piero Campalani]

I also add that this relates to WCPS, since WCS correctly checks what petascopedb says about band names before proceeding.

[Piero Campalani]

Fixed in changeset:a519796 : WCPS now translates range field names (described in petascopedb::range_type_component) into rasdaman band indexes.