#1313 closed defect (fixed)

WCPS_Tranform interval's coordinates in non-native CRS

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

Description

In WCPS or WCS (subsettingCrs), it is allowed to query in a trimming interval with supported CRS beside native CRS (e.g: mean_summer_airtemp: EPSG:4326, CRS:1 also support other CRS like 3857).

for c in (eobstest) return encode(
(c[t(1),
Long:"http://www.opengis.net/def/crs/EPSG/0/3857"(12312320:35123123),
Lat:"http://www.opengis.net/def/crs/EPSG/0/3857" (112310:1512312)]),
"tiff", "nodata=0")

Then the coordinates in non-native CRS (3857), will be transformed to native CRS (e.g: 4326):

"3857": (12312320:35123123) -> "4326": (20:30) of Lat axis and (150:350) in Grid axis

without supporting this function, Petascope will not handle and pass the native CRS with coordinates/bounding box to Rasql Query:

for c in (eobstest) return encode((c[t(1),
Long:"http://www.opengis.net/def/crs/EPSG/0/3857" (20:35),
Lat:"http://www.opengis.net/def/crs/EPSG/0/3857" (10:15)]),
"tiff", "nodata=0")
select encode(c[1,-10:20,121:131], "GTiff", 
"nodata=0;
xmin=20.0;xmax=35.0;ymin=10.0;ymax=15.0;
crs=EPSG:4326") from eobstest AS c where oid(c)=1537

Change History (1)

comment:1 Changed 15 months ago by bphamhuu

  • Milestone changed from 9.2 to 9.3
  • Resolution set to fixed
  • Status changed from new to closed

it is fixed in the patch ticket 1188, when use subsettingCrs with non-native CRS (e.g: 3857), it will translate the subset from 3857 to 4326 in geo-axis, close ticket.

Note: See TracTickets for help on using tickets.