Opened 9 months ago

Closed 8 months ago

#1404 closed defect (fixed)

Petascope_WCS_Check subsettingCrs functionality

Reported by: bphamhuu Owned by: bphamhuu
Priority: major Milestone: 9.3
Component: petascope Version: development
Keywords: Cc: dmisev, mdumitru, vmerticariu
Complexity: Medium


From the CRS Extension OGC

subsettingCrs: CRS Identifier indicating the CRS in which the request subsetting coordinates are expressed.

However, it seems it does not work when requested subsetting is not native CRS (e.g: request in 3857 and native coverage is 4326)


and return error

Lat axis: subset (2999080.943:3503549.844) is out of bounds.

This works with WCPS

for c in (test_eobstest1) return encode(c[t:"CRS:1"(0),
Lat:""(2999080.943:3503549.844)] , 

The WCS query with subsetting in 3857 is equivalent with this subsetting 4326 query


Change History (2)

comment:1 Changed 9 months ago by bphamhuu

  • Cc vmerticariu added

Merged with Alex's example

 See this request
 on the testbed server that fails because it tries to use the subsets given
 in EPSG:3857 as if they were in EPSG:3210

comment:2 Changed 8 months ago by bphamhuu

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.