Hi all,
I've finished my tests.
The conclusion:
Geoserver has a bug which offsets all the results by half a pixel, this is a
known issue with the definition of the location of a pixel. Added to this
there’s the no-data border which appears with non-native, non-multiple
requests. I presume that
Steven M. Ottens wrote:
Hi all,
I've finished my tests. The conclusion: Geoserver has a bug which
offsets all the results by half a pixel, this is a known issue with
the definition of the location of a pixel. Added to this there’s the
no-data border which appears with non-native, non-multiple
Steven M. Ottens wrote:
Mapserver doesn’t offset the data unless it is physically impossible
(non-native, non-multiple resolutions, extents which don’t snap to source
data) but produces a multi-band geotiff where the source data is single
band.
Steven,
Thanks for the excellent post. I'd be
Steven M. Ottens wrote:
On Dec 9, 2009, at 3:44 PM, Frank Warmerdam wrote:
Steven M. Ottens wrote:
Mapserver doesn’t offset the data unless it is physically impossible
(non-native, non-multiple resolutions, extents which don’t snap to source
data) but produces a multi-band geotiff where the
On Dec 9, 2009, at 6:02 PM, Frank Warmerdam wrote:
Steven,
I believe you would want to change this:
OUTPUTFORMAT
NAME GTiff
DRIVER GDAL/GTiff
MIMETYPE image/tiff
IMAGEMODE RGB
EXTENSION tif
END
to:
OUTPUTFORMAT
NAME GTiff
DRIVER GDAL/GTiff
MIMETYPE image/tiff
Hi all, just a general note to mention that in about an hour and a half the
OSGeo Marketing Committee is meeting using IRC. All are welcome to stop by and
comment on topics of discussion. This group has several opportunities for
folks to help out in meaningful way (no programming required).
