WCPS request should enforce encode()

[Peter Baumann]

A user reports that the following query:

for c in (Sentinel2)
	  return
	      coverage ndvi
	        over
             $px N(0:*),
             $py E(0:*),
             $pt ansi(0:*) 
	       values 
           (float)
           ((c[E($px),N($py),ansi($pt)].B08 -  c[E($px),N($py),ansi($pt)].B02) /
           (c[E($px),N($py),ansi($pt)].B08 +  c[E($px),N($py),ansi($pt)].B02))

returns this error message: "Invalid format number in interval (0,0)".

Actually missing is the encode() call in the first place.

The parser should return a syntax error, as per WCPS standard, in such a case. And a test case should be added to systemtest.

[Bang Pham Huu]

@Peter: what about:

for c in (lena) return c

it is still a valid query without any error.

[Dimitar Misev]

Relevant standard clause:

7.1.2 processingExpr
The processingExpr element is either a encodedCoverageExpr (which evaluates to an encoded coverage; see Subclause 7.1.4), or a storeCoverageExpr (see Subclause 7.1.3), or a scalarExpr (which evaluates to coverage description data or coverage summary data; see Subclause 7.1.5).

[Dimitar Misev]

it is still a valid query without any error.

not according to the standard it seems.

[Bang Pham Huu]

Replying to dmisev:

it is still a valid query without any error.

not according to the standard it seems.

or this one? why even it needs encode()?

for c in (lena) return avg(c)

[Dimitar Misev]

Did you read comment:2?