id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
3993	WCS GetCoverage returns right data, wrong coordinates	keithmoss	sdlime	"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"	defect	new	normal		MapServer C Library	unspecified	normal		wcs, xyz, getcoverage