Re: [Geoserver-users] Issue with content dependent GetLegendGraphic requests

2023-10-16 Thread Andrea Aime 
Hi Ivan,
nope, I don't see anything else, but may be missing something, can only
dedicate a few minutes to user list support.
Let's see if someone else has better eye :-D

Cheers
Andrea


On Mon, Oct 16, 2023 at 3:36 PM Ivan Pašić  wrote:

> Hi Andrea,
>
> Thanks for the answer.
>
> The thing is, that even if i define BBOX as lon/lat for GetLegendGraphic I
> still have zero values for count matched. Below is an example of the
> modified request (bbox as lon/at and srs instead of crs):
>
>
> http://geoserver.local/geoserver/myworkspace/wms?REQUEST=GetLegendGraphic&VERSION=1.0.0&FORMAT=image/png&LAYER=mylayer&legend_options=countMatched:true&SRS=EPSG:4326&SRCWIDTH=769&SRCHEIGHT=496&BBOX=15.364493754777163,44.042435837063046,15.365523966875822,44.04309992763117
>
> Am I missing something?
>
> Best regards,
> Ivan
>
> On Mon, Oct 16, 2023 at 2:53 PM Andrea Aime <
> andrea.a...@geosolutionsgroup.com> wrote:
>
>> On Mon, Oct 16, 2023 at 10:16 AM Ivan Pašić 
>> wrote:
>>
>>> Here is example of GetMap request that gives properly styled wms
>>> features:
>>>
>>>
>>> http://geoserver.local/geoserver/myworkspace/wms?SERVICE=WMS&;>VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=mylayer&exceptions=application%2Fvnd.ogc.se_inimage&CRS=EPSG%3A4326&WIDTH=769&HEIGHT=496&BBOX=44.042435837063046%2C15.364493754777163%2C44.04309992763117%2C15.365523966875822
>>> 
>>>
>>
>> WMS 1.3, with CRS 4326, expected axis order of BBOX, lat/lon
>>
>>
>>> And here is example of GetLEgendGraphich for same extent that gives all
>>> zero values for countMatched:
>>>
>>>
>>> http://geoserver.local/geoserver/myworkspace/wms?REQUEST=GetLegendGraphic&VERSION=1.0.0&FORMAT=image/png&LAYER=mylayer&legend_options=countMatched:true&CRS=EPSG%3A4326&&SRCWIDTH=796&SRCHEIGHT=496&BBOX=44.042435837063046%2C15.364493754777163%2C44.04309992763117%2C15.365523966875822
>>>
>>
>> WMS 1.1, with  CRS 4326, expected axis order of BBOX, lon/lat. But bbox
>> is the same, instead of being flipped.
>>
>> Cheers
>> Andrea
>>
>> ==
>>
>> 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  339 8844549
>>
>> 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
>>
>

-- 

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  339 8844549

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

Re: [Geoserver-users] Issue with content dependent GetLegendGraphic requests

2023-10-16 Thread Ivan Pašić 
Hi Andrea,

Thanks for the answer.

The thing is, that even if i define BBOX as lon/lat for GetLegendGraphic I
still have zero values for count matched. Below is an example of the
modified request (bbox as lon/at and srs instead of crs):

http://geoserver.local/geoserver/myworkspace/wms?REQUEST=GetLegendGraphic&VERSION=1.0.0&FORMAT=image/png&LAYER=mylayer&legend_options=countMatched:true&SRS=EPSG:4326&SRCWIDTH=769&SRCHEIGHT=496&BBOX=15.364493754777163,44.042435837063046,15.365523966875822,44.04309992763117

Am I missing something?

Best regards,
Ivan

On Mon, Oct 16, 2023 at 2:53 PM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> On Mon, Oct 16, 2023 at 10:16 AM Ivan Pašić 
> wrote:
>
>> Here is example of GetMap request that gives properly styled wms features:
>>
>>
>> http://geoserver.local/geoserver/myworkspace/wms?SERVICE=WMS&;>VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=mylayer&exceptions=application%2Fvnd.ogc.se_inimage&CRS=EPSG%3A4326&WIDTH=769&HEIGHT=496&BBOX=44.042435837063046%2C15.364493754777163%2C44.04309992763117%2C15.365523966875822
>> 
>>
>
> WMS 1.3, with CRS 4326, expected axis order of BBOX, lat/lon
>
>
>> And here is example of GetLEgendGraphich for same extent that gives all
>> zero values for countMatched:
>>
>>
>> http://geoserver.local/geoserver/myworkspace/wms?REQUEST=GetLegendGraphic&VERSION=1.0.0&FORMAT=image/png&LAYER=mylayer&legend_options=countMatched:true&CRS=EPSG%3A4326&&SRCWIDTH=796&SRCHEIGHT=496&BBOX=44.042435837063046%2C15.364493754777163%2C44.04309992763117%2C15.365523966875822
>>
>
> WMS 1.1, with  CRS 4326, expected axis order of BBOX, lon/lat. But bbox is
> the same, instead of being flipped.
>
> Cheers
> Andrea
>
> ==
>
> 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  339 8844549
>
> 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
>
___
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

