WCPS1.5_Convert subset dimension interval to correct grid axis coordinate

[Bang Pham Huu]

This ticket is important and it is hard as currently, mostly the conversion from geo-referenced axis to grid axis is considered identical, such as Trimm

for c in (eobstest) return encode(
   c[
    '''Lat( 
         0: 
         c[t(0), Lat(70), Long(75)]  
       )'''

   , Long(25:27)], "csv")

this is converted to Rasql in WCPS 1.5

SELECT encode(c[*:*,0:3, '''0:c[0,100,10]]''', "csv" ) FROM eobstest AS c

without regarding to the Lat() axis, i.e, suppose c[0,100,10] = 20 then Lat(0:20) in the above WCPS is equal to Rasql [120:170] with the calculation in Petascope and the correct Rasql is

  SELECT encode(c[*:*,0:3, '''120:170''', "csv" ) FROM eobstest AS c

instead of c[…,0:20,…].

However, in Petascope, there is no way to know the value of c[t(0), Lat(70), Long(75)] before sending to Rasql and Rasql queries in tile to get value. Then, it need to add the calculation to convert this value in Lat() to grid-axis. i.e in Rasql query need to add the conversion also.

 SELECT encode(c[*:*,0:3, '''0:(c[0,100,10]] - MIN_LAT) / LAT_OFFSET''', "csv" ) FROM eobstest AS c

example: c[0,100,10] = 20, MIN_LAT = 5, LAT_OFFSET = 0.5 then Lat(0: c[t(0), Lat(70), Long(750)] will be converted to

SELECT encode(c[*:*,0:3, '''0:(c[0,100,10]] - 5) / 0.5''', "csv" ) FROM eobstest AS c

But, I'm not sure what if happen in irregular axis, need some discussion.

[Bang Pham Huu]

so, after the discussion, we consider this case is an exception and does not allow to add nested coverage expression inside trimming expression.

then it will throw an exception, e.g below.

c[ i(0: c[i(0), j(0)]),…]

[Bang Pham Huu]

as WCPS 1.5 does not support any of non-numeric in interval, this ticket is fixed as throw an exception.