[gdal-dev] Different image with WMS vs tiled WMS
eduardo.ramalho at gmail.com
Tue May 25 11:41:52 EDT 2010
I'm using "gdal_translate" 1.7.1 to create a local png file, by WMS
protocol, from GeoServer 2.0.1.
The file created by WMS is ok. When I try to access the same content
by tiled WMS (WMS-C) the file generated is not quite right.
The difference is on the top right corner of the generated image. By
WMS, my geometry bounding box touches the image border on all sides.
When I request the same image (same pixel dimension, projection and
georeferenced coordinates) the image has an blank band between the
border and my geomerty on top and on right corners. My geometry is not
clipped but it appears like it was scaled down to fit that band on the
same image pixel dimension.
I probably missing something but cannot find any documentation to
justify this problem. Can someone lead me to the rigth path ?
I investigate the GeoServer logs, to try to understand what Gdal was
requesting. This is what I found.
1) A correct image is generated with this kind of request:
1.1) The projection EPSG:3763 is native to my datasource.
1.2) The Bounding box is calculated by postgis for my geometry
1.3) The width and height is the request image dimension.
2) For a tiled WMS request, I only changed the following items on XML
2.1) The URL to GeoWebCache service (inside GeoServer)
2.2) The blocksize from 996x2048 to 256x256. The 256 is my tile size
as defined on GeoWebCache.
This generates 32 http requests by WMS like this.
2.3) it request 8 rows and 4 columns
2.4) 16 requests had "...&width=228..." and not "256".
2.5) all the bbox parameters never outgrown my geometry bbox.
Is this enough to understand what is happening ?
More information about the gdal-dev