Opened 11 years ago

Closed 11 years ago

#384 closed defect (fixed)

crsTransform error on WCS temporal subsetting

Reported by: ungarj Owned by: Piero Campalani
Priority: major Milestone: 8.4.4
Component: petascope Version: 8.4
Keywords: Cc:
Complexity: Medium

Description

Following error occurs when attempting to make a temporal subset in WCS:

Error converting WCPS query to rasql query: Error translating XML WCPS query to rasql - crsTransform expression not implemented.

Tried with both YYYY-MM-DD and CRS:1 subsetting.

Or maybe I'm missing something on the PetascopeTimeHandling tutorial?

Change History (9)

comment:1 by olcl, 11 years ago

Same problem here : This occurs with versions 8.4.1-1 and 8.4.2-1 of the RPMs when requesting any of the output formats.

comment:2 by Piero Campalani, 11 years ago

Hi Joachim,
the queries seem right, so this sounds like this feature got broken.
So weird that Petascope detects a crsTransform operation there, you did not specify a subettingCrs!=nativeCrs.

I'll check.

comment:3 by Piero Campalani, 11 years ago

Owner: changed from abeccati to Piero Campalani
Status: newaccepted

comment:4 by abeccati, 11 years ago

Milestone: 8.4.3

This is a specific behavior of 8.4 if I recall correctly, hence it should stay on the release8.4 line and be replaced by complete temporalCRS in 9.0, scheduling accordingly

comment:5 by Dimitar Misev, 11 years ago

Milestone: 8.4.38.4.4

comment:6 by Piero Campalani, 11 years ago

Joachim, I cannot reproduce the error: are you still having this problem?

Here this is working fine:

  • ANSI-indexed time
    http://localhost:8080/petascope/wcs2?service=WCS&version=2.0.1&request=GetCoverage&coverageId=eobstest&subset=t,CRS:1(1)&format=image/jp2
    
  • ISO8601 date:
    http://localhost:8080/petascope/wcs2?service=WCS&version=2.0.1&request=GetCoverage&coverageId=eobstest&subset=t(1601-01-01)&format=image/jp2
    

comment:7 by Piero Campalani, 11 years ago

(I'm in the HEAD of release_8.4 branch, changset:635be2 )

comment:8 by abeccati, 11 years ago

Let's tag the 8.4.4 and see if it is solved in a packaged release (it takes longer to ask for builds on branches to user :) ). As soon as its out we close this and reopen if needed.

comment:9 by Dimitar Misev, 11 years ago

Resolution: fixed
Status: acceptedclosed

I can't reproduce either, it seems like this is quite outdated so I'll close it.

Note: See TracTickets for help on using tickets.