Opened 13 years ago
Last modified 13 years ago
#3993 new defect
WCS GetCoverage returns right data, wrong coordinates
| Reported by: | keithmoss | Owned by: | sdlime |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | MapServer C Library | Version: | unspecified |
| Severity: | normal | Keywords: | wcs, xyz, getcoverage |
| Cc: |
Description
We're requesting a single pixel bounding box in XYZ output format. The coordinates returned are incorrect, but the data value is correct. We've verified the returned data value in ER Mapper.
The coordinates returned seemed to be the top left corner of the source dataset.
A grid of 3x3 pixels over the same area returns valid coordinates and data values.
See attached ZIP file for sample data and mapfile.
## Example ## URL: SERVICE=WCS&VERSION=1.0.0&REQUEST=GetCoverage&COVERAGE=xyz_test_case&CRS=EPSG%3A4326&BBOX=115.5175%2C-32.0125%2C115.52%2C-32.01&FORMAT=XYZ&RESX=0.0025&RESY=0.0025
Returns: 112 -10.000000000000002 5119
The equivalent call to GDAL's Translate utility: gdal_translate -of XYZ -projwin 115.5175 -32.01 115.52 -32.0125 xyz_test_case.dat.ers extract2.txt
Returns: 115.51875 -32.011249999999997 5119
Attachments (1)
Change History (3)
by , 13 years ago
| Attachment: | xyz_test_case.zip added |
|---|
comment:1 by , 13 years ago
MapServer version 6.0.0, GDAL 1.8, PHP MapScript? ($Revision: 11619 $ $Date: 2011-04-27 12:23:07 -0300 (Wed, 27 Apr 2011) $)
We've opened another bug which may be related: http://trac.osgeo.org/mapserver/ticket/3994
comment:2 by , 13 years ago
We can also provide URLs to our development service for testing/verification if required.
Test case