Optimisation - "illegal bbox"
-----------------------------
Key: GEOS-3217
URL: http://jira.codehaus.org/browse/GEOS-3217
Project: GeoServer
Issue Type: Improvement
Environment: 1.7.5 - windows Vista
Reporter: Jonathan
Assignee: Andrea Aime
Priority: Minor
I have this URL:
http://<host>:8080/geoserver/wcs?request=GetCoverage&version=1.1.1&identifier=j2:bluemarble00&SERVICE=wcs&FORMAT=image/geotiff&boundingbox=-89,0,-180,-90,urn:ogc:def:crs:EPSG::4326
which has an illegal bounbing box. Returns:
"
<ows:Exception exceptionCode="InvalidParameterValue" locator="BoundingBox">
−
<ows:ExceptionText>
illegal bbox, min of dimension 1: -89.0 is greater than max of same dimension: -180.0
</ows:ExceptionText>
</ows:Exception>
"
Which is fine because it's probably wrong (I'm having to use trial and error).
However, the dataset I'm using this query on it on is about 1.7gigs of pyramids (via plugin) from http://etch.opengeo.org/bluemarble/ .
I noticed it takes about 8 (eight) seconds to process the query before realising the bbox is illegal. I changed the layer it was referencing to a smaller, 180mb landsat scene and it responds /instantly/ telling me the bbox is illegal.
May I therefore suggest that things like checking for the legality and validity of the URL be done before it tries to access the dataset, even to confirm the dataset is real - at least, this result implies that isn't the case at present.
--
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