K. Arthur Endsley created GEOS-5035:
---------------------------------------
Summary: Latent bounding box exception for WMS with small extent
Key: GEOS-5035
URL: https://jira.codehaus.org/browse/GEOS-5035
Project: GeoServer
Issue Type: Bug
Components: WMS
Affects Versions: 2.1.1
Environment: Sun Microsystems Inc.: 1.6.0_24 (Java HotSpot(TM) Client
VM);
Build Information:
Version 2.1.1
Subversion Revision 16080
Build Date 23-Jun-2011 10:45
GeoTools Version 2.7.2 (rev 37473)
Reporter: K. Arthur Endsley
Assignee: Andrea Aime
I've set up GeoServer WMS stores for several small areas (~4,000 to 5,000 ft^2)
from GeoTIFFs in GCS WGS84. Initially, the precision displayed in the Layer
description, under the Data tab beneath "Coordinate Reference Systems," is
inadequate (limited to three decimal places). When I set up the Layer(s) the
first time, I left this alone. However, when attempting to preview the
Layer(s), I received the following ServiceException:
<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE
ServiceExceptionReport SYSTEM
"http://vm-winserv08-a.mtri.org:8080/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd";>
<ServiceExceptionReport version="1.1.1" > <ServiceException
code="InvalidBBox">
The request bounding box has zero area: ReferencedEnvelope[-84.778 :
-84.777, 43.956 : 43.956]
</ServiceException></ServiceExceptionReport>
I fixed this by going back in Layer description and typing in higher-precision
bounds. By "fixed" I mean that the WMS worked afterwards. However, I've found
that after a couple days or so I get the ServiceException again, though I've
changed nothing about the Layer description. If I did change the Layer
description in some way (e.g. change the selected Style), I always manually
entered the high-precision bounds again and tested the WMS to see that it
worked.
Here is an example WMS stream that is affected which, note, may be working
because I am still "fixing" these Layers as the problem arises (obviously, I'd
like to not have to re-enter bounding box coordinates every few days):
http://vm-winserv08-a.mtri.org:8080/geoserver/BridgeConditionDSS/wms?service=WMS&version=1.1.0&request=GetMap&layers=BridgeConditionDSS:MannsidingDEM_EastBridge_WGS84&styles=&bbox=-84.7764333996,43.9562142521,-84.7758066003,43.9564145468&width=1032&height=330&srs=EPSG:4326&format=application/openlayers
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
