Hi Paul,
I'm guessing you're working off this page
(http://docs.geoserver.org/stable/en/user/styling/sld-extensions/rendering-transform.html)
already. I can't find anything else so my only suggestion would be to look in
the code.
Looking in the repository, I see this is the only place that "PointStacker"
appears -
https://github.com/geoserver/geoserver/blob/bf0345d228111c15aeff6f7c1bc87b4ed230af96/src/extension/wps/wps-core/src/main/java/org/geoserver/wps/DeprecatedProcessFactory.java
(Ctrl-F for it within the page), and I'd guess that the surrounding items are
also potential transformations (but I don't do Java so I'm likely about to be
corrected...).
The other option is to take a look in the test SLD's here:
https://github.com/geoserver/geoserver/tree/338f0d8c3744c086168530679fcea0a8a666f249/src/wms/src/test/resources/org/geoserver/wms/wms_1_1_1
- those seem to be the only two places in the code-base that the term
"PointStacker" appears.
Cheers,
Jonathan
---- On Thu, 04 Aug 2016 13:30:11 +0100 Paul
Wittle<p.wit...@dorsetcc.gov.uk> wrote ----
Hello,
Is there a complete list online which tells me which GeoServer WPS functions
can be called from within SLD?
I have also been wondering about the PointStacker as I have a layer with three
categories of points in a single layer. I'm aware the function doesn't have a
group by function and that gs:Query can't be chained so I don't think it is
currently possible but ideally I want to have multiple <FeatureTypeStyle>
entries with the point stacker filtered by category. This would allow me to in
effect render the three categories as separate colours and ensure that the
categories are not grouped together.
This leads me to a general question of preference. I'd be interested to hear
if you think 1) layers should be styled by attribute and filtered (i.e. the
three categories in one layer) or 2) they should be split into views in the
database (or sql_views in GeoServer) and presented as three layers?
Currently our group tend to us the later option but having started with ESRI
products I tended to think the first option was better, after all, three types
of road are all roads so they should be in the roads layer. It seems however
that you are forced down the route of option two here if you want to use
PointStacker.
Best Regards,
Paul
"This e-mail is intended for the named addressee(s) only and may contain
information about individuals or other sensitive information and should be
handled accordingly. Unless you are the named addressee (or authorised to
receive it for the addressee) you may not copy or use it, or disclose it to
anyone else. If you have received this email in error, kindly disregard the
content of the message and notify the sender immediately. Please be aware that
all email may be subject to recording and/or monitoring in accordance with
relevant legislation."
------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
