Hi Andrea,

I just tested with below version, it seems  as you said MIN and MAX only
works. Received same error since I am using shape files as backend unable
to get what I want, with mysql / postgres I would have create sql layer.


   - GeoServer Version2.21-SNAPSHOT
   - Git Revisionade1dd70a9861ccd8c13ae299e670d447a8ac81c
   - Build Date15-Nov-2021 16:13


On Thu, Nov 18, 2021 at 3:43 PM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> Hmm.. not sure there is a process that will work for you, on a stable
> version of GeoServer.
> The Aggregate process can do counts, but in order to paint a map, you need
> to aggregate
> on the geometry as well (otherwise it's not part of the aggregation
> output), which does not work.
> It was solved recently on the developer series, not sure there will be a
> backport to stable though (a large change was required):
>
> https://osgeo-org.atlassian.net/browse/GEOT-7015
>
> You can try out a nightly build of the developer series and see if that
> works for you:
> http://geoserver.org/release/main/
>
> Cheers
> Andrea
>
>
> On Thu, Nov 18, 2021 at 10:59 AM Akshay Hegde <akshay.k.he...@gmail.com>
> wrote:
>
>> Hi Andrea,
>>
>> Thanks for reply.
>>
>> I was attempting below, as  you can see I was attempting to count
>> stations at specific location ( group by latitude, longitude ), Kindly find
>> attached screenshot. similar to SQL
>>
>> select count(1) from sometable group by latitude, longitude.
>>
>>    <Transformation>
>>           <ogc:Function name="vec:GroupCandidateSelection">
>>             <ogc:Function name="parameter">
>>               <ogc:Literal>data</ogc:Literal>
>>             </ogc:Function>
>>             <ogc:Function name="parameter">
>>               <ogc:Literal>operationAttribute</ogc:Literal>
>>               <ogc:Literal>stations</ogc:Literal>
>>             </ogc:Function>
>>             <ogc:Function name="parameter">
>>               <ogc:Literal>aggregation</ogc:Literal>
>>               <ogc:Literal>COUNT</ogc:Literal>
>>             </ogc:Function>
>>             <ogc:Function name="parameter">
>>               <ogc:Literal>groupingAttributes</ogc:Literal>
>>               <ogc:Literal>latitude</ogc:Literal>
>>               <ogc:Literal>longitude</ogc:Literal>
>>             </ogc:Function>
>>           </ogc:Function>
>>         </Transformation>
>>
>>
>>
>>
>> On Thu, Nov 18, 2021 at 2:46 PM Andrea Aime <
>> andrea.a...@geosolutionsgroup.com> wrote:
>>
>>> As per process documentation (look at the DescribeProcess output):
>>>
>>> "The aggregate operation to be computed, it can be MAX or MIN"
>>>
>>> This process selects for each group just one feature, the one that has
>>> either the min or the max value of a given attribute
>>> sum or count make no sense in that context.
>>>
>>> Cheers
>>> Andrea
>>>
>>>
>>> On Thu, Nov 18, 2021 at 6:26 AM Akshay Hegde <akshay.k.he...@gmail.com>
>>> wrote:
>>>
>>>>
>>>> I had gone through
>>>>
>>>>
>>>> https://docs.geoserver.org/stable/en/user/styling/sld/extensions/rendering-transform.html#contour-extraction
>>>>
>>>> Unfortunately below transformation with COUNT and SUM never works. It
>>>> only  works with MIN and MAX function.
>>>>
>>>> Is there any resolution ? my aim is to get count, by grouping few
>>>> attributes and to have colored marker based on count value.
>>>>
>>>> example
>>>>
>>>> - count < 100 red color
>>>> - count > 100   and count < 1000 green
>>>> - count > 1000
>>>>
>>>>  <Transformation>
>>>>                   <ogc:Function name="vec:GroupCandidateSelection">
>>>>                       <ogc:Function name="parameter">
>>>>                           <ogc:Literal>data</ogc:Literal>
>>>>                       </ogc:Function>
>>>>                       <ogc:Function name="parameter">
>>>>                           <ogc:Literal>operationAttribute</ogc:Literal>
>>>>                           <ogc:Literal>st:numericAttribute</ogc:Literal>
>>>>                       </ogc:Function>
>>>>                       <ogc:Function name="parameter">
>>>>                           <ogc:Literal>aggregation</ogc:Literal>
>>>>                           <ogc:Literal>COUNT</ogc:Literal>
>>>>                       </ogc:Function>
>>>>                       <ogc:Function name="parameter">
>>>>                           <ogc:Literal>groupingAttributes</ogc:Literal>
>>>>
>>>> <ogc:Literal>st:inferredAttribute</ogc:Literal>
>>>>
>>>> <ogc:Literal>st:inferredAttribute2</ogc:Literal>
>>>>                       </ogc:Function>
>>>>                   </ogc:Function>
>>>>   </Transformation>
>>>> --
>>>> _______________________________________________
>>>> 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
>>>>
>>>
>>>
>>> --
>>>
>>> Regards,
>>>
>>> Andrea Aime
>>>
>>> ==
>>> GeoServer Professional Services from the experts!
>>>
>>> Visit http://bit.ly/gs-services-us for more information.
>>> ==
>>>
>>> Ing. Andrea Aime
>>> @geowolf
>>> Technical Lead
>>>
>>> GeoSolutions Group
>>> phone: +39 0584 962313
>>>
>>> fax:     +39 0584 1660272
>>>
>>> mob:   +39  333 8128928
>>>
>>> https://www.geosolutionsgroup.com/
>>>
>>> http://twitter.com/geosolutions_it
>>>
>>> -------------------------------------------------------
>>>
>>> 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
>>>
>>
>>
>> --
>>
>> <https://about.me/akshay.k.hegde?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb>
>> Akshay Hegde
>> about.me/akshay.k.hegde
>> <https://about.me/akshay.k.hegde?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb>
>>
>
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax:     +39 0584 1660272
>
> mob:   +39  333 8128928
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> 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
>


-- 
<https://about.me/akshay.k.hegde?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb>
Akshay Hegde
about.me/akshay.k.hegde
<https://about.me/akshay.k.hegde?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb>
_______________________________________________
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

Reply via email to