[Geoserver-users] SLD_BODY ignored on SLD Transformation

GeoServer GeoServer User
1

Hello,

I realized the SLD_BODY Option in a WMS request is ignored, when using a SLD
Transformation function:
In my example I pass a valid SLD as a string to Geoserver.

On the server geoserver gets this parameters, but for rendering the passed
SLD is ignored. Geoserver uses the default associated SLD.

For me this looks like a bug.

You can see the request on this link http://nopaste.info/1c0aa1d08f.html
<http://nopaste.info/1c0aa1d08f.html&gt;

regards Markus

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/SLD-BODY-ignored-on-SLD-Transformation-tp5047629.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

2

On Wed, Apr 17, 2013 at 2:57 PM, markusin <markus.innerebner@anonymised.com>wrote:

Hello,

I realized the SLD_BODY Option in a WMS request is ignored, when using a
SLD
Transformation function:
In my example I pass a valid SLD as a string to Geoserver.

On the server geoserver gets this parameters, but for rendering the passed
SLD is ignored. Geoserver uses the default associated SLD.

For me this looks like a bug.

Pay attention, if you are using both layers and SLD_BODY you enter in
"library mode",
and you might get surprising results.
Search the archives of this ml for a discussion about the SLD library mode,
it popped up
a few times over the years

Cheers
Andrea

--

GeoServer training in Milan, 6th & 7th June 2013! Visit
http://geoserver.geo-solutions.it for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

3

HI Andrea,

thanks for the explanation. I read on the page
http://docs.geoserver.org/latest/en/user/styling/sld-working.html
<http://docs.geoserver.org/latest/en/user/styling/sld-working.html&gt;
and got the problem!

without specifying the layer geoserver chooses as layer the value in the
element:
NamedLayer/Name

So now I have to find out in Openlayers, how not to set the layer in such a
request.

Thanks again for your help

Markus

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/SLD-BODY-ignored-on-SLD-Transformation-tp5047629p5047736.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

4

On Wed, Apr 17, 2013 at 6:51 PM, markusin <markus.innerebner@anonymised.com>wrote:

HI Andrea,

thanks for the explanation. I read on the page
http://docs.geoserver.org/latest/en/user/styling/sld-working.html
<http://docs.geoserver.org/latest/en/user/styling/sld-working.html&gt;
and got the problem!

without specifying the layer geoserver chooses as layer the value in the
element:
NamedLayer/Name

So now I have to find out in Openlayers, how not to set the layer in such a
request.

Or, you set the user style as default (I believe it's
<IsDefault>1</IsDefault>)
or also add &styles=... and use the same name as your user style there

Cheers
Andrea

--

GeoServer training in Milan, 6th & 7th June 2013! Visit
http://geoserver.geo-solutions.it for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

5

Hi Andrea,

Nevertheless this behavior in Geoserver sounds a bit weird: on the one hand
in a WMS request the parameters LAYERS is required, but on the other hand
when adding the additional parameter SLD_BODY, the parameter LAYERS should
not be specified. It is a bit contradictory, isn't it?
Wouldn't it be better to define as default behavior, whenever SLD_BODY is
specified it will overwrite the standard style?

regards Markus

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/SLD-BODY-ignored-on-SLD-Transformation-tp5047629p5047777.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

6

Library mode is certainly somewhat complex - at least I found it tricky to document! Hopefully the following will be useful:

http://docs.geoserver.org/stable/en/user/styling/sld-working.html#library-mode

···

On Wed, Apr 17, 2013 at 8:43 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

On Wed, Apr 17, 2013 at 2:57 PM, markusin <markus.innerebner@anonymised.com> wrote:

Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Hello,

I realized the SLD_BODY Option in a WMS request is ignored, when using a SLD
Transformation function:
In my example I pass a valid SLD as a string to Geoserver.

On the server geoserver gets this parameters, but for rendering the passed
SLD is ignored. Geoserver uses the default associated SLD.

For me this looks like a bug.

Pay attention, if you are using both layers and SLD_BODY you enter in “library mode”,
and you might get surprising results.
Search the archives of this ml for a discussion about the SLD library mode, it popped up
a few times over the years

Cheers
Andrea

–

==
GeoServer training in Milan, 6th & 7th June 2013! Visit http://geoserver.geo-solutions.it for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

7

On Wed, Apr 17, 2013 at 10:23 PM, markusin
<markus.innerebner@anonymised.com>wrote:

Hi Andrea,

Nevertheless this behavior in Geoserver sounds a bit weird: on the one hand
in a WMS request the parameters LAYERS is required, but on the other hand
when adding the additional parameter SLD_BODY, the parameter LAYERS should
not be specified. It is a bit contradictory, isn't it?

SLD_BODY is part of the SLD spec, it's not the first time an extension
contradicts the base
spec. It has happened in CSW as well several times.

Wouldn't it be better to define as default behavior, whenever SLD_BODY is
specified it will overwrite the standard style?

We don't make the standards, OGC does. If everybody starts implementing
them their own way
caos will ensue.
Look at the axis order in WFS 1.1, some servers keep everything east/north,
some everything north/east, some follow the EPSG database order, some flip
the axis
on output but demand that spatial filters are provided in east/noth mode...
it's complete caos,
really hard to write a client that works with all the servers (we are
adding configurable "axis order"
modes to the WFS client in GeoTools for both GML output and spatial filters
to try and cope
with at least some of the servers out there).

Cheers
Andrea

--

GeoServer training in Milan, 6th & 7th June 2013! Visit
http://geoserver.geo-solutions.it for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------