Move more SLD processing to datastore
-------------------------------------
Key: GEOS-519
URL: http://jira.codehaus.org/browse/GEOS-519
Project: GeoServer
Type: Improvement
Components: WMS
Versions: 1.3.0 RC7
Reporter: Chris Holmes
Assigned to: Justin Deoliveira
Priority: Blocker
Fix For: 1.4
Our SLD processing currently only sends the bounding box to the backend datastore. Oftentimes users have very large datasets, and use SLD to constrain how much of the data is shown, but we're currently just processing everything in Java. This should be done in the backend database if possible, as that's what such things were designed for. This is a blocker for a lot of nice complex feature work, so I'm putting it as a very high priority.
Ideally we'd get a very nice processor to figure out the pre and post SLD processing that needs to be done, much like the current Filter processing, and likely incorporating some of how that works. But we likely can get a number of nice wins, by just optimizing for one 'rule' per SLD, and constrain our users to make their SLD's in a certain way to get the 'fast' way. RobA also had ideas of 'inner' and 'outer' rules, where we'd do the outer rule in the backend. But basically we should seek to do 'more', like check that there's only one filter/rule, and if so process that. Or check for only 'ands', and ignore Ors, with an eye towards eventually having a full processing chain.
This code will involve changes to the renderer, so I'm putting against 1.4, as it will be on geotools dev branch. We're more constrained on 1.3.x/2.1.x
--
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