I have set up a cascaded WMS store/layer in GeoServer 2.1.3.
When getting maps from this layer, I notice that GeoServer adjusts the
width, height and bbox parameters before passing the request on to the real
WMS. For example, if I request this:
service=WMS&request=GetMap&version=1.1.1&layers=__all__&styles=&format=image%2fpng&transparent=false&height=256&width=256&srs=EPSG%3a3006&bbox=318975.9996007302%2c6400768.000002109%2c319103.9996027855%2c6400896.000002142
The following request is performed by GeoServer:
SERVICE=WMS&LAYERS=__all__&FORMAT=image%2Fpng&TRANSPARENT=FALSE&HEIGHT=266&BGCOLOR=0xFFFFFF&REQUEST=GetMap&BBOX=318971.24960065394,6400762.7500021085,319109.2496028698,6400900.750002143&WIDTH=266&STYLES=&SRS=EPSG:3006&VERSION=1.1.1
Notice that width and height has changed from 256 to 266, and the bbox is
slightly larger. My guess is that this is some form of border/gutter that
is later cut away before returning the result to the client. However, the
resulting image also has what looks like scaling artifacts, with jagged
lines and text that looks slightly blurry at places.
My question is, why is this happening, and what can I do to prevent this
behaviour in GeoServer. I would like the cascading to just pass on the
request without any modification, and without modifying the resulting image.
Best regards,
Per Liedman
--
Per Liedman
Software Engineer, Kartena AB
[email protected] / +46 (0)31 - 77 44 397
http://www.kartena.se
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
