Opened 20 years ago
Last modified 13 years ago
#656 assigned defect
SRS Ignored in GetCoverage
Reported by: | warmerdam | Owned by: | sdlime |
---|---|---|---|
Priority: | high | Milestone: | 6.0 release |
Component: | WCS Server | Version: | unspecified |
Severity: | normal | Keywords: | |
Cc: |
Description (last modified by )
It seems that SRS is ignored in the GetCoverage, and the coverage is erroneously returned with the SRS of the map instead of the SRS of the layer on return. For instance: http://gdal.velocet.ca/cgi-bin/mswcs?REQUEST=GetCoverage&SERVICE=WCS&COVERAGE=TM&BBOX=448285, 4218488,463645,4233848&WIDTH=512&HEIGHT=512&FORMAT=GeoTIFF8&SRS=EPSG:32611 The layer is actually in EPSG 32611 (UTM 11 WGS84) but the result file is just WGS84 instead.
Attachments (1)
Change History (12)
comment:2 by , 20 years ago
I gather the CRS is the coordinate system of the BBOX. My suggestion for now is that we require the CRS and RESPONSE_CRS to match and if they don't return an exception. As noted elsewhere, omitting REPSONSE_CRS is not causing the code to use the CRS as the RESPONSE_CRS which is the action required by the spec.
follow-up: 6 comment:3 by , 20 years ago
Since CRS is required I know the fix. The only slight twist is when RESPONSE_CRS is present. In that case we have to project the BBOX before using it. Otherwise CRS and RESPONSE_CRS just modify the mapObj projection. I'll add the code today.
comment:4 by , 20 years ago
Frank, have you had a chance to verify the fix (assuming I made it)? Steve
comment:6 by , 16 years ago
Replying to sdlime:
Since CRS is required I know the fix. The only slight twist is when RESPONSE_CRS is present. In that case we have to project the BBOX before using it. Otherwise CRS and RESPONSE_CRS just modify the mapObj projection. I'll add the code today.
Steve,
I've just run into the same problem that the BBOX is to be reprojected when both the CRS and the RESPONSE_CRS are passed. In addition RESX and the RESY should also be adjusted when the WIDTH and the HEIGHT are not specified in the URL. I attach a patch that solved my problem, however I'm not sure in that all of the consequences have been considered properly.
by , 16 years ago
Attachment: | mapwcs.c.patch added |
---|
follow-up: 9 comment:7 by , 16 years ago
Description: | modified (diff) |
---|
Is this an issue in both 1.0 and the newer stuff Frank is working on? I will try to take a peek yet this week.
Steve
comment:8 by , 16 years ago
Milestone: | → 5.2 release |
---|
comment:9 by , 16 years ago
Replying to sdlime:
Is this an issue in both 1.0 and the newer stuff Frank is working on? I will try to take a peek yet this week.
Steve
I'm not sure about the 1.1 implication, but I've already posted a thread in the mapserver-dev list in this topic for comment.
http://www.nabble.com/WCS-RESPONSE_CRS-and-BBOX-projection-td17328294.html
Tamas
comment:11 by , 13 years ago
Milestone: | 5.6 release → 6.0 release |
---|
5.6 is over, moving to 6.0. Is this still an issue or not?