Thank you for your reply. I am still having problems, though, which can almost
guarantee fall under the “user error” category.
I have now placed the two rules (I actually have more than two, but in my
snippet below I have simplified it) into the same <FeatureTypeStyle>. I have
added <VendorOption name="sortBy"> and set it to the field gs and specified
descending order.
If I understand it correctly, this should cause the values PA to paint before
LA since it is descending. I have also tried doing this on a numeric field, as
well.
Again, any guidance would be greatly appreciated. And thanks again for your
assistance. I know I am at least on the right track.
<FeatureTypeStyle>
<Rule>
<Name>Type 1</Name>
<Title>Type 1</Title>
<MaxScaleDenominator>750000</MaxScaleDenominator>
<ogc:Filter>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>gs</ogc:PropertyName>
<ogc:Literal>LA</ogc:Literal>
</ogc:PropertyIsEqualTo>
</ogc:Filter>
<PointSymbolizer>
<Graphic>
<ExternalGraphic>
<OnlineResource xlink:type="simple" xlink:href="UT/LA.svg" />
<Format>image/svg+xml</Format>
</ExternalGraphic>
<Size>
<ogc:Literal>10</ogc:Literal>
</Size>
</Graphic>
</PointSymbolizer>
</Rule>
<Rule>
<Name>Type 2</Name>
<Title>Type 2 type</Title>
<MaxScaleDenominator>750000</MaxScaleDenominator>
<ogc:Filter>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>gs</ogc:PropertyName>
<ogc:Literal>PA</ogc:Literal>
</ogc:PropertyIsEqualTo>
</ogc:Filter>
<PointSymbolizer>
<Graphic>
<ExternalGraphic>
<OnlineResource xlink:type="simple" xlink:href="UT/PA.svg" />
<Format>image/svg+xml</Format>
</ExternalGraphic>
<Size>
<ogc:Literal>16</ogc:Literal>
</Size>
</Graphic>
</PointSymbolizer>
</Rule>
<VendorOption name="sortBy">gs D</VendorOption>
</FeatureTypeStyle>
Todd
Todd Fagin
Oklahoma Natural Heritage Inventory/
Oklahoma Biological Survey
From: Andrea Aime [mailto:andrea.a...@geo-solutions.it]
Sent: Saturday, September 1, 2018 6:18 AM
To: Fagin, Todd D. <tfa...@ou.edu>
Cc: GeoServer Mailing List List <geoserver-users@lists.sourceforge.net>
Subject: Re: [Geoserver-users] SLD drawing order
Best to use the vendor extension to do data sorting in that case:
http://docs.geoserver.org/stable/en/user/styling/sld/extensions/z-order/syntax.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.geoserver.org_stable_en_user_styling_sld_extensions_z-2Dorder_syntax.html&d=DwMFaQ&c=qKdtBuuu6dQK9MsRUVJ2DPXW6oayO8fu4TfEHS8sGNk&r=5fn9Z6IrrvMEqCEFIvviYg&m=mg-2EHKKYH5qOX0HWWQCbB8mrSjKablJ0GV2LV4ytB8&s=conAGuqUM-IHdY2ySSF3neH0x2bLCNrvk6_p6RwaQ6Y&e=>
Cheers
Andrea
On Fri, Aug 31, 2018 at 11:57 PM Fagin, Todd D.
<tfa...@ou.edu<mailto:tfa...@ou.edu>> wrote:
Greetings,
I know this is an issue that has been addressed before, but we are having some
issues and am hoping for guidance.
We have a point layer that has, in at least one instance, two points at the
exact some location. Optimally, if would be best if both symbols rendered in a
“stacked” fashion. However, only one of the features is showing. The next best
option would be to prioritize the point drawn based on attribute value. We have
used the <FeatureTypeStyle> tag, but the rendering is still not placing
priority as we have indicated. I have a snippet of the SLD below.
Any suggestions would be greatly appreciated.
<FeatureTypeStyle>
<Rule>
<Name>Type 1</Name>
<Title>Type 1</Title>
<MaxScaleDenominator>750000</MaxScaleDenominator>
<ogc:Filter>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>gs</ogc:PropertyName>
<ogc:Literal>LA</ogc:Literal>
</ogc:PropertyIsEqualTo>
</ogc:Filter>
<PointSymbolizer>
<Graphic>
<ExternalGraphic>
<OnlineResource xlink:type="simple" xlink:href="UT/LA.svg" />
<Format>image/svg+xml</Format>
</ExternalGraphic>
<Size>
<ogc:Literal>10</ogc:Literal>
</Size>
</Graphic>
</PointSymbolizer>
</Rule>
</FeatureTypeStyle>
<FeatureTypeStyle>
<Rule>
<Name>Type 2</Name>
<Title>Type 2</Title>
<MaxScaleDenominator>750000</MaxScaleDenominator>
<ogc:Filter>
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>gs</ogc:PropertyName>
<ogc:Literal>PA</ogc:Literal>
</ogc:PropertyIsEqualTo>
</ogc:Filter>
<PointSymbolizer>
<Graphic>
<ExternalGraphic>
<OnlineResource xlink:type="simple" xlink:href="UT/PA.svg" />
<Format>image/svg+xml</Format>
</ExternalGraphic>
<Size>
<ogc:Literal>16</ogc:Literal>
</Size>
</Graphic>
</PointSymbolizer>
</Rule>
</FeatureTypeStyle>
Thank you,
Todd
Todd Fagin
Oklahoma Natural Heritage Inventory/
Oklahoma Biological Survey
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
http://sdm.link/slashdot<https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DwMFaQ&c=qKdtBuuu6dQK9MsRUVJ2DPXW6oayO8fu4TfEHS8sGNk&r=5fn9Z6IrrvMEqCEFIvviYg&m=mg-2EHKKYH5qOX0HWWQCbB8mrSjKablJ0GV2LV4ytB8&s=EQG0w2axnn6zztGqrRx0e6J3KmYzqKd41fHj5YbGiB8&e=>_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ianturton.com_talks_foss4g.html-23_&d=DwMFaQ&c=qKdtBuuu6dQK9MsRUVJ2DPXW6oayO8fu4TfEHS8sGNk&r=5fn9Z6IrrvMEqCEFIvviYg&m=mg-2EHKKYH5qOX0HWWQCbB8mrSjKablJ0GV2LV4ytB8&s=yjHCDyQkIQ7J5easLh7dbfgbLnAayR1YXeNb7tSV6_M&e=>
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__geoserver.org_comm_userlist-2Dguidelines.html&d=DwMFaQ&c=qKdtBuuu6dQK9MsRUVJ2DPXW6oayO8fu4TfEHS8sGNk&r=5fn9Z6IrrvMEqCEFIvviYg&m=mg-2EHKKYH5qOX0HWWQCbB8mrSjKablJ0GV2LV4ytB8&s=POrndqWf1-vAIdTA138gdteve_tVclMN4jLi5xvUaD0&e=>
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_geoserver_geoserver_wiki_Successfully-2Drequesting-2Dand-2Dintegrating-2Dnew-2Dfeatures-2Dand-2Dimprovements-2Din-2DGeoServer&d=DwMFaQ&c=qKdtBuuu6dQK9MsRUVJ2DPXW6oayO8fu4TfEHS8sGNk&r=5fn9Z6IrrvMEqCEFIvviYg&m=mg-2EHKKYH5qOX0HWWQCbB8mrSjKablJ0GV2LV4ytB8&s=iwG6N_PPYCtX-cywXDk-gDfBVqpJ77e6TgosFVLQdVc&e=>
Geoserver-users@lists.sourceforge.net<mailto:Geoserver-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/geoserver-users<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_geoserver-2Dusers&d=DwMFaQ&c=qKdtBuuu6dQK9MsRUVJ2DPXW6oayO8fu4TfEHS8sGNk&r=5fn9Z6IrrvMEqCEFIvviYg&m=mg-2EHKKYH5qOX0HWWQCbB8mrSjKablJ0GV2LV4ytB8&s=0jz9p9CKop6LzFu2bWIhwfWhXI0Go-GrGrElJzGUGHA&e=>
--
Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V<https://urldefense.proofpoint.com/v2/url?u=http-3A__goo.gl_it488V&d=DwMFaQ&c=qKdtBuuu6dQK9MsRUVJ2DPXW6oayO8fu4TfEHS8sGNk&r=5fn9Z6IrrvMEqCEFIvviYg&m=mg-2EHKKYH5qOX0HWWQCbB8mrSjKablJ0GV2LV4ytB8&s=KFYkfatz-ru2xRnAgxG7rqZMwfwHt9hn4H-2BN2epxw&e=>
for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions
S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax:
+39 0584 1660272 mob: +39 339 8844549
http://www.geo-solutions.it<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.geo-2Dsolutions.it&d=DwMFaQ&c=qKdtBuuu6dQK9MsRUVJ2DPXW6oayO8fu4TfEHS8sGNk&r=5fn9Z6IrrvMEqCEFIvviYg&m=mg-2EHKKYH5qOX0HWWQCbB8mrSjKablJ0GV2LV4ytB8&s=O2jVQHfZ5bF322VugnIvTSxp7DMPBoReE33kAi3qTEc&e=>
http://twitter.com/geosolutions_it<https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_geosolutions-5Fit&d=DwMFaQ&c=qKdtBuuu6dQK9MsRUVJ2DPXW6oayO8fu4TfEHS8sGNk&r=5fn9Z6IrrvMEqCEFIvviYg&m=mg-2EHKKYH5qOX0HWWQCbB8mrSjKablJ0GV2LV4ytB8&s=9zoGl05upmL6z76g5h4HaZ_AzyDOLl4wacyXuIBcOAk&e=>
------------------------------------------------------- Con riferimento alla
normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento
generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza
inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è
un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo
scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo,
ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene
notizia. This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by European
Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or
the information herein by anyone other than the intended recipient is
prohibited. If you have received this email by mistake, please notify us
immediately by telephone or e-mail.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
