Hello Luis,
I already tried this approach and bumped into the maximum get parameter string too.
My problem is really that i have a number of layers together with an inlinefeature layer and a layer with a filter on it.
I cannot combine these three types into one geoserver request.
I succeed in:
- getting a GET request with one SLD_BODY parameter (or POST request with StyledLayerDescriptor) containing the normal layers and their (default) styles and the inlinefeaturelayer, but not the one with the filter because the featureLayerConstraints are not implemented
- getting a GET request containing the normal layers and their styles and the filtered layer, but not combined with the inlinefeaturelayer.
but a combination where al three types can be in one request didnt work.
Maybe someone has an odea on this?
Greeting Kris
Gemeentelijke Belastingdienst Den Haag
Laan van Nieuw Oost-Indië 127, 2593 BM Den Haag
Afdeling Systeemontwikkeling
Kristiaan Geusebroek
telefoon : 070 3533954
e-mail : k.geusebroek@anonymised.com
Luis F Silva lfsilva@anonymised.com 11/12/07 4:11 >>>
Kris
Below you will find an example of SLD with two layers.
The text is adjusted for better reading , you may put all together (without spaces).
Just remember that there is a limit to the total size of the variables sent by an http “get” (something close to 1024 bytes, depending on the browser) and you may have to use “remote” SLD description instead.
Hope this helps.
Regards
Fernando.
topp:RRTEST
STATE
Times New Roman
Normal
8
#000000
0.5
0
#000000
1
1
topp:SPTEST
#C0C0C0
1
STATE
Times New Roman
Normal
8
#000000
#000000
1
1
Justin Deoliveira jdeolive@anonymised.com
Sent by: geoserver-users-bounces@lists.sourceforge.net
11/11/2007 20:46
To
K Geusebroek BDGEUSK@anonymised.com
cc
geoserver-users@lists.sourceforge.net
Subject
Re: [Geoserver-users] Using SLD_BODY and a layer in one request.
Working with inline feature layers can be a bit tricky. I actually
don't think it will work the way you want it to. Although I am not an
expert when it comes to inline features and sld in general so if there
are users who have made this work please pipe up. But here goes:
Things behave different depending if you specify the LAYERS parameter
in a request.
When you do include the LAYERS parameter, the sld document is searched
for the layer specified. If found the style from the sld is used,
otherwise the default configured on the server is used.
When you do not specify the LAYERS parameter, all the layers from the
sld are rendered.
So in request A, no layers are specified so all layers from the sld
(including the inline feature layer) are rendered. However in request B
the topp:states layer is specified. Since no such match is found in the
sld nothing from it is rendered, and the default style on the server is
used.
I believe to get the effect you desire you need to include the layers
you want directly into the sld. Something like this:
<NamedLayer>
<Name>topp:states</Name>
</NamedLayer>
The downside to this is that you lose the ability to dynamically
specify the layer in the request. Although if you are building up the
sld into the request this might be acceptable.
Confusing i know... if any of that is still unclear please let me know.
-Justin
K Geusebroek wrote:
> Hello,
>
> I'm using the inlinefeaure functionality to mark a point on a map using
> the SLD_BODY parameter.
> This works if the request is only used for the inlinefeature layer.
> I'm willing to combine another layer in the request,but don't know the
> right syntax.
>
> request A: only the inline feature:
> http://localhost:10880/geoserver/wms?request=getMap&format=image/png&srs=EPSG:28992&bbox=80897.4056870737,454051.457194593,81358.7355861487,454375.879200015&height=718&width=1021&SLD_BODY=%3C%3Fxml+version%3D'1.0'+encoding%3D'UTF-8'%3F%3E%3CStyledLayerDescriptor+version%3D'1.0.0'+xmlns%3Agml%3D'http%3A%2F%2Fwww.opengis.net%2Fgml'+xmlns%3Aogc%3D'http%3A%2F%2Fwww.opengis.net%2Fogc'+xmlns%3D'http%3A%2F%2Fwww.opengis.net%2Fsld'%3E%3CUserLayer%3E%3CName%3EclientData%3C%2FName%3E%3CInlineFeature%3E%3CFeatureCollection%3E%3CfeatureMember%3E%3CLoc%3E%3Cgml%3AType%3ECircle%3C%2Fgml%3AType%3E%3CpointProperty%3E%3Cgml%3APoint+srsName%3D'http%3A%2F%2Fwww.opengis.net%2Fgml%2Fsrs%2Fepsg.xml%2328992'%3E%3Cgml%3Acoordinates+xmlns%3Agml%3D'http%3A%2F%2Fwww.opengis.net%2Fgml'+decimal%3D'.'+cs%3D'%2C'+ts%3D'+'%3E81203%2C454205%3C%2Fgml%3Acoordinates%3E%3C%2Fgml%3APoint%3E%3C%2FpointProperty%3E%3C%2FLoc%3E%3C%2FfeatureMember%3E%3C%2FFeatureCollection%3E%3C%2FInlineFeature%3E%3CLayerFeatureCons
traints%3E%3CFeatureTypeConstraint%3E%3C%2FFeatureTypeConstraint%3E%3C%2FLayerFeatureConstraints%3E%3CUserStyle%3E%3CFeatureTypeStyle%3E%3CRule%3E%3CPointSymbolizer%3E%3CGraphic%3E%3CMark%3E%3CWellKnownName%3E%3Cogc%3ALiteral%3Ecircle%3C%2Fogc%3ALiteral%3E%3C%2FWellKnownName%3E%3CFill%3E%3CCssParameter+name%3D'fill'%3E%3Cogc%3ALiteral%3E%230000FF%3C%2Fogc%3ALiteral%3E%3C%2FCssParameter%3E%3C%2FFill%3E%3C%2FMark%3E%3CSize%3E%3Cogc%3ALiteral%3E10.5%3C%2Fogc%3ALiteral%3E%3C%2FSize%3E%3C%2FGraphic%3E%3C%2FPointSymbolizer%3E%3C%2FRule%3E%3C%2FFeatureTypeStyle%3E%3C%2FUserStyle%3E%3C%2FUserLayer%3E%3C%2FStyledLayerDescriptor%3E
> <http://localhost:10880/geoserver/wms?request=getMap&format=image/png&srs=EPSG:28992&bbox=80897.4056870737,454051.457194593,81358.7355861487,454375.879200015&height=718&width=1021&SLD_BODY=%3C%3Fxml+version%3D'1.0'+encoding%3D'UTF-8'%3F%3E%3CStyledLayerDescriptor+version%3D'1.0.0'+xmlns%3Agml%3D'http%3A%2F%2Fwww.opengis.net%2Fgml'+xmlns%3Aogc%3D'http%3A%2F%2Fwww.opengis.net%2Fogc'+xmlns%3D'http%3A%2F%2Fwww.opengis.net%2Fsld'%3E%3CUserLayer%3E%3CName%3EclientData%3C%2FName%3E%3CInlineFeature%3E%3CFeatureCollection%3E%3CfeatureMember%3E%3CLoc%3E%3Cgml%3AType%3ECircle%3C%2Fgml%3AType%3E%3CpointProperty%3E%3Cgml%3APoint+srsName%3D'http%3A%2F%2Fwww.opengis.net%2Fgml%2Fsrs%2Fepsg.xml%2328992'%3E%3Cgml%3Acoordinates+xmlns%3Agml%3D'http%3A%2F%2Fwww.opengis.net%2Fgml'+decimal%3D'.'+cs%3D'%2C'+ts%3D'+'%3E81203%2C454205%3C%2Fgml%3Acoordinates%3E%3C%2Fgml%3APoint%3E%3C%2FpointProperty%3E%3C%2FLoc%3E%3C%2FfeatureMember%3E%3C%2FFeatureCollection%3E%3C%2FInlineFeature%3E%3CLayerFeatureCon
straints%3E%3CFeatureTypeConstraint%3E%3C%2FFeatureTypeConstraint%3E%3C%2FLayerFeatureConstraints%3E%3CUserStyle%3E%3CFeatureTypeStyle%3E%3CRule%3E%3CPointSymbolizer%3E%3CGraphic%3E%3CMark%3E%3CWellKnownName%3E%3Cogc%3ALiteral%3Ecircle%3C%2Fogc%3ALiteral%3E%3C%2FWellKnownName%3E%3CFill%3E%3CCssParameter+name%3D'fill'%3E%3Cogc%3ALiteral%3E%230000FF%3C%2Fogc%3ALiteral%3E%3C%2FCssParameter%3E%3C%2FFill%3E%3C%2FMark%3E%3CSize%3E%3Cogc%3ALiteral%3E10.5%3C%2Fogc%3ALiteral%3E%3C%2FSize%3E%3C%2FGraphic%3E%3C%2FPointSymbolizer%3E%3C%2FRule%3E%3C%2FFeatureTypeStyle%3E%3C%2FUserStyle%3E%3C%2FUserLayer%3E%3C%2FStyledLayerDescriptor%3E>
>
> request B: adjusted the above request to contain an extra layer (and style):
> http://localhost:10880/geoserver/wms?request=getMap&format=image/png&layers=topp:states&styles=AlternativeStateStyle&srs=EPSG:28992&bbox=80897.4056870737,454051.457194593,81358.7355861487,454375.879200015&height=718&width=1021&SLD_BODY=%3C%3Fxml+version%3D'1.0'+encoding%3D'UTF-8'%3F%3E%3CStyledLayerDescriptor+version%3D'1.0.0'+xmlns%3Agml%3D'http%3A%2F%2Fwww.opengis.net%2Fgml'+xmlns%3Aogc%3D'http%3A%2F%2Fwww.opengis.net%2Fogc'+xmlns%3D'http%3A%2F%2Fwww.opengis.net%2Fsld'%3E%3CUserLayer%3E%3CName%3EclientData%3C%2FName%3E%3CInlineFeature%3E%3CFeatureCollection%3E%3CfeatureMember%3E%3CLoc%3E%3Cgml%3AType%3ECircle%3C%2Fgml%3AType%3E%3CpointProperty%3E%3Cgml%3APoint+srsName%3D'http%3A%2F%2Fwww.opengis.net%2Fgml%2Fsrs%2Fepsg.xml%2328992'%3E%3Cgml%3Acoordinates+xmlns%3Agml%3D'http%3A%2F%2Fwww.opengis.net%2Fgml'+decimal%3D'.'+cs%3D'%2C'+ts%3D'+'%3E81203%2C454205%3C%2Fgml%3Acoordinates%3E%3C%2Fgml%3APoint%3E%3C%2FpointProperty%3E%3C%2FLoc%3E%3C%2FfeatureMember%3E%3C%2FFeatureCollec
tion%3E%3C%2FInlineFeature%3E%3CLayerFeatureConstraints%3E%3CFeatureTypeConstraint%3E%3C%2FFeatureTypeConstraint%3E%3C%2FLayerFeatureConstraints%3E%3CUserStyle%3E%3CFeatureTypeStyle%3E%3CRule%3E%3CPointSymbolizer%3E%3CGraphic%3E%3CMark%3E%3CWellKnownName%3E%3Cogc%3ALiteral%3Ecircle%3C%2Fogc%3ALiteral%3E%3C%2FWellKnownName%3E%3CFill%3E%3CCssParameter+name%3D'fill'%3E%3Cogc%3ALiteral%3E%230000FF%3C%2Fogc%3ALiteral%3E%3C%2FCssParameter%3E%3C%2FFill%3E%3C%2FMark%3E%3CSize%3E%3Cogc%3ALiteral%3E10.5%3C%2Fogc%3ALiteral%3E%3C%2FSize%3E%3C%2FGraphic%3E%3C%2FPointSymbolizer%3E%3C%2FRule%3E%3C%2FFeatureTypeStyle%3E%3C%2FUserStyle%3E%3C%2FUserLayer%3E%3C%2FStyledLayerDescriptor%3E
> <http://localhost:10880/geoserver/wms?request=getMap&format=image/png&layers=topp:states&styles=AlternativeStateStyle&srs=EPSG:28992&bbox=80897.4056870737,454051.457194593,81358.7355861487,454375.879200015&height=718&width=1021&SLD_BODY=%3C%3Fxml+version%3D'1.0'+encoding%3D'UTF-8'%3F%3E%3CStyledLayerDescriptor+version%3D'1.0.0'+xmlns%3Agml%3D'http%3A%2F%2Fwww.opengis.net%2Fgml'+xmlns%3Aogc%3D'http%3A%2F%2Fwww.opengis.net%2Fogc'+xmlns%3D'http%3A%2F%2Fwww.opengis.net%2Fsld'%3E%3CUserLayer%3E%3CName%3EclientData%3C%2FName%3E%3CInlineFeature%3E%3CFeatureCollection%3E%3CfeatureMember%3E%3CLoc%3E%3Cgml%3AType%3ECircle%3C%2Fgml%3AType%3E%3CpointProperty%3E%3Cgml%3APoint+srsName%3D'http%3A%2F%2Fwww.opengis.net%2Fgml%2Fsrs%2Fepsg.xml%2328992'%3E%3Cgml%3Acoordinates+xmlns%3Agml%3D'http%3A%2F%2Fwww.opengis.net%2Fgml'+decimal%3D'.'+cs%3D'%2C'+ts%3D'+'%3E81203%2C454205%3C%2Fgml%3Acoordinates%3E%3C%2Fgml%3APoint%3E%3C%2FpointProperty%3E%3C%2FLoc%3E%3C%2FfeatureMember%3E%3C%2FFeatureColle
ction%3E%3C%2FInlineFeature%3E%3CLayerFeatureConstraints%3E%3CFeatureTypeConstraint%3E%3C%2FFeatureTypeConstraint%3E%3C%2FLayerFeatureConstraints%3E%3CUserStyle%3E%3CFeatureTypeStyle%3E%3CRule%3E%3CPointSymbolizer%3E%3CGraphic%3E%3CMark%3E%3CWellKnownName%3E%3Cogc%3ALiteral%3Ecircle%3C%2Fogc%3ALiteral%3E%3C%2FWellKnownName%3E%3CFill%3E%3CCssParameter+name%3D'fill'%3E%3Cogc%3ALiteral%3E%230000FF%3C%2Fogc%3ALiteral%3E%3C%2FCssParameter%3E%3C%2FFill%3E%3C%2FMark%3E%3CSize%3E%3Cogc%3ALiteral%3E10.5%3C%2Fogc%3ALiteral%3E%3C%2FSize%3E%3C%2FGraphic%3E%3C%2FPointSymbolizer%3E%3C%2FRule%3E%3C%2FFeatureTypeStyle%3E%3C%2FUserStyle%3E%3C%2FUserLayer%3E%3C%2FStyledLayerDescriptor%3E>
> Only the layer from the request appears but wuth the default style, not
> the one from the request.
>
> What am i doing wrong
>
> Greetings Kris
>
>
> Gemeentelijke Belastingdienst Den Haag
> Laan van Nieuw Oost-Indië 127, 2593 BM Den Haag
> Afdeling Systeemontwikkeling
> Kristiaan Geusebroek
> telefoon : 070 3533954
> e-mail : k.geusebroek@anonymised.com
> <mailto:k.geusebroek@anonymised.com>
>
> De disclaimer van toepassing op e-mail van de gemeente Den Haag vindt u op:
>
> http://www.denhaag.nl/disclaimer
>
> !DSPAM:4007,4733230889381431913854!
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
>
> !DSPAM:4007,4733230889381431913854!
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
> !DSPAM:4007,4733230889381431913854!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Esta mensagem, incluindo os seus anexos, contém informações confidenciais destinadas a indivíduo e propósito específicos, e é protegida por lei. Caso você não seja o citado indivíduo, deve apagar esta mensagem. É terminantemente proibida a utilização, acesso, cópia ou divulgação não autorizada das informações presentes nesta mensagem. As informações contidas nesta mensagem e em seus anexos são de responsabilidade de seu autor, não representando idéias, opiniões, pensamentos ou qualquer forma de posicionamento por parte da PST Indústria Eletrônica da Amazônia Ltda.
The information contained in this communication is confidential, is law protected, and is intended only for the business use of the addressee. If you have received this communication in error, please immediately delete it. It’s forbidden the unauthorized use, access, copy or disclose of the information contained in this communication. The content of this message is responsibility of the author, and does not represent ideas, opinions, thoughts or any kind of statement of PST Indústria Eletrônica da Amazônia Ltda.
De disclaimer van toepassing op e-mail van de gemeente Den Haag vindt u op:
http://www.denhaag.nl/disclaimer