-
-
Notifications
You must be signed in to change notification settings - Fork 375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WMS-dimensions on 6.5-dev not working properly #5032
Comments
Got it. @deduikertjes, any chance you have a small test case available? Steve |
Hi Steve, I'm happy to provide a test case. What would you like to have? Mapfile + data? Or only an URL from a service. MArco On 12-11-14 17:13, Steve Lime wrote:
|
Ideally I'd need a mapfile, data and sample URL. If you can describe the data contents maybe I can fashion a similar dataset or perhaps there's already a suitable candidate in the regression tests suite. Steve From: deduikertjes [notifications@github.com] Hi Steve, I'm happy to provide a test case. What would you like to have? Mapfile + data? Or only an URL from a service. MArco On 12-11-14 17:13, Steve Lime wrote:
— |
@deduikertjes, I just patched master. Can you give it a try? Steve BTW Thanks for the test case! |
It was obvious what the problem was so I'm confident the issue has been fixed. Closing for now... |
Hi,
I'm using WMS-dimensions as described on http://mapserver.org/ogc/wms_dimension.html. This is working fine in mapserver 6.4.1.
When using WMS Dimensions on 6.5-dev (checked out from GitHub on 5-11-2014) I get the following exception report when doing a getmap request with paramters like: &DIM_QUALITY=0.9/1&DIM_LINEAR=-1/0,0/1:
msDrawMap(): Image handling error. Failed to draw layer named 'jan2014_low'.
msPostGISLayerWhichShapes(): Query error. Error executing query: ERROR: operator does not exist: >= numeric
LINE 1: ...32.505600397 6790506.21879132))',900913) and (((( >= 0.90000...
^
HINT: No operator matches the given name and argument type(s). You might need to add explicit type casts.
MArco
The text was updated successfully, but these errors were encountered: