Opened 8 years ago
Closed 8 years ago
#1404 closed defect (fixed)
Petascope_WCS_Check subsettingCrs functionality
Reported by: | Bang Pham Huu | Owned by: | Bang Pham Huu |
---|---|---|---|
Priority: | major | Milestone: | 9.3 |
Component: | petascope | Version: | development |
Keywords: | Cc: | Dimitar Misev, Alex Dumitru, Vlad Merticariu | |
Complexity: | Medium |
Description
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)
http://localhost:8080/rasdaman/ows?service=WCS&version=2.0.1& request=GetCoverage&coverageId=test_eobstest1& subset=Lat(2999080.943,3503549.844)&subset=Long(2894306.761,3339584.724)& subset=t("1950-01-01") &subsettingCrs=http://www.opengis.net/def/crs/EPSG/0/3857&format=image/tiff
and return error
Lat axis: subset (2999080.943:3503549.844) is out of bounds.
This works with WCPS
http://localhost:8080/rasdaman/ows?service=WCS&version=2.0.1&request=ProcessCoverages&query= for c in (test_eobstest1) return encode(c[t:"CRS:1"(0), Long:"http://www.opengis.net/def/crs/EPSG/0/3857"(2894306.761:3339584.724), Lat:"http://www.opengis.net/def/crs/EPSG/0/3857"(2999080.943:3503549.844)] , "tiff")
The WCS query with subsetting in 3857 is equivalent with this subsetting 4326 query
http://localhost:8080/rasdaman/ows?service=WCS&version=2.0.1&request=GetCoverage&coverageId=test_eobstest1& subset=Lat(26,30)&subset=Long(26,30) &subset=t:"CRS:1"(0) &outputCrs=http://www.opengis.net/def/crs/EPSG/0/3857&format=image/tiff
Change History (2)
comment:1 by , 8 years ago
Cc: | added |
---|
comment:2 by , 8 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Merged with Alex's example