Re: [Geoserver-users] Issue with content dependent GetLegendGraphic requests

2023-10-16 Thread Andrea Aime 
On Mon, Oct 16, 2023 at 10:16 AM Ivan Pašić  wrote:

> Here is example of GetMap request that gives properly styled wms features:
>
>
> http://geoserver.local/geoserver/myworkspace/wms?SERVICE=WMS&;>VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=mylayer&exceptions=application%2Fvnd.ogc.se_inimage&CRS=EPSG%3A4326&WIDTH=769&HEIGHT=496&BBOX=44.042435837063046%2C15.364493754777163%2C44.04309992763117%2C15.365523966875822
> 
>

WMS 1.3, with CRS 4326, expected axis order of BBOX, lat/lon


> And here is example of GetLEgendGraphich for same extent that gives all
> zero values for countMatched:
>
>
> http://geoserver.local/geoserver/myworkspace/wms?REQUEST=GetLegendGraphic&VERSION=1.0.0&FORMAT=image/png&LAYER=mylayer&legend_options=countMatched:true&CRS=EPSG%3A4326&&SRCWIDTH=796&SRCHEIGHT=496&BBOX=44.042435837063046%2C15.364493754777163%2C44.04309992763117%2C15.365523966875822
>

WMS 1.1, with  CRS 4326, expected axis order of BBOX, lon/lat. But bbox is
the same, instead of being flipped.

Cheers
Andrea

==

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  339 8844549

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
___
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

[Geoserver-users] Latest stable release GeoServer 2.24.0

2023-10-16 Thread Peter Smythe 
 We are very pleased to eventually announce the release of the latest
stable version of GeoServer 2.24.0 (in conjunction with GeoTools 30.0).
The release contains a number of new features, bug fixes and enhancements
so you are encouraged to upgrade to it. Many more details are available in
the related blog posts, please take the time to read them:

GeoServer (
https://geoserver.org/announcements/2023/10/15/geoserver-2-24-0-released.html
)

GeoTools (
https://geotoolsnews.blogspot.com/2023/10/geotools-300-released.html)

Your attention is specifically drawn to the *Upgrade Notes*:

GeoServer strives to maintain backwards compatibility allowing for a smooth
> upgrade experience.
>
> We have one minor change to share in this release:
>
>-
>
>URL Checks: The url check security setting
> is
>now enabled by default.
>
>In GeoServer 2.22.5 and 2.23.2 this setting was available for use, but
>was turned off by default. If you are not yet in a position to upgrade to
>2.24.0 you may wish to enable the recommended setting.
>
>

Peter and Jody

___
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

[Geoserver-users] Issue with content dependent GetLegendGraphic requests

2023-10-16 Thread Ivan Pašić 
Hi,

I'm facing issues with getting content dependent legend graphics for wms
layers.

I have WMS layer with an assigned SLD style with several property-based
rules. When I make GetMap requests all the features are properly styled
based on the defined rules.
If I make the GetLegndGraphic request I also get properly rendered legend.

However, if I add to that GetLegendGraphic request additional query
parameter for legend options like "*&legend_options=countMatched:true*"
then i get zero (0) values for every rule like there are no features that
match that rule. Which is strange because I can clearly see in the GetMap
request that it's properly styled.
As far as I can see I'm setting correct values for "extent", "crs",
"srcwidth", "srcheight" so I'm really not sure where it can go wrong.
Also, if I add "hideEmptyRules:true" then I get empty legend which is
actually expected if already I have zero values for every rule with
"countMatched".


Here is example of GetMap request that gives properly styled wms features:

http://geoserver.local/geoserver/myworkspace/wms?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=mylayer&exceptions=application%2Fvnd.ogc.se_inimage&CRS=EPSG%3A4326&WIDTH=769&HEIGHT=496&BBOX=44.042435837063046%2C15.364493754777163%2C44.04309992763117%2C15.365523966875822

And here is example of GetLEgendGraphich for same extent that gives all
zero values for countMatched:

http://geoserver.local/geoserver/myworkspace/wms?REQUEST=GetLegendGraphic&VERSION=1.0.0&FORMAT=image/png&LAYER=mylayer&legend_options=countMatched:true&CRS=EPSG%3A4326&&SRCWIDTH=796&SRCHEIGHT=496&BBOX=44.042435837063046%2C15.364493754777163%2C44.04309992763117%2C15.365523966875822


I guess I' missing something obvious here so looking forward to hearing
some suggestions.

Thanks a lot.

Best regards,
Ivan
___
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