in this investigation?
Pablo Torres Carreira
Date: Wed, 27 Jan 2010 13:47:46 -0500
From: crschm...@crschmidt.net
To: discuss@lists.osgeo.org
Subject: Re: [OSGeo-Discuss] WCS/WMS accuracy tests?
On Wed, Jan 27, 2010 at 04:35:59PM -0200, Pablo Carreira wrote:
Hi Simone,
The issue
Hi there,
any feedback on this from the gdal/mapserver folks?
Anyone looked into my findings?
Simone.
---
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Founder - Software Engineer
Via Carignoni 51
55041 Camaiore (LU)
Italy
phone: +39 0584983027
Hi Simone,
The issue
http://jira.codehaus.org/browse/GEOS-3702217is not avaliable.
Pablo Torres Carreira
Date: Wed, 27 Jan 2010 18:39:51 +0100
Subject: Re: [OSGeo-Discuss] WCS/WMS accuracy tests?
From: simone.giannecch...@geo-solutions.it
To: discuss@lists.osgeo.org
Hi there,
any
-Discuss] WCS/WMS accuracy tests?
From: simone.giannecch...@geo-solutions.it
To: discuss@lists.osgeo.org
Hi there,
any feedback on this from the gdal/mapserver folks?
Anyone looked into my findings?
Simone.
---
Ing. Simone
] WCS/WMS accuracy tests?
From: simone.giannecch...@geo-solutions.it
To: discuss@lists.osgeo.org
Hi there,
any feedback on this from the gdal/mapserver folks?
Anyone looked into my findings?
Simone.
---
Ing. Simone Giannecchini
BTW, The possibility of the problem is in
Qgis and not the server has been contemplated in this investigation?
Pablo Torres Carreira
Date: Wed, 27 Jan 2010 13:47:46 -0500
From: crschm...@crschmidt.net
To: discuss@lists.osgeo.org
Subject: Re: [OSGeo-Discuss] WCS/WMS accuracy tests
message:
From: Steven M. Ottens ste...@minst.net
Date: December 9, 2009 2:03:31 PM GMT+01:00
To: OSGeo Discussions discuss@lists.osgeo.org
Subject: Re: [OSGeo-Discuss] WCS/WMS accuracy tests?
Reply-To: OSGeo Discussions discuss@lists.osgeo.org
Hi all,
I've finished my tests
Dear All,
I have spent some time investigating this isue with GeoServer trunk.
Here:
http://jira.codehaus.org/browse/GEOS-3702
you can find a quick detailed report. I am particularly interested in FrankW
feedback.
Ciao,
Simone
Steven M. Ottens wrote:
On Dec 7, 2009, at 5:47 PM, Stephen
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
Hello Steven,
the deegree crowd would also be interested in a description of your test
cases and the results. If you could send an email either here or,
preferably, to the deegree developer list [1], this would be much
appreciated.
I talked to one of the main deegree WMS developers and he told me
Hi all,
Working with Geoserver as a WCS we discovered that requesting a GeoTIFF in the
same projection as the original GeoTIFF produces a shifted dataset.
(http://jira.codehaus.org/browse/GEOS-3702) The shift is small, less than one
pixel of the original dataset, but with a coarse dataset of
15 matches
Mail list logo