|
Simon Hartley created an issue |
Spatial filter missing from SQL when a rendering transform style is used |
Issue Type: |
|
---|---|
Affects Versions: |
2.9.0 |
Assignee: |
Unassigned |
Attachments: |
transform.sld |
Created: |
18/Jul/16 5:11 PM |
Priority: |
|
Reporter: |
Here’s a SQL View PostGIS layer I’m calling “test”: select * FROM (VALUES (ST_SetSRID(ST_MakePoint(0,0),4326), 20)) AS v(location, temperature) Here’s the query I use to render it: When I set the built-in “point” style to be the default, the following SQL is in the log as I expect: SELECT encode(ST_AsBinary(CASE WHEN ST_HasArc(“location”) THEN “location” ELSE ST_Simplify(ST_Force2D(“location”), 0.02217446788201656) END),‘base64’) as “location” FROM (select * FROM (VALUES (ST_SetSRID(ST_MakePoint(0,0),4326), 20)) AS v(location, temperature) When I use my Rendering Transformation style (attached), I get the following SQL in the log (without a spatial filter): I didn’t have this problem when I was using GeoServer 2.2.5 and the lack of spatial filter is slowing the transform hugely when I use a real-world SQL layer. |
This message was sent by Atlassian JIRA (v1000.148.3#100005-sha1:53b5f3f) |
|