Opened 3 years ago

Closed 3 years ago

#756 closed defect (fixed)

Band names in Petascope

Reported by: pcampalani Owned by: pcampalani
Priority: major Milestone: 9.0.x
Component: petascope Version: development
Keywords: band labels Cc: mase
Complexity: Medium


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.

Change History (5)

comment:1 Changed 3 years ago by dmisev

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

comment:2 Changed 3 years ago by mase

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

comment:3 Changed 3 years ago by pcampalani

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

comment:4 Changed 3 years ago by pcampalani

  • Status changed from new to accepted

comment:5 Changed 3 years ago by pcampalani

  • Resolution set to fixed
  • Status changed from accepted to closed

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

Note: See TracTickets for help on using tickets.