I'm testing out WCS in Geoserver 1.5.0 beta 2 (.war version). Using
the "Arc_Sample" coverage I noticed that my getCoverage requests must include
exactly the same grid envelope as listed in the describeCoverage response.
It's my understanding that I *should* be able to request a different resolution
of the data by specifying a different grid envelope in my getCoverage
requests.
Have I misunderstood something? Is that feature available in beta 2?
Did you get the epsg-hsql exception sorted out? If you provide a sample request I can try this against geoserver trunk; ... there is a checkout here somewhere.
Jody
Hi devs,
I'm testing out WCS in Geoserver 1.5.0 beta 2 (.war version). Using the "Arc_Sample" coverage I noticed that my getCoverage requests must include exactly the same grid envelope as listed in the describeCoverage response. It's my understanding that I *should* be able to request a different resolution of the data by specifying a different grid envelope in my getCoverage requests.
Have I misunderstood something? Is that feature available in beta 2?
I'm testing out WCS in Geoserver 1.5.0 beta 2 (.war version). Using the "Arc_Sample" coverage I noticed that my getCoverage requests must include exactly the same grid envelope as listed in the describeCoverage response. It's my understanding that I *should* be able to request a different resolution of the data by specifying a different grid envelope in my getCoverage requests.
You're indeed right, it should and it's a bug.
If you can, provide more details (requests, sample data, stack traces).
WCS is beta, and I guess there are issues around.
If you don't find the issue in WCS, you can assume it's brand new and
that we may need detailed information on how to reproduce it.
Using the demo WCS getCoverage request for Arc_Sample works fine. I get the
expected tiff response. If I alter the request to have a different GridEnvelope
like this:
... then the request fails. It's my understanding that this change will cause
the image to be resampled. My tomcat log of the problem is below. It's
possible that I'm just misunderstanding the purpose of GridEnvelope. Let me
know if you think that's the case!
Jan 23, 2007 9:34:35 AM org.vfny.geoserver.util.requests.XmlCharsetDetector
getXmlEncoding
WARNING: Invalid(?) XML declaration: <!-- P.
Jan 23, 2007 9:34:35 AM
org.vfny.geoserver.util.requests.readers.DispatcherXmlReader getRequest
INFO: getting request type from
org.vfny.geoserver.util.requests.DispatcherHandler@anonymised.com
Jan 23, 2007 9:34:35 AM org.vfny.geoserver.servlets.AbstractService doService
INFO: handling request:
Request: null
coverage:nurc:Arc_Sample
output format:TIFF
version:1.0.0
envelope:Env[9.420000076293944 : 11.819999694824217, 42.20000076293945 :
43.90000049273173]
interpolation:null
Jan 23, 2007 9:34:35 AM org.vfny.geoserver.servlets.AbstractService doService
WARNING: service exception while executing request:
Request: null
coverage:nurc:Arc_Sample
output format:TIFF
version:1.0.0
envelope:Env[9.420000076293944 : 11.819999694824217, 42.20000076293945 :
43.90000049273173]
interpolation:null
cause: java.lang.IllegalArgumentException: The operation name parameter may not
be null.
Jan 23, 2007 9:34:35 AM org.vfny.geoserver.wcs.WcsException getXmlResponse
WARNING: encountered error: java.lang.IllegalArgumentException: The operation
name parameter may not be null.
Quoting banders@anonymised.com:
Hi devs,
I'm testing out WCS in Geoserver 1.5.0 beta 2 (.war version). Using
the "Arc_Sample" coverage I noticed that my getCoverage requests must include
exactly the same grid envelope as listed in the describeCoverage response.
It's my understanding that I *should* be able to request a different
resolution
of the data by specifying a different grid envelope in my getCoverage
requests.
Have I misunderstood something? Is that feature available in beta 2?