Opened 9 years ago
Closed 8 years ago
#1298 closed defect (fixed)
CRS reprojection in WMS 1.3
Reported by: | Dimitar Misev | Owned by: | Alex Dumitru |
---|---|---|---|
Priority: | major | Milestone: | 9.3 |
Component: | petascope | Version: | development |
Keywords: | Cc: | Bang Pham Huu | |
Complexity: | Medium |
Description
This should be implemented; in rasql reprojection is supported with the project() function, in WCPS with crsTransform().
Alex please extend the description with more information and then assign to Bang.
Change History (3)
comment:1 by , 9 years ago
comment:2 by , 8 years ago
Milestone: | 9.2 → 9.3 |
---|
I need to do this ticket as well, just focused on WCPS 1.5 and almost forget.
comment:3 by , 8 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
the patch was accepted, close ticket, thanks.
Note:
See TracTickets
for help on using tickets.
The following changes are needed:
petascope.wms2.service.getmap.access.RasqlQueryGenerator Use the crs in mergedLayer.boundingbox.crs and modify the generated rasql query to reproject the rasdaman object to the given crs.
In petascope.wms2.service.insertwcslayer.InsertWCSLayerHandler you need to generate a boundingbox for each CRS that we support for the layer that is being imported
In petascope.wms2.service.getmap.MergedLayer you need to modify the boundingBoxToSubset method in such a way that it calculates the rasdaman indices based on the requested crs (boundingbox.crs). I assume there is already a method for this in WCS so try to use that one.
That should be it, test it according to wiki:WMSGuide that it works correctly with other crses and add a test in the systemtest