Opened 8 years ago
Last modified 8 years ago
#1436 closed defect
WCPS_Supports user defined band names in range constructor — at Version 1
Reported by: | Bang Pham Huu | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 9.4 |
Component: | petascope | Version: | development |
Keywords: | Cc: | Dimitar Misev, Vlad Merticariu | |
Complexity: | Medium |
Description (last modified by )
current WCPS checks band names strictly (i.e: if in range constructor has a non-existing band, it will throw exception). This is necesary as in netCDF, it can write in coverage metadata user defined band names and should be supported.
WCPS query example:
for c in ( test_rgb ) return encode( { blueTEST: c.red; redTEST: c.blue }.redTEST , "netcdf")
the output should have redTEST as band name in netCDF.
\"redTEST\":{ \"type\":\"unsigned char\",\"metadata\":{\"units\":\"10^0\"},\"name\":\"redTEST\"}
Furthermore, a range constructor with a single field should only translate the field expression to rasql, and not to a whole range constructor. E.g.
single field
WCPS: for c in (test_rgb) return {blue: c.red} rasql: select c.red from test_rgb as c
multi field
WCPS: for c in (test_rgb) return {blue: c.red; red: c.blue} rasql: select {c.red, c.blue} from test_rgb as c
Note:
See TracTickets
for help on using tickets.