Sorry for missing the previous discussion. I do have a mapfile, data, and requests that result in offset grids being returned. I will re-read the spec once more before filing a ticket, but seems strange (although not impossible) to me that the expected result would be a grid that is shifted compared to the original data. Would this still be the appropriate place to file the ticket? http://trac.osgeo.org/mapserver/ Thanks for the help.
On Mon, May 3, 2010 at 8:19 AM, Lime, Steve D (DNR) <[email protected]> wrote: > Like I said in the referenced message, I thought all was well in this regard. > We'd need a good test case (data, mapfile, 1.0/1.1 requests) attached to a > ticket. If there's a difference in the pixel models between WCS 1.0 and 1.1 > then a request that differs only in version might be expected to generate > slightly different output. I haven't looked at those specs in a good while > though. > > Steve > > ________________________________________ > From: [email protected] > [[email protected]] On Behalf Of Roger André > [[email protected]] > Sent: Sunday, May 02, 2010 11:45 AM > To: Ben Tuttle > Cc: [email protected] > Subject: Re: [mapserver-users] WCS 1.0 vs 1.1 image shifted > > Hi Ben, > > I think it's a bug, at least based on the conversation that took place last > year with Steve Lime regarding this - > http://www.mail-archive.com/[email protected]/msg06123.html > > I'm not sure what the current state is of this though. > > Roger > -- > > On Fri, Apr 30, 2010 at 1:18 PM, Ben Tuttle > <[email protected]<mailto:[email protected]>> wrote: > I am trying to understand the results I am getting from WCS requests > to MapServer. > If I make the same request changing only the WCS version the images I > get back are shifted by 1 pixel in the x and y directions. A request > for VERSION=1.1.0 gives me the image I expect while VERSION=1.0.0 > gives me back an image shifted by 1 pixel in the x and y directions to > the North and West. > The underlying data and mapfile are the same in both cases. So I am > not sure if this is perhaps a MapServer bug or if perhaps I am reading > the WCS spec incorrectly and this is actually the intended result (I > hope it's not). Can anyone help me out? > > Request Examples: > http://map.ngdc.noaa.gov/cgi-bin/mapserver/test_image_ms_wcs100_avgvis42_23_47_28.tif?map=../../../nfs/gisdata/mapserver/gcv4/index.map&request=GetCoverage&service=WCS&COVERAGE=F162008_v4_avg_vis&crs=EPSG:4326&VERSION=1.0.0&format=geotiff&resx=0.0083333333&resy=0.0083333333&bbox=42,23,47,28 > > http://map.ngdc.noaa.gov/cgi-bin/mapserver/test_image_ms_wcs110_avgvis42_23_47_28.tif?map=../../../nfs/gisdata/mapserver/gcv4/index.map&request=GetCoverage&service=WCS&COVERAGE=F162008_v4_avg_vis&crs=EPSG:4326&VERSION=1.1.0&format=geotiff&resx=0.0083333333&resy=0.0083333333&bbox=42,23,47,28 > > > System Details: > MapServer version 5.6.3 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP > OUTPUT=SVG SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=ICONV > SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER > SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER > SUPPORTS=THREADS SUPPORTS=GEOS INPUT=TIFF INPUT=EPPL7 INPUT=POSTGIS > INPUT=ORACLESPATIAL INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE > > Red Hat Enterprise Linux Server release 5.5 (Tikanga) > > -- > Cheers, Ben Tuttle > _______________________________________________ > mapserver-users mailing list > [email protected]<mailto:[email protected]> > http://lists.osgeo.org/mailman/listinfo/mapserver-users > > -- Cheers, Ben Tuttle _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
