On Sun, Dec 11, 2016 at 10:21 PM, Martin Davis wrote:
> Yes, I tried this. It ate the s though, so not ideal (possibly
> because using it from Windows/curl). If that is the solution then I will
> try harder to see if formatting can be preserved.
>
> Anyway, the same thing happens when using the
Yes, I tried this. It ate the s though, so not ideal (possibly because
using it from Windows/curl). If that is the solution then I will try
harder to see if formatting can be preserved.
Anyway, the same thing happens when using the web editor.
Seems to me a better behaviour would be to inject m
Those are the defaults - the SLD spec gives more examples e.g. points
default to a gray square IIRC.
Ian
On 8 December 2016 at 18:52, Martin Davis wrote:
> I noticed some odd behaviour in GS 2.9.1. I load a style via the REST API
> which has the following in a PolygonSymbolizer:
>
>
>
> #000
On Thu, Dec 8, 2016 at 7:52 PM, Martin Davis wrote:
> It looks like GeoServer is deleting parameter elements with "default"
> values (although I'm not aware that there is any such thing as default
> values for SLD entries).
>
See the "raw" parameter description in the REST API reference here:
h
I noticed some odd behaviour in GS 2.9.1. I load a style via the REST API
which has the following in a PolygonSymbolizer:
#00
1
1.0
When I view the style in the Style Editor panel the following is displayed:
This is also what is stored in the data di
