WMS requests returning blank depending on bounds
------------------------------------------------
Key: GEOS-1804
URL: http://jira.codehaus.org/browse/GEOS-1804
Project: GeoServer
Issue Type: Bug
Components: WMS
Affects Versions: 1.6.2, 1.6.1, 1.6.0
Reporter: Arne Kepp
Assignee: Andrea Aime
This one does not (already adjusted to avoid world bounds on all sides):
http://sigma.openplans.org:8080/geoserver/wms?exceptions=application/vnd.ogc.se_inimage&height=512&width=512&layers=topp:states&request=GetMap&srs=EPSG:900913&format=image/png&transparent=false&tiled=false&version=1.1.0&bbox=-2.001747083166E7,-2.001747083166E7,2.001747083166E7,2.001747083166E7
Cropping more from all sides helps:
http://sigma.openplans.org:8080/geoserver/wms?exceptions=application/vnd.ogc.se_inimage&height=512&width=512&layers=topp:states&request=GetMap&srs=EPSG:900913&format=image/png&transparent=false&tiled=false&version=1.1.0&bbox=-1.901747083166E7,-1.901747083166E7,1.901747083166E7,1.901747083166E7
The only difference is the bounds, but all three should be legitimate ?
EPSG:4326 does not have these issues when requesting the same area. It makes me think that this may be related to the sheer size of the coordinates, or that that we touch upon the world bounds issue while reprojecting (the native SRS of topp:states is 4326 if I remember correctly).
So I guess, on second thought, this could be related to the date boundary after all. I'll file a bug anyway, easy to mark as duplicate.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira