Opened 4 years ago

Closed 3 years ago

#470 closed defect (fixed)

support asterisk in trim operation

Reported by: j.yu Owned by: pcampalani
Priority: major Milestone: 9.0
Component: petascope Version: 8.5
Keywords: asterisk subset Cc: mdumitru, mantovani@…
Complexity: Medium

Description (last modified by j.yu)

According to wcs kvp req8
shall not return an exception

The log tells :
java.lang.NumberFormatException?: For input string: '*'
may be the error happens when * is converted to numeric number

support * in subset

stringLo= low;


stringHi= low;


Change History (15)

comment:1 Changed 4 years ago by j.yu

  • Description modified (diff)
  • Owner changed from j.yu to pcampalani
  • Status changed from new to assigned

comment:2 Changed 4 years ago by dmisev

A comparable request with the new petascope is:



<ows:ExceptionReport version="2.0.0" 
    xmlns:ows="" xmlns:xsd="" xmlns:xlink="">
    <ows:Exception exceptionCode="InvalidRequest">
        <ows:ExceptionText>Error while casting a subset to numeric format for comparison: For input string: "*"</ows:ExceptionText>


comment:3 Changed 4 years ago by pcampalani

Ok I didn't know about this WCS req. and the CITE testsuite does not include it I guess, since all the KVPs passed..
I see the first test is for reqs 1 to 9:

Assertion: req1-9:For all coverages offered by the server under test, test coverage
structure, service parameters, and service metatada via GetKVP GetCapabilities, 
DescribeCoverage and GetCoverage operations. Verify the responses contain the required information.

But it runs only DescribeCoverage and GetCapabilities requests.

comment:4 Changed 4 years ago by pcampalani

  • Milestone set to 9.0

comment:5 Changed 4 years ago by pcampalani

  • Keywords asterisk subset added

comment:6 Changed 4 years ago by pcampalani

Not sure about how to enable this.

Starting at WCPS, should the asterisk be incorporated as:

  • a numericScalarExpr
  • a stringScalarExpr
  • a new kind of ScalarExpr?

The first and third case are preferred, otherwise the asterisk would need to be "quoted" in the request.

How is this handled in RasQL?

comment:7 Changed 4 years ago by dmisev

In rasql the asterisk is recognized, e.g.

select c[*:*,*:*] from mr as c

is equivalent to

select c from mr as c

I think the best way is to enable this in WCPS, e.g.

for c in (mr)

and then translating it from WCS to WCPS will be trivial.

comment:8 Changed 4 years ago by pcampalani

Yes, I was starting with the assumption to start enabling the WCPS, but the issue is.. see comment:6 :)

comment:9 Changed 4 years ago by dmisev

I think I'd adapt numericScalarExpr, or introduce something like wildcardScalarExpr. The first is probably easier

comment:10 Changed 4 years ago by pcampalani

Fixed for WCS KVP and WCPS in changeset:5b93ab3.
Keep this open while fix for WCS XML/SOAP/REST is applied.

comment:11 Changed 4 years ago by pcampalani

  • Cc mdumitru added
  • Resolution set to fixed
  • Status changed from assigned to closed

XML fixed in changeset:cde6ccf.
REST missing, but this ticket can be superseded by #554 as asterisk operations are in the systemtests.

comment:12 Changed 4 years ago by pcampalani

  • Cc mantovani@… added

Asterisk currently works only with numerical subsettings, whereas it breaks if timestamps are used in trimming: re-opening the ticket.

for c in (eobstest)
return encode(
   c[Lat(0), Long(51), t(*:"1950-01-03")]
, "csv")

TODO : fix, and add test.

comment:13 Changed 4 years ago by pcampalani

  • Resolution fixed deleted
  • Status changed from closed to reopened

Reopen since this currently works when numeric coordinates are in the other end of the subset with asterisk.

comment:14 Changed 4 years ago by pcampalani

  • Status changed from reopened to accepted

comment:15 Changed 3 years ago by pcampalani

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

Asterisks now also work in association with ISO8601 time subsets (changeset:61fe75e).

Note: See TracTickets for help on using tickets.