We have a layer with +- 350K records and the point features are rendered based on 2 attributes: 1 has 10 distinct values and defines the symbol (mark), the other one has 12 distinct values and defines the color.
Now we have 1 big SLD with +- 3200 lines and because of its size the SLD is hard to maintain. That's why we want to change and are looking for alternatives. I tested already 2 alternatives: using recode function and storing symbol + color in spatial table. Both have its pros and cons. But maybe there are a few others. In an ideal world using this SLD (or SLDs) it's possible to: - render the features correctly (of course) - render features which are unknown with a specific rendition (similar to the ElseIf rule) - create different legends: 1 based on symbol, the other one on color (because a legend with 120 different items - as with our current SLD - is not really clarifying) -- View this message in context: http://osgeo-org.1560.x6.nabble.com/SLD-Best-practices-tp5067939.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
