On Sat, Sep 23, 2017 at 2:01 PM, Stefan Overkamp <
stefan.overk...@gisworks.info> wrote:
> Maybe a optional metadata @name (in addition to @title and @abstract)
> would be a solution.
>
Maybe... but remember rules are going to get mixed and some rules might be
missing @name.
So basically the same
Many thanks for your explanation.
I'm working on a javascript client that uses REST to get layergroups,
layers and the SLD to get the rules.
Then configuring a tree with layers and their rules and get Legend-Icons
for each rule.
It is planned that users can change the rules visibility.
Maybe a op
On Fri, Sep 22, 2017 at 1:36 PM, Stefan Overkamp <
stefan.overk...@gisworks.info> wrote:
> Hi geoserver-community,
>
> creating a style in CSS-Format translates the style to sld-XML.
>
> The documentation states:
> The SLD Name for a rule is autogenerated based on the filters from the CSS
> rules
Hi geoserver-community,
creating a style in CSS-Format translates the style to sld-XML.
The documentation states:
The SLD Name for a rule is autogenerated based on the filters from the
CSS rules that combined to form it, for aid in troubleshooting.
Instead of this, there is no sld name property
