Re: [Geoserver-users] Cache Geoserver 2.23.1. Row - Column order.

[Andrea Aime]

Hi Miguel,
the slipppy map definition is not coming from OGC/WMTS, it's coming from
the likes of OpenStreetMap and uses a z/x/y order. For reference:

https://en.wikipedia.org/wiki/Tiled_web_map
https://wiki.openstreetmap.org/wiki/Slippy_map

The current code does not allow to generate a z/y/x layout, but it would be
possible to get it
with small code modifications in GeoWebCache.

A note about WMTS... in both the KVP and RESTful implementations the URLs
have
named, position independent parameters that a client has to follow and
replace.
For example, this is the URl template for a restful KVP:

https://testServer/geoserver/gwc/service/wmts/rest/myLayer/{style}/{TileMatrixSet}/{TileMatrix}/{TileRow}/{TileCol}?format=image/png

but this one is also valid (it's up to the server to define the URL
template):

https:// testServer
/geoserver/gwc/service/wmts/rest/myLayer/{style}/{TileMatrixSet}/{TileMatrix}/{TileCol}/{TileRow}?format=image/png

The job of the WMTS client is to take the URL template and replace
parameters by name, without bothering about their position in the URL.



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


On Mon, May 20, 2024 at 12:32 PM Miguel Ángel Parrilla Godínez via
Geoserver-users  wrote:

> Hello
>
>
>
> We are generating caches with geoserver 2.23.1, using a Slippy blobstore.
> In the result obtained, we can see that the order of columns and rows is
> not the same as that shown in the OGC WMTS (
> https://www.ogc.org/standard/wmts/) standard.
>
> That is, in the standard it is observed that the configuration of the
> capablities file is as follows:
>
> {TileMatrix}/{TileRow}/{TileCol}.png
>
> While now the result requires you to make the following configuration:
>
> {TileMatrix}/{TileCol}/{TileRow}.png
>
>
>
> What's the reason for that?
>
> Is it possible to configure the final order of rows and columns in
> geoserver?
>
> Thanks a lot.
>
>
>
> Miguel Ángel.
>
> --
>
> AVISO LEGAL: Este correo y en su caso su(s) archivo(s) adjunto(s),
> proceden de TRACASA INSTRUMENTAL, S.L. y se dirige exclusivamente a su
> destinatario, puede contener información privada o confidencial amparada
> por el secreto de empresa, y a la que sólo tiene el derecho de acceder el
> destinatario. Si no es Vd. el destinatario indicado, o la persona
> responsable de su entrega al mismo, deberá abstenerse de examinar su
> contenido y queda notificado de que la utilización, divulgación y/o copia
> sin autorización está prohibida en virtud de la legislación vigente. Si ha
> recibido este mensaje por error, le rogamos que nos lo comunique
> inmediatamente mediante correo electrónico a esta misma dirección, y
> proceda a su destrucción segura. TRACASA INSTRUMENTAL, S.L. es el
> responsable de tratamiento de los datos de carácter personal facilitados
> que se utilizarán con la finalidad de mantener comunicaciones con usted.
> Tiene la posibilidad de ejercitar los derechos de acceso, rectificación,
> limitación del tratamiento, supresión y portabilidad, mediante solicitud
> dirigida por escrito, acreditando su identidad a la dirección electrónica
> d...@itracasa.es. Puede consultar información adicional y detallada sobre
> nuestra política de protección de datos de nuestra web www.itracasa.es.
> ___
> 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

Re: [Geoserver-users] sld fill-opacity on mark in graphic graphic stroke stroke not working?

[Andrea Aime]

Hi Grégoire,
I can confirm it's the case... the situation is confusing, because for a
Graphic object one can set an opacity at the Graphic level,
which does work:


  
circle

  #ff
  0.5

  
  12
*  0.5*


[image: image.png]

I guess that for the fill and stroke within the mark, one could multiply
the internal opacity by the graphic's own opacity?
But right now it's not done, and the graphic opacity is overriding whatever
you set for fill and stroke.


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


On Fri, May 17, 2024 at 2:51 PM VANDENSCHRICK, Grégoire
 wrote:

> Hi,
>
> I have a rather simple sld symbology that intends to represent lines by
> circles, much like explained in the cookbook;
>
> here is my sld:
>
> http://www.opengis.net/sld; xmlns:sld="http://www.opengis.net/sld;
> xmlns:gml="http://www.opengis.net/gml; xmlns:ogc="
> http://www.opengis.net/ogc; version="1.0.0">
>   
> URBAN_DUP_Public_space_filter_18_bicycle
> 
>   URBAN_DUP_Public_space_filter_18_bicycle
>   
> 
>   Bicycle PLUS
> Vlo PLUS
> Fiets PLUS
> Bicycle PLUS
>   
>   http://www.opengis.net/ogc;>
> 
>   VELO
>   1
> 
>   
>   http://www.opengeospatial.org/se/units/metre;>
> 
>   
> 
>   
> circle
> 
>name="fill">#ff
>name="fill-opacity">0.5
> 
>   
>   40
> 
>   
>   40 40
> 
>   
> 
>   
> 
>   
> 
>
> I'm under Geoserver 2.24.2, and everything works except the fill-opacity.
> Is there a known bug there, or do I do something wrong? I did try to put a
> stroke-opacity just after the stroke-dasharray CssParameter, but it's not
> working either...
>
> Thank you already for your ideas/help,
>
> Greg for BruGIS
> ___
> 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 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] [EXTERNO] Re: Enable Jetty Logs

[Andrea Aime]

Hi Oscar,
there are known vulnerability issues affecting versions of GeoServer as old
as 2.13, exposing them to the internet is a significant risk.
Please try to upgrade as soon as possible, newer versions have been patched
and are no longer affected.

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


On Wed, May 15, 2024 at 6:39 AM Oscar Diago Alonso via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> Hi.
>
>
>
> Yes, it is. I know is rather old (although I have clients with even older
> ones).
>
>
>
> The idea behind is to capture every request performed against GeoServer
> without the need of enabling Developer level logs. I have also learned
> about the Monitor extension, so I will give that a go, too.
>
>
>
> Best regards.
>
>
>
>
> *Óscar Diago Alonso Ingeniero GIS*
> (+34) 945 13 13 72 | Plza. del Renacimiento, 9, 2.ª planta, Oficina 2 -
> 01004 Vitoria-Gasteiz
>
>
>
> *De:* Russ Hore 
> *Enviado el:* martes, 14 de mayo de 2024 15:42
> *Para:* Oscar Diago Alonso 
> *CC:* geoserver-users@lists.sourceforge.net
> *Asunto:* [EXTERNO] Re: [Geoserver-users] Enable Jetty Logs
>
>
>
> 2.13 is very old?
>
>
>
> Are you sure that is the right version you are using?
>
>
>
> Russ
>
>
>
> On 14 May 2024, at 06:54, Oscar Diago Alonso via Geoserver-users <
> geoserver-users@lists.sourceforge.net> wrote:
>
>
>
> Good morning.
>
>
>
> I’ve installed GeoServer 2.13 as a Windows service. I was wondering if it
> is possible to turn on the logging of the Jetty servlet packed with
> GeoServer.
>
>
>
> I’v been looking for documentation on how to do that, but I’m not finding
> anything useful. Is it even possible? Does anyone know how to achieve that?
>
>
>
> Best regards.
>
>
>
> *Óscar Diago Alonso — Ingeniero GIS *(+34) 945 13 13 72 | Plza. del
> Renacimiento, 9, 2.ª planta, Oficina 2 - 01004 Vitoria-Gasteiz
> <https://www.linkedin.com/company/geograma/>
> Si no ves la imagen puedes acceder desde aquí
> <https://www.linkedin.com/company/geograma/>
>
> Esta comunicación contiene información de acceso restringido y de uso
> exclusivo del destinatario. Si usted no es el destinatario tenga en cuenta
> que cualquier distribución, copia o uso de esta comunicación o la
> información que contiene está estrictamente prohibida. Si usted ha recibido
> esta comunicación por error por favor notifíquelo en la dirección
> d...@geograma.com. Tratamos su dirección de correo electrónico y otros
> datos personales para mantener el contacto y comunicación con Ud. y, en su
> caso, remitirle información sobre nuestros productos y servicios. Si no
> desea recibir tal información envíe un e-mail en tal sentido a
> d...@geograma.com. Puede acceder, rectificar y suprimir los datos, así
> como otros derechos, como se detalla en la información adicional y completa
> a su disposición en nuestra política de privacidad en la URL
> www.geograma.com/politica-privacidad/
>
> <https://www.geograma.com/>
> ___
> 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/u

Re: [Geoserver-users] push data source

[Andrea Aime]

Agreed. For those that need to process moving points at scale, things can
get complex, we shared the approach
we took in one such cases in this old blog post:

https://www.geosolutionsgroup.com/portfolio/real-time-maritime-picture-with-geoserver/

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


On Tue, May 14, 2024 at 2:27 PM Peter Smythe  wrote:

> Hi Jeremy
>
> While you *can* do this via GeoServer, it's probably far from optimal.
> GeoServer is designed to publish data (via WMS, WFS standards).  You could
> use a WFS-T (transaction) to update a device's location stored in a spatial
> database, but it would be more efficient to have a simple CRUD API directly
> to the database, not via GeoServer.  Take a look at https://postgrest.org/
> perhaps?  You might  also want to look into websockets for real time
> display updates.
>
> Peter
>
> GeoServer PSC
> AWS Solutions Architect
> https://github.com/petersmythe
>
>
> On Mon, 13 May 2024 at 21:29, Jeremy Jackson  wrote:
>
>> Is there a data source or API which would allow pushing a point feature
>> and/or updating it in realtime?
>>
>> For example, a GPS tracking device which emits a location update once a
>> minute, could this cause a map to be updated in real time?
>>
>>
>>
>> ___
>> 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 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 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] invisible mapped/share drives in Store creation

[Andrea Aime]

Hi Armando,
yes that's what we were expecting, thanks for sharing step by step
instructions on how to get it fixed

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


On Fri, Apr 19, 2024 at 5:20 PM Armando Forlani 
wrote:

> Hi Andrea and Jody,
>
>
>
> I RESOLVED my issue taking clues from this
>
>
> https://superuser.com/questions/1758898/service-is-not-able-to-access-a-network-drive-mapping-despite-running-under-the
>
> ..which led to this:
>
>
> https://learn.microsoft.com/en-us/answers/questions/1168194/how-run-windows-services-as-the-current-user-when
>
> ..and tried a few things but essentially the Windows service has to be
> started as the user logging in the machine and has access to the shared
> folders (default is ‘Network Service’):
>
>1. Go to the Service console via services.msc
>2. Locate the GeoServer service
>3. Set manual start/stop and stop the service
>4. Properties à Log On
>5. Change ‘This account’ value…
>   1. Click ‘Browse’ and check only the ‘User’ box in the object type
>   list
>   2. Enter ‘\’ in the ‘Enter the object
>   name to select’ and validate it by clicking ‘Check Names’
>   3. OK
>6. Start service
>
>
>
> Hopefully I was the only one experiencing this issue, but if there are
> others.. this should be of some use.
>
>
>
> Thanks,
>
> Armando
>
>
>
>
>
> Original issue:
>
>
>
> I’m creating a new Store using a GeoPackage file as data source
> (database). It works fine with a gpkg file saved locally i.e. anywhere on
> the C: drive. I’m unable to make it work with files stored on a share
> drive, either the full path or a logical drive letter.
>
>
>
> file://J:/folder/data.gpkg
>
>   Error creating data store, check the parameters. Error message: Unable
> to obtain connection: path to 'J:\folder\data.gpkg': 'J:\' does not exist
>
>
>
> file:\\J:\folder\data.gpkg
>
>   Error creating data store, check the parameters. Error message: Unable
> to obtain connection: path to 'J:\folder\data.gpkg': 'J:\' does not exist
>
>
>
> file:DOMAIN.LOCAL/SHARED/shared_folder/folder/data.gpkg
>
>   Error creating data store, check the parameters. Error message: Unable
> to obtain connection: [SQLITE_CANTOPEN] Unable to open the database file
> (unable to open database file)
>
>
>
> file:DOMAIN.LOCAL\SHARED\shared_folder\folder\data.gpkg
>
>   Error creating data store, check the parameters. Error message: Unable
> to obtain connection: [SQLITE_CANTOPEN] Unable to open the database file
> (unable to open database file)
>
>
>
> It is also impossible making use of the ‘Browse…’ link next to the
> ‘database’ edit box. It won’t list any mapped drives in the drop down list.
> Only ‘Data directory’, ‘Home directory’, A:\, ‘OS Disk (C:)’, D:\ are
> shown.
>
>
>
> Moving data locally is not an option.
>
>
>
> Running:
>
> Windows 10 Enterprise
>
> VMware Virtual Platform
>
> Eclipse Adoptium: 17.0.10 (OpenJDK 64-Bit Server VM)
>
> GeoServer 2.24.2 as a Windows service
>
>
>
> Any help would be really appreciated.
>
>
>
> Thanks,
>
> Armando
>
>
>
>
>
>
>
>
> This message has been scanned for malware by Forcepoint.
> www.forcepoint.com
>
___
Geoserver-users mailing list

Please make sure you read the following two 

Re: [Geoserver-users] [Geotools-devel] forwarding GEBCO WMS fails - help needed

[Andrea Aime]

On Wed, Apr 24, 2024 at 3:30 PM Roar Brænden 
wrote:

> What I'm confused about is how the two classes should influence on what is
> sent as Accept-header. Nothing in the code indicates something like that.
>

One is the built-in java client, the other the Apache one... I guess they
might have different defaults, if no accept-header is specified?
Just thinking out loud

Cheers
Andrea
___
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] FW: WMS broken after GeoServer Update (SAXException)

[Andrea Aime]

Hi Daniel,
I've tested with the official GeoServer docker image, the preview works
fine:

> docker pull docker.osgeo.org/geoserver:2.25.0
> docker run  -it -p8080:8080 docker.osgeo.org/geoserver:2.25.0

[image: image.png]

The "binary package" is also working fine for me. In neither case did I had
to set up an allowlist...

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


On Tue, Apr 23, 2024 at 1:12 PM Calliess Daniel Ing. <
daniel.calli...@stadt-salzburg.at> wrote:

> Hi again,
>
>
>
> is there anybody who could tell if this is expected behaviour or a side
> effect of the introduction of the ENTITY_RESOLUTION_ALLOWLIST setting?
>
>
>
> Regards
> Daniel
>
>
>
>
>
> *From:* Calliess Daniel Ing.
> *Sent:* Montag, 22. April 2024 15:00
> *To:* geoserver-users 
> *Subject:* WMS broken after GeoServer Update (SAXException)
>
>
>
> Hi,
>
>
>
> I updated my GeoServer (Tomcat 9/Windows Server) from 2.24.2 to 2.25.0 and
> now I can't preview WMS layers. The error message is:
> "java.lang.reflect.UndeclaredThrowableExceptionorg.xml.sax.SAXException:
> Entity resolution disallowed for null". The same message is shown when I
> try to validate an SLD stylesheet. I copied the full stack trace to a file
> and attached it to this message. I also reverted back to the data dir
> included in the 2.25.0 release and can reproduce the error f.e. with the
> 'point' style.
>
>
>
> I now found out that when I'm starting GeoServer with the
> -DENTITY_RESOLUTION_ALLOWLIST=* parameter, the error is gone. Although this
> parameter shouldn't be necessary because the styles are only containing
> references to www.opengis.net and www.w3.org which are in the default
> list of allowed domains for entity expansion according to the
> documentation
> <https://docs.geoserver.org/latest/en/user/production/config.html#production-config-external-entities>
> .
>
>
>
> The geoserver log shows a lot of "WARN   [geotools.xsd] - Sax parser
> property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit'
> not recognized.  Xerces version is incompatible." messages. Might there be
> a connection to the above issue?
>
>
>
> Am I doing something wrong?
>
>
>
> Thank you and best regards
> Daniel
> ___
> 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 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] Something went wrong on admin interface of GeoWebCache

[Andrea Aime]

Hi Jean-Christophe,
that's a very long jump!

Based on the stack trace, that layer has a reference to a style that's
missing, in the
"other styles" section.
Clean it up and the GUI for caching should be working again.

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


On Tue, Apr 23, 2024 at 4:20 PM Jean-Christophe Bastin 
wrote:

> Hello community,
>
>
>
> I’m actually working on a migration from GeoServer 2.10.0 to 2.25.0.
>
> I made many tests and adaptations to make my workspace work well again,
> and sounds like a last point isn’t going well.
>
> Forgive me for the traduction, it is coming from a french UI.
>
> When accessing “Tiles cache”, “Layers cache”, then clicking to add a new
> layer (the list is empty) , a “Oops something went wrong” message is
> displayed with a stack trace that I give you in the attached file
> “add-tile-cache.log”.
>
> It’s like GeoServer is not able to generate the page to display, but I
> don’t know why.
>
> I see in the About section the GeoServer version is well 2.25.0, and
> GeoWebCache version is 1.25.0, is it good ?
>
> Am I missing something ? Maybe something went wrong during the migration ?
>
>
>
> Many thanks !
>
>
>
> Jean-Christophe
> ___
> 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 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] Geometry type mismatch

[Andrea Aime]

Hi Daniel,
the issue is not recorded yet in Jira, I invite you to file a report there:
https://osgeo-org.atlassian.net/projects/GEOS/summary

In order to get it fixed, see this guide:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-fixes,-improvements-and-new-features-in-GeoServer

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


On Mon, Apr 22, 2024 at 5:31 PM Calliess Daniel Ing. <
daniel.calli...@stadt-salzburg.at> wrote:

> Hi,
>
>
>
> after upgrading GeoServer from 2.24.0 to 2.24.1 one of my users was unable
> to process data from the WFS service in the software FME. The problem comes
> from the fact that the feature type returned in the GetFeature request
> doesn't match the feature type declared in the DescribeFeatureType request
> when accessing the service using WFS 1.1.0. In this case FME doesn't detect
> the geometries.
>
>
>
> This can be reproduced using the 'ne:countries' layer in a new GeoServer
> installation. This is what my tests showed:
>
>
>
> GeoServer 2.24.0
>
> WFS 1.0.0
>
>GetFeature = MultiPolygon
>
>DescribeFeatureType = MultiPolygonPropertyType
>
> WFS 1.1.0
>
>GetFeature = MultiSurface
>
>DescribeFeatureType = MultiSurfacePropertyType
>
> WFS 2.0.0
>
>GetFeature = MultiSurface
>
>DescribeFeatureType = MultiSurfacePropertyType
>
>
>
> GeoServer 2.24.1
>
> WFS 1.0.0
>
>GetFeature = MultiPolygon
>
>DescribeFeatureType = MultiPolygonPropertyType
>
> WFS 1.1.0
>
>GetFeature = *MultiSurface*
>
>DescribeFeatureType = *MultiPolygonPropertyType*
>
> WFS 2.0.0
>
>GetFeature = MultiSurface
>
>DescribeFeatureType = MultiSurfacePropertyType
>
>
>
> Please look into this and correct the error.
>
>
>
> Thank you and best regards
> Daniel
> ___
> 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 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] Geometry type mismatch

[Andrea Aime]

Hi Jukka,
the flip axis issue has been resolved recently and the fix will be part of
2.25.1 (and is already part of 2.24.3):
https://osgeo-org.atlassian.net/browse/GEOS-11236

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


On Mon, Apr 22, 2024 at 9:31 PM Rahkonen Jukka <
jukka.rahko...@maanmittauslaitos.fi> wrote:

> Hi,
>
>
>
> I made a test with Geoserver 2.25.0 and I can confirm that there is a
> mismatch between DescribeFeatureType and GetFeature for ne:countries with
> WFS 1.1.0.
>
> I tried to test also topp:states but it seems that there is something else
> broken with that. GetFeature with WFS 1.1.0 and WFS 2.0 returns this error:
>
>
>
> 
>
> We have had issues trying to flip axis of
> GEOGCS["GCS_WGS_1984", DATUM["WGS_1984", SPHEROID["WGS_1984", 6378137.0,
> 298.257223563]], PRIMEM["Greenwich", 0.0], UNIT["degree",
> 0.017453292519943295], AXIS["Longitude", EAST], AXIS["Latitude", NORTH]] No
> authority was defined for code "GCS_WGS_1984". Did you forget
> "AUTHORITY:NUMBER"?
>
>
>
> I was testing with a new Geoserver binzip installation on Windows, JVM
> Eclipse Adoptium: 11.0.22.
>
>
>
> -Jukka Rahkonen-
>
>
>
>
>
>
>
> *Lähettäjä:* Ian Turton 
> *Lähetetty:* maanantai 22. huhtikuuta 2024 19.00
> *Vastaanottaja:* Calliess Daniel Ing. 
> *Kopio:* geoserver-users 
> *Aihe:* Re: [Geoserver-users] Geometry type mismatch
>
>
>
>
>
>
>
> On Mon, 22 Apr 2024 at 16:29, Calliess Daniel Ing. <
> daniel.calli...@stadt-salzburg.at> wrote:
>
> Hi,
>
>
>
> after upgrading GeoServer from 2.24.0 to 2.24.1 one of *my users*
>
>
>
> *Please look into this and correct the error.*
>
>
>
> Please remember that GeoServer is maintained by volunteers - if your users
> have a problem then they are (presumably) paying you to take care of it. If
> you are not up to fixing the problem yourself please contact one of the 
> commercial
> support teams <https://geoserver.org/support/> that will look into it for
> you.
>
>
>
> Ian
>
> --
>
> Ian Turton
> ___
> 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 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] forwarding GEBCO WMS fails - help needed

[Andrea Aime]

Pheraps a matter of user agent? The service might have a white list of
acceptable ones (eh well known client apps).

Just an idea...

Andrea

Il dom 21 apr 2024, 00:44 Brent Wood via Geoserver-users <
geoserver-users@lists.sourceforge.net> ha scritto:

> Hi,
>
> I'm looking to install geoserver on a ship.
>
> I'd like to use the GEBCO WMS service to provide a background map layer,
> but cache it locally to avoid internet traffic.
>
> The capabilities doc is at:
>
> https://wms.gebco.net/mapserv?REQUEST=GETCAPABILITIES=1.3.0=WMS
>
> The layer I wish to provide is: GEBCO_LATEST_SUB_ICE_TOPO
>
> I can connect & get the capabilities doc in a browser. I can select & open
> the layer in QGIS.
>
> When I try to set up a WMS store in Geoserver I enter the required
> parameters, but get told the connection test to the URL failed with error
> 403.
>
> I understand this means the Gebco server is refusing to reply with the
> doc. I'm not sure why the URL works from a browser but fails when sent from
> Geoserver, any suggestions appreciated, as far  as I know it is an
> identical request, from the same host.
>
>
> Thanks,
>
>   Brent Wood.
>
> ___
> 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 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] invisible mapped/share drives in Store creation

[Andrea Aime]

One way to find out quickly if it's related to the account used to run
GeoServer as a service,
it's to get on the machine where QGIS is working fine, install GeoServer
but not let it run
as a service... and start it manually, from the windows menu. That way it
works with the
same rights. Does it work then? If yes, you have issues with the limits of
the service account.
Otherwise, there is something likely to debug in the GeoServer code itself.

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


On Fri, Apr 19, 2024 at 4:17 PM Armando Forlani 
wrote:

> Hi Andrea,
>
> Thank you for your input. I did play around with a Ubuntu server on AWS
> years ago and know exactly what you mean. The best I can do here
> (hopefully) is deploying GS as a TomCat webapp.
>
> I’m not convinced by the readonly explanation though. I was editing a
> local (to GS) gpkg file with QGIS (both directly and as a GS WFS) and
> changes were reflected by GeoServer immediately (after panning the map)… so
> that’s not the problem. I’ve got to identify the issue before raising it as
> one.
>
> As you said, it would be great finding someone who has experienced the
> same issue, even better, someone who resolved it.
>
> Armando
>
>
>
>
>
>
>
> *From:* Andrea Aime 
> *Sent:* 19 April 2024 14:24
> *To:* Armando Forlani 
> *Cc:* Jody Garnett ;
> geoserver-users@lists.sourceforge.net
> *Subject:* Re: [Geoserver-users] invisible mapped/share drives in Store
> creation
>
>
>
> Armando, the problem is not using SQLite remotely (it works fine as long
> as the file is read only and not modified by other applications),
>
> but that you're on Windows, which is not the common way to deploy
> GeoServer (Linux deploys are, anecdotally, 30% faster on the same hardware,
>
> so they are the more common choice).
>
>
>
> The issue you're seeing needs some debugging, I'm confident they can be
> solved, but hardly on a mailing list,
>
> unless you find someone that already stumbled into the same issue.
>
>
> Regards,
>
> Andrea Aime
>
>
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us
> <http://webdefence.global.blackspider.com/urlwrap/?q=AXicBcFNCsIwEAbQTzyDN3AldmJbRXGlKF24EDxC7J_BSUYmaaC39z3csF4Cr9UCyvOu6ihqJm8dtxKSClMrHvv6cX9y3ZTH8nCqcFVvQyfUiLIN7pIGplEyTV98UvqdjXm7RDybMRax1-zaPhZTBLDZAn-QfCKP>
> 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 

Re: [Geoserver-users] SLD gap property GeoServer 2.23.1

[Andrea Aime]

It is indeed ignored. Generally speaking, GeoServer is built around SLD
1.0 + vendor extensions, and tends
to ignore SLD 1.1 specific bits (well, unless someone funded development
geared towards supporting those extra
features, e.g., it happened for inline graphics for example).

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


On Fri, Apr 12, 2024 at 4:27 PM Miguel Ángel Parrilla Godínez via
Geoserver-users  wrote:

> Hi all
>
> I would like to know if GeoServer 2.23.1 still ignores  the SLD gap
> property.
>
> I´m trying and it doesn´t work:
>
>
>
>   
>
> 
>
>   
>
> 
>
>   
>
>
>
>   
>
>   
>
>  *"arrow.svg"*/>
>
> image/svg+xml
>
>   
>
>   
>
>   
>
> square
>
> 
>
>   #ff
> 
>
> 
>
> 
>
>   #232323
> 
>
>   0.5
> 
>
> 
>
>   
>
>   70
>
>   
>
> 45
>
>   
>
> 
>
> 
>
>  5
>
> 
>
>   
>
> 
>
>   
>
>
>
>
>
> Thanks.
>
> Miguel Ángel.
>
> --
>
> AVISO LEGAL: Este correo y en su caso su(s) archivo(s) adjunto(s),
> proceden de TRACASA INSTRUMENTAL, S.L. y se dirige exclusivamente a su
> destinatario, puede contener información privada o confidencial amparada
> por el secreto de empresa, y a la que sólo tiene el derecho de acceder el
> destinatario. Si no es Vd. el destinatario indicado, o la persona
> responsable de su entrega al mismo, deberá abstenerse de examinar su
> contenido y queda notificado de que la utilización, divulgación y/o copia
> sin autorización está prohibida en virtud de la legislación vigente. Si ha
> recibido este mensaje por error, le rogamos que nos lo comunique
> inmediatamente mediante correo electrónico a esta misma dirección, y
> proceda a su destrucción segura. TRACASA INSTRUMENTAL, S.L. es el
> responsable de tratamiento de los datos de carácter personal facilitados
> que se utilizarán con la finalidad de mantener comunicaciones con usted.
> Tiene la posibilidad de ejercitar los derechos de acceso, rectificación,
> limitación del tratamiento, supresión y portabilidad, mediante solicitud
> dirigida por escrito, acreditando su identidad a la dirección electrónica
> d...@itracasa.es. Puede consultar información adicional y detallada sobre
> nuestra política de protección de datos de nuestra web www.itracasa.es.
> ___
> 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-

Re: [Geoserver-users] invisible mapped/share drives in Store creation

[Andrea Aime]

Armando, the problem is not using SQLite remotely (it works fine as long as
the file is read only and not modified by other applications),
but that you're on Windows, which is not the common way to deploy GeoServer
(Linux deploys are, anecdotally, 30% faster on the same hardware,
so they are the more common choice).

The issue you're seeing needs some debugging, I'm confident they can be
solved, but hardly on a mailing list,
unless you find someone that already stumbled into the same issue.

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


On Fri, Apr 19, 2024 at 12:50 PM Armando Forlani 
wrote:

> Hi,
>
> I understand the limitation of querying a sqlite file remotely, but this
> works just fine on clients such as QGIS (that’s likely because Client
> Application and SQLite Database Engine sit together? Unlike GeoServer? As
> your link suggest).
>
>
>
> It is not possible for me to move all GeoPackage files on the same machine
> with GeoServer. I’m not interfering in how various teams manage and store
> their data. It simply not going to happen. Yes, we do have the usual
> suspect “enterprise” GIS stack. Here I’m attempting to also have a full
> open source stack e.g. postgres/postgis+geoserver(+geonetwork) initially
> for particular case scenarios and purposes. The addition of GeoPackage as a
> Store in GS is brilliant and, in theory, makes it easier to set up not just
> a demo, but a fully working, if not a little bit simplistic, open source
> GIS stack.
>
>
>
> There is no warnings in the GS docs that it’s not possible to connect to
> sqlite remotely. The interface lets me happily attempt such connection. In
> which case it should only be a performance issue rather than the outright
> inability to connect: Error creating data store, check the parameters.
> Error message: Unable to obtain connection: [SQLITE_CANTOPEN] Unable to
> open the database file (unable to open database file).
>
>
>
> So, does this
>
> file:DOMAIN.LOCAL/SHARED/shared_folder/folder/data.gpkg
>
> ..return
>
>   Error creating data store, check the parameters. Error message: Unable
> to obtain connection: [SQLITE_CANTOPEN] Unable to open the database file
> (unable to open database file)
>
> ..because there is something wrong in the path, shared folder permission
> (even if visible in the file explorer on the same machine where GS is
> installed), etc.. OR is it simply not allowed (either by GS or the sqlite
> driver)?
>
>
>
> I tried setting up a shapefile store (I believe GS won’t attempt a
> connection just yet, it did not complain), then create a layer from the
> only shp file in the store (a path to the file really), it returns a java
> error output…:
>
>
>
> Caused by: java.io.FileNotFoundException:
> \\DOMAIN.LOCAL\SHARED\shared_folder\folder\layer.shp (Access is denied)
>
>
>
> That ‘Access is denied’ suggests that it’s not the type of store but
> something to do with GS accessing remote locations.
>
>
>
>
>
>
>
>
>
>
>
> *From:* Jody Garnett 
> *Sent:* 18 April 2024 22:06
> *To:* Armando Forlani 
> *Cc:* geoserver-users@lists.sourceforge.net
> *Subject:* Re: [Geoserver-users] invisible mapped/share drives in Store
> creation
>
>
>
> Here:
>
> https://www.sqlite.org/useovernet.html
>
>
> --
>
> Jody Garnett
>
>
>
>
>
> On Thu, Apr 18, 2024 at 8:49 PM Armando Forlani <
> armando.forl...@tfl.gov.uk> wrote:
>
> Hi Jody,

Re: [Geoserver-users] Setting SKIP_DEMO_DATA=true changes the global settings.

[Andrea Aime]

What you're seeing seems quite normal to me.
>From the documentation:

"The environment variable SKIP_DEMO_DATA can be set to true to create an
empty data directory."

So you switch from a demo data directory, that not only has data, but also
several settings, to one that's
completely empty, where everything picks built-in defaults.

Using the internal data directory is anyways a bad idea, please externalize
it instead
<https://github.com/geoserver/docker?tab=readme-ov-file#how-to-mount-an-external-folder-for-use-as-a-data-directory>,
and use a
starter data directory with the base settings that best suit your needs. If
you like the settings
found in the demo data, just start from there and remove the bits you don't
want.

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


On Fri, Apr 19, 2024 at 11:21 AM Shingo NISHIYAMA (西山 真吾) <
shin...@intent-exchange.com> wrote:

> Does anyone have any information?
>
> Best regards,
> Shingo
>
> -Original Message-
> From: Shingo NISHIYAMA
> Sent: Friday, March 29, 2024 4:30 PM
> To: geoserver-users 
> Subject: Setting SKIP_DEMO_DATA=true changes the global settings.
>
> Hello All,
>
> I am using geoserver docker image.
> If I set `SKIP_DEMO_DATA=true`[1], the Global Settings[2] will change.
> For example, "Number of Decimals" is set to 4 instead of the default value
> of 8.
>
> Is this an intended change? Or is it a bug?
>
> [1]
> https://github.com/geoserver/docker?tab=readme-ov-file#environment-variables
> [2]
> https://docs.geoserver.org/latest/en/user/configuration/globalsettings.html
>
> $ docker image ls --digests docker.osgeo.org/geoserver
> REPOSITORY   TAG   DIGEST
>   IMAGE ID   CREATED SIZE
> docker.osgeo.org/geoserver   2.25.0
> sha256:19335fcc02fbdcbcff0acdc89a05831f88e074d9025e49b11cb0355df1091c4f
>  e2ab41d76027   9 days ago  957MB
>
> $ docker run --rm -it -p 80:8080 -e SKIP_DEMO_DATA=false
> docker.osgeo.org/geoserver:2.25.0 ...
> $ curl -s -u admin:geoserver http://localhost:80/geoserver/rest/settings
> | jq .global.settings.numDecimals
> 8
>
> ---
>
> $ docker run --rm -it -p 80:8080 -e SKIP_DEMO_DATA=true
> docker.osgeo.org/geoserver:2.25.0 ...
> $ curl -s -u admin:geoserver http://localhost:80/geoserver/rest/settings
> | jq .global.settings.numDecimals
> 4
>
> Best regards,
> Shingo
>
>
>
> ___
> 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 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

I

Re: [Geoserver-users] Wrong time values for Oracle DATE columns

[Andrea Aime]

Hi Daniel,
the Oracle datastore tests seem to confirm what Ian says, they create a
table to store a date, a timestamp, and a time column (some databases
can handle the three types as separate) and the syntax is the following:

CREATE TABLE DATES (D DATE, DT TIMESTAMP, T TIMESTAMP)

and then they check the mappings work, overriding the test because Oracle
has no notion of "time" alone:

/*
 * Oracle has no concept of just "Time". Sigh...
 * @see org.geotools.jdbc.JDBCDateTest#testMappings()
 */
@Override
public void testMappings() throws Exception {
SimpleFeatureType ft = dataStore.getSchema(tname("dates"));

assertEquals(Date.class,
ft.getDescriptor(aname("d")).getType().getBinding());
assertEquals(Timestamp.class,
ft.getDescriptor(aname("dt")).getType().getBinding());
assertEquals(Timestamp.class,
ft.getDescriptor(aname("t")).getType().getBinding());
}

So yes, if you want GeoServer to handle date+time, use the TIMESTAMP column
type.

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


On Thu, Apr 18, 2024 at 1:06 PM Calliess Daniel Ing. <
daniel.calli...@stadt-salzburg.at> wrote:

> Hi,
>
>
>
> I just discovered that GeoServer is rounding Oracle DATE attribute values
> down to zero or twelve hours when I'm publishing data from a 'Oracle NG
> (OCI)' data store. Examples:
>
>
>
> 1.1.2024 17:34:12 becomes 1.1.2024 12:00:00 or
>
> 1.1.2024 03:17:05 becomes 1.1.2024 00:00:00
>
>
>
> This happens only when I'm publishing a complete table, not when I'm
> defining an SQL view. Directly after creating the new layer, the column
> type is set to the Java data type 'Date'. Comparing to an SQL view I saw
> that there the column is defined as 'Timestamp'. But also changing the data
> type using the 'Customize attributes' function to 'Timestamp' or 'Time'
> doesn't help.
>
>
>
> This happend in GeoServer 2.23.0 and also 2.25.0.
>
>
>
> Does anybody have an idea what's going on here.
>
>
>
> Thank you and best regards
> Daniel
> ___
> 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 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] invisible mapped/share drives in Store creation

[Andrea Aime]

And oh,
for the second error, the path can be accessed, but SQLITE states it cannot
open the file.
Maybe it's due to write permissions? Try checking the "read only" flag.

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


On Thu, Apr 18, 2024 at 2:15 PM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> HI Armando,
> the errors seem telling, "J: does not exist". If it's really there, then I
> would assume GeoServer is really
> not seeing it.
>
> See for example:
> https://superuser.com/questions/1758898/service-is-not-able-to-access-a-network-drive-mapping-despite-running-under-the
>
>
> 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 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
>
>
> On Thu, Apr 18, 2024 at 1:44 PM Armando Forlani <
> armando.forl...@tfl.gov.uk> wrote:
>
>> Hi,
>>
>>
>>
>> I’m creating a new Store using a GeoPackage file as data source
>> (database). It works fine with a gpkg file saved locally i.e. anywhere on
>> the C: drive. I’m unable to make it work with files stored on a share
>> drive, either the full path or a logical drive letter.
>>
>>
>>
>> file://J:/folder/data.gpkg
>>
>>   Error creating data store, check the parameters. Error message: Unable
>> to obtain connection: path to 'J:\folder\data.gpkg': 'J:\' does not exist
>>
>>
>>
>> file:\\J:\folder\data.gpkg
>>
>>   Error creating data store, check the parameters. Error message: Unable
>> to obtain connection: path to 'J:\folder\data.gpkg': 'J:\' does not exist
>>
>>
>>
>> file:DOMAIN.LOCAL/SHARED/shared_folder/folder/data.gpkg
>>
>>   Error creating data store, check the parameters. Error message: Unable
>> to obtain connection: [SQLITE_CANTOPEN] Unable to open the database file
>> (unable to open database file)
>>
>>
>>
>> file:DOMAIN.LOCAL\SHARED\shared_folder\folder\data.gpkg
>>
>>   Error creating data store, check the parameters. Error message: Unable
&

Re: [Geoserver-users] invisible mapped/share drives in Store creation

[Andrea Aime]

HI Armando,
the errors seem telling, "J: does not exist". If it's really there, then I
would assume GeoServer is really
not seeing it.

See for example:
https://superuser.com/questions/1758898/service-is-not-able-to-access-a-network-drive-mapping-despite-running-under-the


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


On Thu, Apr 18, 2024 at 1:44 PM Armando Forlani 
wrote:

> Hi,
>
>
>
> I’m creating a new Store using a GeoPackage file as data source
> (database). It works fine with a gpkg file saved locally i.e. anywhere on
> the C: drive. I’m unable to make it work with files stored on a share
> drive, either the full path or a logical drive letter.
>
>
>
> file://J:/folder/data.gpkg
>
>   Error creating data store, check the parameters. Error message: Unable
> to obtain connection: path to 'J:\folder\data.gpkg': 'J:\' does not exist
>
>
>
> file:\\J:\folder\data.gpkg
>
>   Error creating data store, check the parameters. Error message: Unable
> to obtain connection: path to 'J:\folder\data.gpkg': 'J:\' does not exist
>
>
>
> file:DOMAIN.LOCAL/SHARED/shared_folder/folder/data.gpkg
>
>   Error creating data store, check the parameters. Error message: Unable
> to obtain connection: [SQLITE_CANTOPEN] Unable to open the database file
> (unable to open database file)
>
>
>
> file:DOMAIN.LOCAL\SHARED\shared_folder\folder\data.gpkg
>
>   Error creating data store, check the parameters. Error message: Unable
> to obtain connection: [SQLITE_CANTOPEN] Unable to open the database file
> (unable to open database file)
>
>
>
> It is also impossible making use of the ‘Browse…’ link next to the
> ‘database’ edit box. It won’t list any mapped drives in the drop down list.
> Only ‘Data directory’, ‘Home directory’, A:\, ‘OS Disk (C:)’, D:\ are
> shown.
>
>
>
> Moving data locally is not an option.
>
>
>
> Running:
>
> Windows 10 Enterprise
>
> VMware Virtual Platform
>
> Eclipse Adoptium: 17.0.10 (OpenJDK 64-Bit Server VM)
>
> GeoServer 2.24.2 as a Windows service
>
>
>
> Any help would be really appreciated.
>
>
>
> Thanks,
>
> Armando
>
>
>
>
>
>
> This message has been scanned for malware by Forcepoint.
> www.forcepoint.com
> ___
> 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 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] MapBox style created with REST API

[Andrea Aime]

Hi Alexandre,
while I don't have experience using MBStyle with the REST API, it seems
odd, I would
expect it only if raw was not present and set to true.
Can you share both the request you're using, and the full stack trace (down
to the last caused by please).

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


On Mon, Apr 15, 2024 at 12:16 PM Alexandre Gacon 
wrote:

> Hello,
>
> I am creating styles in MapBox style format with the REST API with a raw
> parameter set to true.
>
> When I try to get back the styles with the REST API, I always have a 500
> error. In the log file I have the following errors:
>
> java.lang.UnsupportedOperationException: null
>
>   at 
> org.geoserver.community.mbstyle.MBStyleHandler.encode(MBStyleHandler.java:134)
>
>
> It works correctly with SLD and CSS formats.
>
> Is it a known issue?
>
> --
> Alexandre Gacon
> ___
> 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 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] WFS query of a Vector Mosaic datastore

[Andrea Aime]

Hi Richard,
at least part of the issue has been fixed in the meantime. You can test the
improvement using a nightly
build of the 2.25 or 2.24 series. If you're on an older version, I strongly
recommend an upgrade,
the vector mosaic has seen lots of performance related improvements in the
last year.

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


On Thu, Mar 21, 2024 at 9:33 AM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> Yes, confirmed, it's happening while the WFS 1.1&/2.0 GetFeature tries to
> compute the total features matched.
> The store lacks an efficient path to perform such a count, and resorts to
> a "load everything and filter in memory".
>
> So far the store has only been used (in production) for WMS purposes and
> this code needs to be developed
> to efficiently support WFS usage (or just use WFS 1.0, does not seem to
> happen in that case, at least for GML output).
>
> I'd recommend to open a jira ticket, and then, if you are in any urgent
> need to get a fix, look at this guide:
>
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-fixes,-improvements-and-new-features-in-GeoServer
> (consider the talking part done, it's the resourcing part that is missing)
>
> 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 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
>
>
> On Tue, Mar 19, 2024 at 9:28 PM Richard Matsunaga via Geoserver-users <
> geoserver-users@lists.sourceforge.net> wrote:
>
>> Hi Andrea,
>>
>>
>>
>> The SLD= was a mistake and has been removed. Has no effect anyway it
>> seems.
>>
>>
>>
>> I checked the bounding boxes produced for each row and they seems fine. I
>> then built a query with Postgis to filter by a bounding box and it returned
>> a subset of results.
>>
>>
>>
>> The logs show this query and, unless it is incomplete, it does not seem
>> to be filtering by the bounding box at all.
>>
>> SELECT "ogc_fid",encode(ST_AsEWKB("wkb_geometry"), 'base64') as

Re: [Geoserver-users] Line with perpendicular offset in legend

[Andrea Aime]

Hi Cécile,
yes it should be doable... with some changes.

The offset for lines and polygons is actually managed inside
StreamingRenderer, around line 3050+,
and the BufferedImageLegendGraphicBuilder does not employ one, it calls
directly StyledShapePainter.

One approach is to move the offset handling from StreamingRenderer down to
StyledShapePainter.
The other possibility is to extract the offset handling into a static
utility method that
BufferedImageLegendGraphicBuilder can use, in case there is an offset.

The former seems cleaner, but has a higher chance of unwanted side effects.

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


On Thu, Apr 11, 2024 at 1:55 PM Cécile Vuilleumier <
cecile.vuilleum...@camptocamp.com> wrote:

> Hi all
>
> I have a question regarding perpendicular offset of line symbolizers in
> legends.
> When using a symbolizer with no offset and another one with an offset, we
> see both symbols on top of another (without offset) in the legend. The
> discrepancy between the symbols on the map and in the legend might be a bit
> confusing. See an example at the bottom of this message.
>
> Could we imagine taking into account the offset in the legend?
> We already had a similar question regarding symbols at the beginning / the
> end of lines, so I can imagine it's not something doable but figured it's
> worth to ask the question.
>
> Cheers, Cécile
>
> Example SLD:
>
> 
> http://www.opengis.net/sld;
> <http://www.opengis.net/sld> xmlns:ogc="http://www.opengis.net/ogc;
> <http://www.opengis.net/ogc> xmlns:xlink="http://www.w3.org/1999/xlink;
> <http://www.w3.org/1999/xlink> xmlns:xsi=
> "http://www.w3.org/2001/XMLSchema-instance;
> <http://www.w3.org/2001/XMLSchema-instance> 
> xsi:schemaLocation="http://www.opengis.net/sld
> StyledLayerDescriptor.xsd"
> <http://www.opengis.net/sldStyledLayerDescriptor.xsd>>
>   
> line
> 
>   Line
>   
> 
>   line
>   line
>   
> 
>   #0070ff
>   6
>   0.7
> 
> 3
>   
>   
> 
>   #00
>   1
>   0.7
> 
> 0
>   
> 
>   
> 
>   
> 
>
> Result in style preview:
>
>
> --
> *camptocamp*
>
>
> *Cécile Vuilleumier *
> Geospatial developer
> www.camptocamp.com
> ___
> 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 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 GeoServe

Re: [Geoserver-users] WPS plugin issue/usage

[Andrea Aime]

Hi David,
the JTS:centroid takes a single geometry and computes its centroid.
In both cases instead you're feeding it a feature collection, that list, a
list of features, where each feature is geometry + attributes.

So, you're giving it something much more complex than what it's prepared to
process.
Something like this would work instead:

http://www.w3.org/2001/XMLSchema-instance;
xmlns="http://www.opengis.net/wps/1.0.0;
xmlns:wfs="http://www.opengis.net/wfs;
xmlns:wps="http://www.opengis.net/wps/1.0.0;
xmlns:ows="http://www.opengis.net/ows/1.1;
xmlns:gml="http://www.opengis.net/gml;
xmlns:ogc="http://www.opengis.net/ogc;
xmlns:wcs="http://www.opengis.net/wcs/1.1.1;
xmlns:xlink="http://www.w3.org/1999/xlink;
xsi:schemaLocation="http://www.opengis.net/wps/1.0.0
http://schemas.opengis.net/wps/1.0.0/wpsAll.xsd;>
  JTS:centroid
  

  geom
  

  

  

  
  

  result

  


I'm giving the process what it's expecting: a polygon (would work with any
other geometry type as well, as long as they are just geometries).

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


On Thu, Apr 4, 2024 at 1:05 PM David Alvey (Corporate Services and
Transformation) via Geoserver-users 
wrote:

> Hi
>
> I have installed the WPS extension in geoserver 2.21.1 but not sure if my
> query is wrong or the installation has failed.
>
> The heatmap tiles do render but when running a centroid query by Posting
> the following to https://wms.derbyshire.gov.uk/geoserver/ows?strict=true
>
>
>  service="WPS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns="http://www.opengis.net/wps/1.0.0; xmlns:wfs="
> http://www.opengis.net/wfs; xmlns:wps="http://www.opengis.net/wps/1.0.0;
> xmlns:ows="http://www.opengis.net/ows/1.1; xmlns:gml="
> http://www.opengis.net/gml; xmlns:ogc="http://www.opengis.net/ogc;
> xmlns:wcs="http://www.opengis.net/wcs/1.1.1; xmlns:xlink="
> http://www.w3.org/1999/xlink; xsi:schemaLocation="
> http://www.opengis.net/wps/1.0.0
> http://schemas.opengis.net/wps/1.0.0/wpsAll.xsd;>
>   JTS:centroid
>   
> 
>   geom
>   https://wms.derbyshire.gov.uk/geoserver/DCC/ows?service=WFSversion=1.0.0request=GetFeaturetypeName=DCC%3AMotorbike_Accidents_2022maxFeatures=50outputFormat=application%2FjsonpropertyName=the_geom;
> method="GET"/>
> 
>   
>   
> 
>   result
> 
>   
> 
>
> I get
>
> 
> http://www.w3.org/2001/XMLSchema;
> xmlns:ows="http://www.opengis.net/ows/1.1; xmlns:wps="
> http://www.opengis.net/wps/1.0.0; xmlns:xlink="
> http://www.w3.org/1999/xlink; xml:lang="en" service="WPS"
> serviceInstance="http://wms.derbyshire.gov.uk/geoserver/ows?;
> version="1.0.0">
> 
> JTS:centroid
> Centroid
> Returns the geometric centroid of a geometry. Output
> is a single point.  The centroid point may be located outside the
> geometry.
> 
> 
> 
> 
>  locator="geom">
> Failed to retrieve value for input
> geom
> 
> 
> 
> 
> 
>
> The actual name of the geometry column is the_geom but tried changing the
> identifier and get (this does get logged)
>
> 
> http://www.w3.org/2001/XMLSchema;
> xmlns:ows="http://www.opengis.net/ows/1.1;

Re: [Geoserver-users] Possible ways and costs for specific developments/improvements for GeoServer

[Andrea Aime]

See notes inline below:


On Wed, Apr 10, 2024 at 4:53 PM Erik Böhm  wrote:

>
> As some of those features are important for us, we are evaluating the
> option to take on this suggestion. In that sense, and because I did not
> find anything on the GeoServer Community sites, I wanted to ask how we
> could manage this, which options there would be and which would be the one
> preferred by you.
>
> How would it work if we would hire a contractor and contribute these
> features to GeoServer?
>

The GeoServer commercial support  page
offers a list of companies that can take on this kind of task.


> And for the specific feature of the GeoServer being able to fully
> interpret all definitions in SLDs exported from QGIS, would you be able to
> guess the amount of work this would take? In that way, we maybe could
> estimate the costs of hiring a developer for this feature.
>

As others, I'd urge you to come out with a specific list of features that
are missing. In GeoSolutions we did an analysis in the past and come up
with a variety of issues

   - Bits that could be exported to SLD, but are not (e.g., attribute
   dependent values and expressions)
   - Bits that are exported, but using invalid SLD syntax
   - Bits that cannot be exported, because there is no equivalent SLD syntax

The list is large, making an estimate is not very likely. Rather than "I
want to export everything possible",
approach the commercial support providers with a firm list of features you
need instead.

Cheers
Andrea
___
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] queryables ogc api features

[Andrea Aime]

Hi Bart,
gut feeling, looks like a bug in the generation of links... queryables are
a JSON schema object, so they should not respond
to a generic "application/json" type, but to a "application/schema+json"
instead.
Might  be off the mark though, I did not check what's actually going on.

To get it fixed, see this guide:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-fixes,-improvements-and-new-features-in-GeoServer

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


On Fri, Mar 29, 2024 at 4:24 PM Verbeeck Bart (AIV) via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> Dear all
>
>
>
> I noticed something that might be a bug in ogc api features
> version 2.24.x
>
>
>
> If you ask for the queryables the hrml representation is ok
>
>
> geo.api.vlaanderen.be/VHAWaterlopen/ogc/features/v1/collections/VHAG/queryables
> <https://geo.api.vlaanderen.be/VHAWaterlopen/ogc/features/v1/collections/VHAG/queryables?f=json>
>
>
>
>
> geo.api.vlaanderen.be/VHAWaterlopen/ogc/features/v1/collections/VHAG/queryables?f=json
>  gives
> a response
>
>
> geo.api.vlaanderen.be/VHAWaterlopen/ogc/features/v1/collections/VHAG/queryables?f=application/json
> gives an error
>
>
>
> {
>
> "code": "NoApplicableCode",
>
> "description": "Could not find acceptable representation"
>
> }
>
>
>
> If you check the contents of
> geo.api.vlaanderen.be/VHAWaterlopen/ogc/features/v1/collections/VHAG/queryables?f=json
>
>
>
> {
>
> "href":
> https://geo.api.vlaanderen.be/collections/VHAG/queryables?f=application%2Fjson
> ,
>
> "rel": "self",
>
> "type": "application/json",
>
> "title": "This document"
>
> },
>
>
>
> the url is wrong: “/Workspace/ogc/features/v1” is missing.
>
>
>
> So if you use the html representation to check the queryables, the links
> to “other formats” are wrong.
>
>
>
> Bart
> ___
> 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 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] Problems recreating a layer after a deletion

[Andrea Aime]

Gut feeling, you might be ignoring the relationship between featuretype and
layer. While they are separate resources,
you have to delete both of them when performing a remove.

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


On Mon, Apr 1, 2024 at 7:57 AM Phil Scadden  wrote:

> I created a layer from a datastore with:
> curl -u user:passwd -X POST -H "Content-type: text/xml" -d
> "MylayermylayerMy
> Layer
> wks:myStyleEPSG:2193"
> https://myserver/rest/workspaces/wks/datastores/wks-zl/featuretypes
>
>
>
> However, the structure in the postgis datastore so I deleted with:
>
> curl -u user:passwd -X POST -H "Content-type: text/xml"
> https://myserver/rest/layers/wks:Mylayer
>
>
>
> Doesn’t show up. However, when I tried recreate with exactly the same
> POST, I get:
>
>
>
> Resource named 'Mylayer' already exists in store: 'wks-zl'
>
>
>
> Clearly, I did delete wrong, but how do I republish via REST?
>
> 
>
> Ngā mihi, Nā Phil Scadden (he/him)
>
> Te Raraunga me te Tātaritanga Mokowā Aronuku (Geospatial Data and
> Analysis)
>
> *GNS Science* *Te Pῡ Ao*
>
> 13A Alma St, Renwick, 7204
>
> New Zealand Ph +64 27 3463185
>
>
>
> “Whāia te iti kahurangi ki te tūohu koe me he maunga teitei”
>
>
> Notice: This email and any attachments are confidential and may not be
> used, published or redistributed without the prior written consent of the
> Institute of Geological and Nuclear Sciences Limited (GNS Science). If
> received in error please destroy and immediately notify GNS Science. Do not
> copy or disclose the contents.
> ___
> 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 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] Impossible to turn off "Enable All Statistics" in > Server status > System Status

[Andrea Aime]

I've made a quick test on a GeoServer we deployed, with a NGINX proxy in
front of it (don't know the details of the deploy tough).

I can enable and disable the statistics without issues, the request
disabling them looks as follows (slightly edited for privacy):

curl '
https://some-host.org/geoserver/web/wicket/bookmarkable/org.geoserver.web.admin.StatusPage?6-3.IBehaviorListener.0-tabs-panel-refreshed~values-statistics=false'
\
  -X 'POST' \
  -H 'accept: application/xml, text/xml, */*; q=0.01' \
  -H 'accept-language: it-IT,it;q=0.9,en-GB;q=0.8,en;q=0.7,en-US;q=0.6' \
  -H 'cache-control: no-cache' \
  -H 'content-length: 0' \
  -H 'cookie: GeoServerUILanguage=en; GeoServerUILanguage=en; ' \
  -H 'origin: https://some-host.org' \
  -H 'pragma: no-cache' \
  -H 'referer:
https://some-host.org/geoserver/web/wicket/bookmarkable/org.geoserver.web.admin.StatusPage?6=false'
\
  -H 'sec-ch-ua: "Google Chrome";v="123", "Not:A-Brand";v="8",
"Chromium";v="123"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "Linux"' \
  -H 'sec-fetch-dest: empty' \
  -H 'sec-fetch-mode: cors' \
  -H 'sec-fetch-site: same-origin' \
  -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36' \
  -H 'wicket-ajax: true' \
  -H 'wicket-ajax-baseurl:
wicket/bookmarkable/org.geoserver.web.admin.StatusPage?6filter=false' \
  -H 'wicket-focusedelementid: statistics' \
  -H 'x-requested-with: XMLHttpRequest'

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


On Tue, Mar 26, 2024 at 9:47 AM Михаил Захаренков 
wrote:

> Hello.
> I'm facing the error described in
> https://osgeo-org.atlassian.net/browse/GEOS-10468.
> I am using geoserver version 2.24.2.
>
> I noticed that when you enable the option, a POST request is sent with the
> form data:
> *tabs:panel:refreshed-values:statistics: on*
>
> If you disable the checkbox, the request will be sent without a parameter.
> As a result, the server returns a 403 Forbidden error and statistics
> continue to be collected, and the checkbox becomes enabled again.
>
> It seems to me that when the checkbox is disabled,
> tabs:panel:refreshed-values:statistics: off
> should be sent, by analogy).
>
> I am aware of GEOSERVER_CSRF_WHITELIST and my domain is added to this list
> in the web.xml file.
>
> Best regards, Mike.
> ___
> 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 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

Re: [Geoserver-users] Securing WMTS service

[Andrea Aime]

I believe you want to turn on the "Data security" option in the "caching
defaults" page:
https://docs.geoserver.org/main/en/user/geowebcache/config.html#geoserver-data-security

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


On Tue, Mar 26, 2024 at 2:17 PM geospatial techno <
geospatial.techno2...@gmail.com> wrote:

> Hi there,
> Is there a way to secure the WMTS service in GeoServer that is not listed
> in the security service dropdown?
> ___
> 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 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] WFS query of a Vector Mosaic datastore

[Andrea Aime]

Yes, confirmed, it's happening while the WFS 1.1&/2.0 GetFeature tries to
compute the total features matched.
The store lacks an efficient path to perform such a count, and resorts to a
"load everything and filter in memory".

So far the store has only been used (in production) for WMS purposes and
this code needs to be developed
to efficiently support WFS usage (or just use WFS 1.0, does not seem to
happen in that case, at least for GML output).

I'd recommend to open a jira ticket, and then, if you are in any urgent
need to get a fix, look at this guide:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-fixes,-improvements-and-new-features-in-GeoServer
(consider the talking part done, it's the resourcing part that is missing)

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


On Tue, Mar 19, 2024 at 9:28 PM Richard Matsunaga via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> Hi Andrea,
>
>
>
> The SLD= was a mistake and has been removed. Has no effect anyway it seems.
>
>
>
> I checked the bounding boxes produced for each row and they seems fine. I
> then built a query with Postgis to filter by a bounding box and it returned
> a subset of results.
>
>
>
> The logs show this query and, unless it is incomplete, it does not seem to
> be filtering by the bounding box at all.
>
> SELECT "ogc_fid",encode(ST_AsEWKB("wkb_geometry"), 'base64') as
> "wkb_geometry","params" FROM "vector_products"."raw_points_index";
>
> Richard
>
>
>
> *From:* Andrea Aime 
> *Sent:* Tuesday, March 19, 2024 5:23 AM
> *To:* Richard Matsunaga 
> *Cc:* geoserver-users@lists.sourceforge.net
> *Subject:* Re: [Geoserver-users] WFS query of a Vector Mosaic datastore
>
>
>
> You don't often get email from andrea.a...@geosolutionsgroup.com. Learn
> why this is important <https://aka.ms/LearnAboutSenderIdentification>
>
> Hi Richard,
>
> the mosaic should query and open only the files whose geometry, in the
> mosaic index, intersects the bbox you provided.
>
> So first, check the mosaic index, which entries are actually matching the
> provided bbox?
>
>
>
> The "" bit does not make sense in a GetFeature, makes me wonder if
> you're passing it by mistake, or if you have some
>
> customization/plugin that makes use of it?
>
>
> 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 th

Re: [Geoserver-users] Feature type details - customize attributes via rest api?

[Andrea Aime]

Hi Nikolaus,
the attribute customization can be performed once by GUI, check the
representation you get from the REST API, and then you can replicate.
However mind, that tool controls the attribute available for the layer in
all requests and services, not just GetFeatureInfo.
If you want to hide an attribute in feature info, but use it in GetMap,
that's not the tool you need to use. You'll need to use something like
GeoFence instead.

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


On Tue, Mar 19, 2024 at 10:05 AM Nikolaus Pruzsinszky 
wrote:

> Hi user group,
> does anyone know if it is possible to customize the attributes of a
> feature type using the rest api?
> I would like to limit the number of attributes that are exposed to a
> getfeatureinfo request - basically I just want to remove one or the other
> attribute. Since my data is published using only the rest api (automation),
> I can not use the GUI to do that. I know that this could maybe also be
> achieved using the freemarker templates, but this is not my prefered way of
> doing it.
>
> Cheers, Niko
> ___
> 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 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] WFS query of a Vector Mosaic datastore

[Andrea Aime]

Hi Richard,
the mosaic should query and open only the files whose geometry, in the
mosaic index, intersects the bbox you provided.
So first, check the mosaic index, which entries are actually matching the
provided bbox?

The "" bit does not make sense in a GetFeature, makes me wonder if
you're passing it by mistake, or if you have some
customization/plugin that makes use of it?

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


On Fri, Mar 15, 2024 at 10:19 PM Richard Matsunaga via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> Hello,
>
>
>
> We are using the Vector Mosaic datastore (
> https://docs.geoserver.org/main/en/user/community/vector-mosaic/index.html).
> It seems to functioning well for our needs except for one case.
>
>
>
> With a WFS GetFeature request, the response time is so slow our load
> balancer times out before the response comes back grom GeoServer. The
> timeout is 1 min, a typical WFS GetFeature request takes about 2 mins
> according to the GeoServer logs.
>
>
>
> Our mosaic index is stored in PostgreSQL and the mosaic flat files are
> FlatGeoBuf.
>
>
>
> From the GeoServer logs, it appears that the entire index is being queried
> instead of being filtered by the input bounding box to the GetFeature. We
> have over 1000 rows in the index. I am guessing each of these files are
> then being queried against the bounding box, but I’m not sure.
>
>
>
> It starts with this query:
>
>
>
> SELECT "ogc_fid",encode(ST_AsEWKB("wkb_geometry"), 'base64') as
> "wkb_geometry","params" FROM "vector_products"."raw_points_index";
>
>
>
> Then we get many entries like:
>
>
>
> [geotools.vectormosaic] - Found and set datastore for granule null with
> params {url=file:/
> /GeoserverData/farmtrx/raw_points/dALzgubWabg8nVZlObJZU_raw_points_32814/dALzgubWabg8nVZlObJZU_raw_points_32814.fgb}
>
>
>
> Eventually it seems to succeed, but long after the gateway timed out:
>
>
>
> "GET
> /geoserver/wfs?service=WFS=2.0.0=GetFeature=application/json=-8428045.938524414,5672717.233576572,-8427400.045285502,5673091.775131803,EPSG:3857=raw_points=file:///
> /styles/abXuSt4KMlbFn8SG84bHX/abXuSt4KMlbFn8SG84bHX_33272_raw_points_hct.sld=100=yldt_ha"
> took 119988ms
>
>
>
> Previously we stored all the vector data in PostgreSQL and this GetFeature
> query returned nearly instantaneously. Am I correct that it seems the
> original query would be better to be filtered by the bounding box, thus
> returning one or a few rows?
>
>
>
> Thanks,
>
> Richard
> ___
> 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 mailing list

Please make sure you read the following two resources bef

Re: [Geoserver-users] WFS 2.0.0 GetFeature ignores leading zero in literal Filter

[Andrea Aime]

Yes, I agree the ticket was resolved by mistake. Re-opened.

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


On Mon, Mar 18, 2024 at 6:19 PM BORGHINO, JEREMY <
jeremy.borgh...@worldline.com> wrote:

> Hi,
>
>
>
> I am having an issue while trying to use a filter in a WFS GetFeature
> Request.
>
> I am trying to filter on a *string* column with the following query param
> in my GET request:
>  Filter=*my_column*
> *01*
>
> But it appears that the leading zero is trimmed – instead of fetching 01
> it fetches 1.
>
> I found the same issue here marked as resolved
> https://osgeo-org.atlassian.net/browse/GEOS-7540 but the issue is still
> here in GEOSERVER 2.23.2.
>
>
>
> Thanks for your help,
>
> Regards,
>
> Jeremy
>
> Worldline, Cardlink, GoPay and Santeos are registered trademarks and trade
> names owned by the Worldline Group. This e-mail and any documents attached
> are confidential and intended solely for the addressee. It may also be
> privileged. If you are not the intended recipient of this e-mail, you are
> not authorized to copy, disclose, use or retain it. Please notify the
> sender immediately and delete this e-mail (including any attachments) from
> your systems. As e-mails may be intercepted, amended or lost, they are not
> secure. Therefore, Worldline’s and its subsidiaries’ liability cannot be
> triggered for the message content. Although the Worldline Group endeavors
> to maintain a virus-free network, we do not warrant that this e-mail is
> virus-free and do not accept liability for any damages, losses or
> consequences resulting from any transmitted virus if any. The risks are
> deemed to be accepted by anyone who communicates with Worldline or its
> subsidiaries by e-mail.
> Please consider the environment before printing, sending or forwarding
> this email.
>
> ___
> 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 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] Tomcat warning message

[Andrea Aime]

Hi Georg,
it's GeoServer trying to figure out which rasterizer is used by the JVM,
some as faster than
others. It's normal behavior.

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


On Mon, Mar 11, 2024 at 10:19 AM Georg Weickelt <
georg.weick...@ibedelmann.de> wrote:

> I have Geoserver version 2.24.2 running under Tomcat 9.0.85. Tomcat
> displays this error message:
>
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.geoserver.web.admin.StatusPanel (
> file:/srv/tomcat/webapps/geoserver/WEB-INF/lib/gs-web-core-2.24.2.jar) to
> method sun.java2d.pipe.RenderingEngine.getInstance()
> WARNING: Please consider reporting this to the maintainers of
> org.geoserver.web.admin.StatusPanel
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
>
> Do I need to worry about this?
>
>
> Georg
> ___
> 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 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] Problem with symlinks

[Andrea Aime]

I don't have experience using symlinks for the data dir... what errors do
you get?
I guess you'll get some stack traces in the logs, can you share them?

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


On Fri, Mar 15, 2024 at 2:35 PM Uwe Seher  wrote:

> Same Problem on openSUSE15.5, no symlinks accepted.
>
> Am Mo., 11. März 2024 um 15:32 Uhr schrieb Uwe Seher  >:
>
>> Hi!
>> I am trying u migrate our geoserver installation from 2.19.x to 2.24.1
>> and from aur old server to a new one running on debian 11/java 11. This
>> part is ok, the new instance is up and running. It is now running on a vm
>> which should reference the data-directory from another machine. We did this
>> with the old instance too (with nfs), the new one references the data-dir
>> on the host machine. This works too, the datadir is accessible read/write
>> for the tomcat user. When i try to set this as the data-dir for geoserver
>> by creating a symlink this does not work. I tried it too with the original
>> data-dir from the installation and it does not work when i move it and
>> create a symlink in the same dir. The same dir works when it is accessed
>> directly. I do not understand what happens here, because i did this several
>> times before.
>>
>> Thank you in advance
>> Uwe Seher
>>
> ___
> 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 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] Publishing Raster data from PostGres-Table

[Andrea Aime]

Hi Felix,
while I have never tried it out, there is a community module that
should allow publishing rasters from within PostgreSQL databases:
https://docs.geoserver.org/main/en/user/community/pgraster/pgraster.html

Mind, it's unsupported, and I know nobody using it. Storing rasters in
databases never became popular, as far as I know,
it's a good idea if you want to perform spatial analysis inside the DB, but
for map rendering, better keep your data in
well optimized GeoTIFF files instead.

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


On Fri, Mar 15, 2024 at 4:16 PM Felix Keßler via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> Hey Guys,
> I am trying to publish raster-data from my Postgres-Table. I am
> currently using MapServer as I could not find a working solution to use
> geoserver, but the MapServer is pretty slow and I prefer GeoServer for
> other layers etc. and thus would like to know if someone has a working
> example using geoserver?
>
> Thanks in advance,
> Felix
>
>
>
> ___
> 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 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] Style REST API removing WellKnownName

[Andrea Aime]

Yep, as Ian says, "pretty printing" of the style has been the default since
the beginning of the REST API availability.
However, there is a query paameter you can append to your style
publication, that allows skipping the pretty print:
"...?raw=true".

Looks like it's not documented in the REST API, although it has also been
in the API for many years.

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


On Fri, Mar 15, 2024 at 12:06 PM Ian Turton  wrote:

> It has always dropped default values e.g. square marks, black strokes and
> grey fills etc. It avoids cluttering up the SLD with unnecessary elements.
> The simplest answer would seem to be for you to leave such defaults out of
> your SLD files (or ignore them when looking for differences).
>
> Ian
>
> On Fri, 15 Mar 2024 at 10:49, Alexandre Gacon 
> wrote:
>
>> Hello,
>>
>> When I send a style with a WellKnowName of type square to GeoServer with
>> a REST API, the WellKnownName is removed from the SLD definition, because
>> square is the default value.
>>
>> As a consequence, when I retrieve the SLD with a GET on the REST API and
>> I compare it to my definition, it is detected as a difference.
>>
>> Shouldn't the REST API respect the original content sent?
>>
>> --
>> Alexandre Gacon
>> ___
>> 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
>>
>
>
> --
> Ian Turton
> ___
> 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 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] App Schema layer dimensions

[Andrea Aime]

Hi Nuno,
that code you reference returns a collection, which is then used to collect
the values in another method, using heavily feature visitors to get
min/max/unique values in an efficient way:
https://github.com/geoserver/geoserver/blob/891f439892aeb3ffea5de6e91e4330f798c7/src/wms/src/main/java/org/geoserver/wms/WMS.java#L1396

Wondering if the app-schema store is able to support those visits, some
specific points about it:

   - MappingFeatureCollectin does not seem to be able to delegate the visit
   downstreams, so it will run it in memory (inefficient)
   - The visitors are built with local attribute names, without namespace
   context. Would a lookup in that condition work, against a complex feature?

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


On Wed, Mar 13, 2024 at 7:19 PM Nuno Oliveira <
nuno.olive...@geosolutionsgroup.com> wrote:

> Hi Kamilla,
> I haven't encountered a scenario where I've worked with App-Schema complex
> data alongside time dimensions, so I can't provide firsthand experience on
> that topic.
> That being said, upon reflection, I can't immediately think of a reason
> why it wouldn't work. I've checked the code where the dimension values are
> collected, and at first glance, it seems that it should function properly
> with complex features:
>
>-
>
> https://github.com/geoserver/geoserver/blob/891f439892aeb3ffea5de6e91e4330f798c7/src/wms/src/main/java/org/geoserver/wms/WMS.java#L1677-L1691
>
> Hence, based on my initial assessment, I believe this functionality should
> work. However, I haven't used dimensions with complex features before, so
> it's possible that there could be an undetected bug within that integration.
> This situation would require a debugging session to fully understand
> what's happening.
>
> Kind regards,
> Nuno Oliveira
>
> On Tue, Mar 12, 2024 at 8:22 PM Kamilla Kisova <
> kamilla.kis...@microstep-mis.com> wrote:
>
>> Hi team,
>>
>> I've been trying to adjust an App Schema layer we have. We are trying to
>> bring this layer alive with current data, since so far it has been
>> sitting on the server with only two whole timestamps' worth of test data
>> available.
>>
>> So far we have relied on the WMS GetCapabilities to get appropriate
>> dimension information, but this time we noticed that the App Schema
>> layer's capabilities only states "> default="current" units="ISO8601"/>", no matter the interval and default
>> value we set. This layer is based on a Postgres database, and I can see
>> in the configuration files that the time dimension is set appropriately,
>> very similarly to SQL views.
>>
>> Where could I find more information about App Schema stores/layers and
>> dimensions? I've tried looking around on the Geoserver documentation for
>> App Schema, but haven't found anything on the dimensions.
>>
>> Best regards,
>> Kamilla Kisova
>>
>>
>> ___
>> 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://git

Re: [Geoserver-users] Recommended way to run Geoserver

[Andrea Aime]

What Brad said, indeed!

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


On Mon, Mar 4, 2024 at 12:41 PM Brad Hards  wrote:

> If you're familiar with an approach and it works for your needs, I would
> stick with that.
>
> If not, I can only suggest giving the options a try and seeing what you
> like. There are no bad ways (except maybe on Windows...).
>
> Brad
>
> On 4 Mar 2024 7:56 pm, Kristian Nils Robin Morin via Geoserver-users <
> geoserver-users@lists.sourceforge.net> wrote:
>
> Hi,
>
> There are several different ways to run geoserver depending on the
> situation.
> But given you don't have any specific requirements more than adding
> plugins to the installation, which one would you choose?
>
> The major options are running it through a Tomcat servlet container or
> dokker.
> There are many docker containers from different distributions to choose
> from. Images from Kartoza, Geosolutions and the official repository to name
> a few. It's a bit of a minefield. Previously I just downloaded the war
> file, added my plugins and I was up and running.
> I attended Foss4G in Firenze 2022 and I have a vague memory that Andreas
> Aimee recommended running the official version, but I might remember wrong.
> How would I go about it to select what method to run in production
> with minimal overhead?
>
>
>
>
>
>
> ___
> 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 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] ogc api features filter: during

[Andrea Aime]

I'm just guessing here (answering from phone), but if memory serves me
right, the default filter language changed from ECQL to CQL2 (following the
evolution of the standard), with an implementation that's also not up to
date (CQL2 keeps on changing). Try using filter-lang to choose ECQL instead?

Ah, found the syntax for CQL2, something like this (found it in tests for
our current implementation):

T_DURING(ATTR1, INTERVAL(TIMESTAMP('2006-11-30T01:30:00Z'),
TIMESTAMP('2006-12-31T01:30:00Z')))

However, it seems the CQL2 syntax evolved in the meantime, and the function
in the latest version can only be used
to compare an interval with another interval, and not any longer an instant
with an interval. Check the standard DRAFT here:
https://docs.ogc.org/DRAFTS/21-065.html

Long story short, if you want something that is stable interface wise, at
least for the time being, add "=ecql-tex" to your request
and keep on using GeoServer's own CQL flavor.


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


On Sat, Mar 2, 2024 at 9:35 AM Jody Garnett  wrote:

> Verbeeck,
>
> The best way to assist with this project is to pitch in and help during an
> ogc / osgeo code sprint. Or to interact with the developer Andrea who is
> seeking funding to work on this module.
>
> It is really nice that you are testing, since the specification is a
> moving target I am not surprised if some functionality changes between 2.19
> and 2.24 (which is quite a long time for a community module).
>
> I also would love to see this module improved, but do not know how to get
> it funded (or myself time to work on it).
> --
> Jody Garnett
>
>
> On Mar 1, 2024 at 6:33:40 AM, Verbeeck Bart (AIV) via Geoserver-users <
> geoserver-users@lists.sourceforge.net> wrote:
>
>>
>>
>> Dear all
>>
>>
>>
>> The question below appears to be under LDAP snow.
>>
>> Meanwhile I found another time related issue
>>
>> in 2.19 time can be between single quotes (but doesn’t have to
>>
>> geo.api.vlaanderen.be/GIPOD/ogc/features/collections/HINDERGEVOLG/items?f=application/json=0=EPSG:31370=20=HindranceStart
>> < %272024-02-28T09:19:48.330Z%27
>> <https://geo.api.vlaanderen.be/GIPOD/ogc/features/collections/HINDERGEVOLG/items?f=application/json=0=EPSG:31370=20=HindranceStart%20%3C%20%272024-02-28T09:19:48.330Z%27>
>>
>> geo.api.vlaanderen.be/GIPOD/ogc/features/collections/HINDERGEVOLG/items?f=application/json=0=EPSG:31370=20=HindranceStart
>> < 2024-02-28T09:19:48.330Z
>> <https://geo.api.vlaanderen.be/GIPOD/ogc/features/collections/HINDERGEVOLG/items?f=application/json=0=EPSG:31370=20=HindranceStart%20%3C%202024-02-28T09:19:48.330Z>
>>
>>
>>
>> in 2.24 it has to be between single quotes
>>
>> geo.api.beta-vlaanderen.be/GIPOD/ogc/features/collections/HINDERGEVOLG/items?f=application/json=0=EPSG:31370=20=HindranceStart
>> < %272024-02-28T09:19:48.330Z%27
>> <https://geo.api.beta-vlaanderen.be/GIPOD/ogc/features/collections/HINDERGEVOLG/items?f=application/json=0=EPSG:31370=20=HindranceStart%20%3C%20%272024-02-28T09:19:48.330Z%27>
>>
>> geo.api.beta-vlaanderen.be/GIPOD/ogc/features/collections/HINDERGEVOLG/items?f=application/json=0=EPSG:31370=20=HindranceStart
>> < 2024-02-28T09:19:48.330Z
>> <https://geo.api.beta-vlaanderen.be/GIPOD/ogc/features/collections/HINDERGEVOLG/items?f=application/json=0=EPSG:31370=20=HindranceStart%20%3C%202024-02-28T09:19:48.330Z>
>>  (g

[Geoserver-users] GeoServer 2.23.5 released

[Andrea Aime]

Hi all,
GeoServer 2.23.5 has been released, the announcement can be found here:
https://geoserver.org/announcements/2024/02/18/geoserver-2-23-5-released.html

This is the last planned maintenance release of GeoServer 2.23.x, providing
existing installations with minor updates and bug fixes. Sites using the
2.23.x series are encouraged to upgrade to GeoServer 2.24.x, or eventually
wait next month for the 2.25.0 release, and upgrade their installation,
with the help of the upgrade guide
<https://docs.geoserver.org/main/en/user/installation/upgrade.html#notes-on-upgrading-specific-versions>
.

Best regards
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] SchemaLocations WFS Responses

[Andrea Aime]

Anna,
do you need them to be all local, or would it be ok if they were all
sitting on schemas.opengis.net?
If the latter is ok, then maybe this setting, found in the WFS admin page,
is an answer: "encode canonical wfs schema location"

[image: image.png]

Cheers
Andrea


On Wed, Feb 21, 2024 at 11:31 AM Anna-Lena Hock via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> Hello,
>
> Usually the schemaLocations are generated by Geoserver and use the same
> schemaLocation like the service-uri. Every schemaLocation points to those
> local uri, but there is only one schemaLocation which points to
> schemas.opengis.net. And there are other references to schema.opengis.net
> which are downloaded and defined twice in concequence - once by
> schema.opengis.net and our local uri.
>
> I hope this one was better to understand.
>
> I will open an issue on jira now.
> Thanks for the reply!
>
> Kind regards
> Anna-Lena
>
> Am 21.02.2024 um 08:17 schrieb Roar Brænden :
>
> Hi,
> Ï'm struggling to understand what you are asking about.
> You're saying:
>
> The user downloaded all the schemaLocations, which were all referenced
> locally until he came to this reference:
>
>
> What was he using when he downloaded those schemaLocations?
>
> How did those xsd-files end up on that server
> https://sgx.geodatenzentrum.de/web_geoserver_schemas?
>
> I suppose a solution would be to go through all the xsd-files at that
> location to make sure none of them are referring to an external entity if a
> local copy is present.
>
> Best regards,
> Roar Brænden
>
>
> 20. feb. 2024 kl. 13:07 skrev Anna-Lena Hock via Geoserver-users <
> geoserver-users@lists.sourceforge.net>:
>
> Hello,
>
> Unfortunately there was no reply to my question. Is it useful to open an
> issue on jira?
>
> Kind regards,
> Anna-Lena
>
> Am 31.01.2024 um 09:50 schrieb Anna-Lena Hock :
> Hello everyone,
>
> currently we are facing problems with the schemaLocations used in the
> WFS-Responses.
>
> The user downloaded all the schemaLocations, which were all referenced
> locally until he came to this reference:
>
> https://sgx.geodatenzentrum.de/web_geoserver_schemas/gml/3.2.1/coordinateOperations.xsd
> Here is the problematic schemaLocation to schemas.opengis.net. Now the
> problems continues, because the objects will be defined twice - locally
> from sgx.geodatenzentrum.de and from schemas.opengis.net.
>
> Is there a workaround for this problem or a possibility to solve it?
>
> Kind regards,
> anna-lena
>
>
>
>
> ___
> 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 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  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 scrive

Re: [Geoserver-users] Adding store - File input options

[Andrea Aime]

Hi,
action happens in here:
https://github.com/geoserver/geoserver/blob/9e40cbbccb9626b8d08516c8eacaf5a8f168189b/src/web/core/src/main/java/org/geoserver/web/wicket/browser/GeoServerFileChooser.java#L31

As you can see there's already a property to get rid of access outside of
the data directory, but nothing
to lock the browser to a particular sub-folder of it

Cheers
Andrea

On Wed, Feb 21, 2024 at 10:49 AM Šimon Janovič  wrote:

> I created a folder user-data in data_dir that contains a folder for each
> user. When inputting a file I'd like to programmatically add a 4th option
> User directory, which would refer to *data_dir/user-data/[logged-in
> user]/*. I'd also like to dispose of the options '/' and 'Home directory'
> as it exposes the '/root' directory and the entire file system of my
> server. Could anybody point me to the set of files in which this is
> programmed? I'd like to make some changes as long as they're not
> destructive.
> [image: file_input.png]
> Thank you, have a nice day.
>
>  - Šimon Janovič
>
> ___
> 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  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] Deleting database table through REST API

[Andrea Aime]

On Tue, Feb 20, 2024 at 2:52 PM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> If one uploads in replace mode, a lot of damage can be done... the old
> data is removed before adding the new one.
> All one needs is to upload a file that can be self described properly, but
> cannot be properly read (corrupted shapefile for example).
>

Correcting myself here, wrong example, as the delete and re-populate uses a
transaction, the above won't cause data loss.
One can still go destructive by setting the "update" query parameter to
"overwrite" by mistake though.

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] Restrict WMS layer to bounding box

[Andrea Aime]

Hi,
it cannot be done using the default security subsystem, but the GeoFence
extension allows to perform data clipping
on polygons based on the current user instead (it's a bit complicated to
use though).

Cheers
Andrea

On Tue, Feb 20, 2024 at 3:48 PM Markus Strauch 
wrote:

> Hello,
>
>
>
> is it possible to restrict the visibility of a layer to a certain bounding
> box, ideally on a per-user basis? Think of a network operator that wants to
> publish different parts of the network to different construction companies.
>
>
>
> I have tried to publish a shapefile and decrease the size of the bounding
> box (both native coordinates and long/lat), but still Geoserver shows
> everything that is on the layer, even beyond that bounding box.
>
>
>
>
>
>
>
>
>
> --
> Mit freundlichen Grüßen,
>
> Markus Strauch
>
> ---
>
>
> topoGRiDS GmbH
> Reichspräsidentenstr. 21-25, 45470 Mülheim a. d. Ruhr
> Duisburg HRB 17947
> Geschäftsführer: Lutz Kalkoff, Heike Feuster
> 
> Telefon +49 (208) 698880-11
> Telefax +49 (208) 698880-12
> Mobil   +49 (163) 43000-64
> eMail   markus.stra...@topogrids.de
> -
> www.topogrids.de
>
>
> ___
> 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  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] Deleting database table through REST API

[Andrea Aime]

data). It's symmetric.
If you want to remove the ability to delete data, you need to get rid of
the ability to create it as well.


> Finally, in your current-api-breakdown reply, you mention the only
> existing related endpoint is to delete also the data for a coverage:
>
> > DELETE
> /workspaces/{workspaceName}/coveragestores/{storeName}?deleteType=none/all/metadata.
> With "metadata" the configuration files are all removed (e.g., the mosaic
> configuration files), with "all" the actual raster data is removed as well
>
> Well, this is the perfect example of what I'm proposing. Note how it's an
> operation on the CoverageStore and not on the Coverage.
> I concede that's probably related to the fact that CoverageStores support
> a single Coverage?
>

No, it's meant to go and destroy all coverages and associated data
contained in the mosaic
<https://github.com/geoserver/geoserver/blob/0ab715486a958632e9e7d54ad5746a4858189f3b/src/restconfig/src/main/java/org/geoserver/rest/catalog/CoverageStoreController.java#L198>,
if called that way.
If the same is called on the single coverage, it will delete only the data
files associated to that coverage, and that coverage alone.
E.g., if a NetCDF file happens to offer content for multiple coverages, it
will be removed only when the last coverage referencing it
it is removed as well.

These APIs are meant to be used by data managers that pay attention to what
they do ("admin" in GeoServer is tha same
as "root" on Linux, all powerful).

A separate resource makes a difference only in your mind, in my experience
I'm just as easily going to make a mistake in the path
or in the query string (see example in my previous mail).


> I think that exposes my point of view in a more civil way, and yes, we'll
> probably have to go through the GSIP process.
>

Thank you for the explanation, unfortunately it did not change my mind.
Further discussion is pointless, let's get the PSC members to vote, and
take responsibility for the result, whatever it is.
I'm happy to let the proposal pass anyways, if the rest of the PSC is happy
with the direction you're suggesting, but I want my disagreement to be on
record.

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] SchemaLocations WFS Responses

[Andrea Aime]

Hi Anna,
it is your right to open a ticket in Jira. and if you provide steps to
reproduce (sample data, mapping files and so on) it would
be useful as well. But I very much doubt it will change anything, in terms
of getting an answer.

If you need a solution now, see this guide:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-fixes,-improvements-and-new-features-in-GeoServer

Cheers
Andrea


On Tue, Feb 20, 2024 at 1:11 PM Anna-Lena Hock via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> Hello,
>
> Unfortunately there was no reply to my question. Is it useful to open an
> issue on jira?
>
> Kind regards,
> Anna-Lena
>
> > Am 31.01.2024 um 09:50 schrieb Anna-Lena Hock :
> > Hello everyone,
> >
> > currently we are facing problems with the schemaLocations used in the
> WFS-Responses.
> >
> > The user downloaded all the schemaLocations, which were all referenced
> locally until he came to this reference:
> >
> https://sgx.geodatenzentrum.de/web_geoserver_schemas/gml/3.2.1/coordinateOperations.xsd
> > Here is the problematic schemaLocation to schemas.opengis.net. Now the
> problems continues, because the objects will be defined twice - locally
> from sgx.geodatenzentrum.de and from schemas.opengis.net.
> >
> > Is there a workaround for this problem or a possibility to solve it?
> >
> > Kind regards,
> > anna-lena
>
>
>
> ___
> 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  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] SAML Authentication extension on GeoServer 2.24.2

[Andrea Aime]

The SAML community module has been dropped and is no longer available, due
to lack of a developer to look after it.
If anyone is interested in becoming the module maintainer, just let us
know, and we can give you directions on how
to write a pull request to resurrect the module

Best Regards
Andrea


On Fri, Feb 16, 2024 at 2:12 PM Vinay Kumar 
wrote:

> Hi,
>
> We are looking for SAML auth on geoserver 2.24 official version. However
> on community version
> its there for 2.23.x only.
>
> Is it going to be available soon on stable version soon on officially.
>
> Or is there any issue for SAML extension.
>
>
> Regards,
> Vinay
> ___
> 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  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] ImageMosaic location - URLs?

[Andrea Aime]

On Fri, Feb 16, 2024 at 6:42 AM Alexander Petkov  wrote:

> If your tiles are indexed by time, this might be a workable solution.
> However, for a horizontally tiled mosaic using remotely stored tiles might
> not be practical.
>

"remotely"is the key word here... the server GeoServer is running on must
be in the same cloud, and in the same "region" of the cloud, as the bucket
its accessing, to get decent performance.

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] Deleting database table through REST API

[Andrea Aime]

Ok,
let's start over with more context. In particular, let's start with the
existing API and how it works in terms of "native" resources, and what
"dangerous" functionality is already there.

*List of native resources*
How does one get a list of resources (feature types, coverages, wms and
wmts layers), all GET requests here:

   - 
/workspaces/{workspaceName}/datastores/{storeName}/featuretypes?list=all/available
   (either all of them, or the ones non configured)
   - /workspaces/{workspace}/coveragestores/{store}/coverages?list=all
   (returns both configured and non configured, no option implies only
   configured)
   - /workspaces/{workspace}/wmsstores/{wmsstore}/wmslayers/{wmslayer} ->
   no ability to list available layers here!
   -
   
/workspaces/{workspace}/wmtsstores/{wmtsstore}/layers?list=available/configured

When the parameters have the same name, they do the same thing, but the
availability of them is spotty. The only type of native resource that
cannot be enumerated in the WMS layer one.

*Exploring a non configured native resource*

This does not seem to be available for any type of native resource. This
would be useful, although not part of Cecile's original request.

*Creation of new native resources*
How does one create a new native resource that was not there:

   - POST 
/workspaces/{workspaceName}/datastores/{storeName}/{method}.{format}?target= wrote:

> Two wrongs don't make a right, IMHO.
> I'd rather break convention than introduce such a dangerous parameter to
> an existing API endpoint and change its semantics
>
> I'm not talking about a rewrite of the REST API, but a new verb to the
> existing API. Don't see how that'd make it harder for the people that's
> used to it, when it doesn't even exist. Used the the rest api having all
> sorts of parameters I take it. So how much harder is it when I ask "how do
> I delete a table in my database?"
> - oh, just need to add this param to DELETE
> ../stores/mystore/featuretypes/xxx
> - or, oh, just need to call DELETE ../stores/mystore/drop/xxx
>
> For the former, you need to update the documentation saying if you pass
> this, then it does this, if you pass this other parameter then it does this
> other thing. Beware to check all your scripts, because if you accidentally
> leave this parameter on, your company database will be destroyed.
> As opposed to not changing the current api and adding an endpoint that
> says:
> This will delete the database table. Fails in case there's an existing
> FeatureType using it.
>
> My point is this deserves its own endpoint. Way more explicit and less
> error prone than a new param to the current delete featuretype operation,
> which would change its semantics so drastically.
>
> In any case, that's just my opinion.
>
> Cheers,
> Gabe
>
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
> *Gabriel Roldán*
> Geospatial Developer
>
>
>
> On Thu, Feb 15, 2024 at 1:18 PM Andrea Aime <
> andrea.a...@geosolutionsgroup.com> wrote:
>
>> On Thu, Feb 15, 2024 at 3:00 PM Gabriel Roldan 
>> wrote:
>>
>>> I mean "increases complexity and difficults understanding", of course.
>>>
>>
>> But parameters are already widely used in the GeoServer REST API, and
>> "cascade" is used in other places as well.
>> This would be breaking convention, making the API harder to use for those
>> that are already used to it.
>>
>> Don't get me wrong, I know the GeoServer REST API is old and would need a
>> rewrite, but that's the key point, a rewrite would be the time to break
>> compatibility and adopt new ways of doing things.
>>
>>
>>>
>>>
>>>> question arises of how to determine which table to delete once you
>>>> deleted the FeatureType. I guess it should be an operation of the DataStore
>>>> and not of the FeatureType, and use the FeatureType's nativeName to
>>>> distinguish?
>>>>
>>>
>> The REST API only returns configured feature types by default. There is
>> (guess what?) a parameter in the "featuretypes" resource, called "list",
>> that can take
>> 3 different values:
>>
>>- "configured" (default if not specified): only lists the configured
>>feature types (links to the feature type info resource)
>>- "available": returns the native feature types not yet configured
>>(mind, only their names)
>>- "available_with_geom": same as above, bon only spatial ones
>>- "all": returns all of them, configured or available (again, just
>>names)
>>
>> The FeatureTypeController

Re: [Geoserver-users] Deleting database table through REST API

[Andrea Aime]

I'm in disagreement with both the direction taken and the attitude shown,
best to put an end to it and make it go through a formal GSIP instead (when
someone has the resources to spend on both the discussion and
implementation of it)

Regards
Andrea



Il gio 15 feb 2024, 20:19 Gabriel Roldan  ha
scritto:

> Two wrongs don't make a right, IMHO.
> I'd rather break convention than introduce such a dangerous parameter to
> an existing API endpoint and change its semantics
>
> I'm not talking about a rewrite of the REST API, but a new verb to the
> existing API. Don't see how that'd make it harder for the people that's
> used to it, when it doesn't even exist. Used the the rest api having all
> sorts of parameters I take it. So how much harder is it when I ask "how do
> I delete a table in my database?"
> - oh, just need to add this param to DELETE
> ../stores/mystore/featuretypes/xxx
> - or, oh, just need to call DELETE ../stores/mystore/drop/xxx
>
> For the former, you need to update the documentation saying if you pass
> this, then it does this, if you pass this other parameter then it does this
> other thing. Beware to check all your scripts, because if you accidentally
> leave this parameter on, your company database will be destroyed.
> As opposed to not changing the current api and adding an endpoint that
> says:
> This will delete the database table. Fails in case there's an existing
> FeatureType using it.
>
> My point is this deserves its own endpoint. Way more explicit and less
> error prone than a new param to the current delete featuretype operation,
> which would change its semantics so drastically.
>
> In any case, that's just my opinion.
>
> Cheers,
> Gabe
>
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
> *Gabriel Roldán*
> Geospatial Developer
>
>
>
> On Thu, Feb 15, 2024 at 1:18 PM Andrea Aime <
> andrea.a...@geosolutionsgroup.com> wrote:
>
>> On Thu, Feb 15, 2024 at 3:00 PM Gabriel Roldan 
>> wrote:
>>
>>> I mean "increases complexity and difficults understanding", of course.
>>>
>>
>> But parameters are already widely used in the GeoServer REST API, and
>> "cascade" is used in other places as well.
>> This would be breaking convention, making the API harder to use for those
>> that are already used to it.
>>
>> Don't get me wrong, I know the GeoServer REST API is old and would need a
>> rewrite, but that's the key point, a rewrite would be the time to break
>> compatibility and adopt new ways of doing things.
>>
>>
>>>
>>>
>>>> question arises of how to determine which table to delete once you
>>>> deleted the FeatureType. I guess it should be an operation of the DataStore
>>>> and not of the FeatureType, and use the FeatureType's nativeName to
>>>> distinguish?
>>>>
>>>
>> The REST API only returns configured feature types by default. There is
>> (guess what?) a parameter in the "featuretypes" resource, called "list",
>> that can take
>> 3 different values:
>>
>>- "configured" (default if not specified): only lists the configured
>>feature types (links to the feature type info resource)
>>- "available": returns the native feature types not yet configured
>>(mind, only their names)
>>- "available_with_geom": same as above, bon only spatial ones
>>- "all": returns all of them, configured or available (again, just
>>names)
>>
>> The FeatureTypeController delete mapping already has a "recurse" flag to
>> delete layers while the feature type is removed.
>> Now here there is a risk of confusion between "recurse" and "cascade", a
>> "removeData" flag would probably avoid confusion.
>>
>> 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

Re: [Geoserver-users] Deleting database table through REST API

[Andrea Aime]

On Thu, Feb 15, 2024 at 3:00 PM Gabriel Roldan 
wrote:

> I mean "increases complexity and difficults understanding", of course.
>

But parameters are already widely used in the GeoServer REST API, and
"cascade" is used in other places as well.
This would be breaking convention, making the API harder to use for those
that are already used to it.

Don't get me wrong, I know the GeoServer REST API is old and would need a
rewrite, but that's the key point, a rewrite would be the time to break
compatibility and adopt new ways of doing things.


>
>
>> question arises of how to determine which table to delete once you
>> deleted the FeatureType. I guess it should be an operation of the DataStore
>> and not of the FeatureType, and use the FeatureType's nativeName to
>> distinguish?
>>
>
The REST API only returns configured feature types by default. There is
(guess what?) a parameter in the "featuretypes" resource, called "list",
that can take
3 different values:

   - "configured" (default if not specified): only lists the configured
   feature types (links to the feature type info resource)
   - "available": returns the native feature types not yet configured
   (mind, only their names)
   - "available_with_geom": same as above, bon only spatial ones
   - "all": returns all of them, configured or available (again, just names)

The FeatureTypeController delete mapping already has a "recurse" flag to
delete layers while the feature type is removed.
Now here there is a risk of confusion between "recurse" and "cascade", a
"removeData" flag would probably avoid confusion.

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] Deleting database table through REST API

[Andrea Aime]

lutions, for example PostgREST https://postgrest.org
>
> (not sure if that one lets you drop tables) but you get the idea.
>
>
>
> Cheers,
>
> Gabe
>
>
>
>
>
>
>
> On Mon, 12 Feb 2024 at 16:25, Jody Garnett  wrote:
>
> I am open to improvements and addition to the importer API (which offers
> some control as it is responsible for the automatic creation of tables; it
> has an opportunity to delete an existing table when replacing contents).
>
>
>
> See example
> https://docs.geoserver.org/latest/en/user/extensions/importer/rest_examples.html#replacing-postgis-table-using-the-contents-of-a-csv-file
>
>
>
>
>
> --
>
> Jody Garnett
>
>
>
>
>
> On Feb 12, 2024 at 1:30:11 AM, Cécile Vuilleumier <
> cecile.vuilleum...@camptocamp.com> wrote:
>
> Hi all
> When creating a feature type in a database datastore with the REST API,
> GeoServer will create the corresponding table if it does not exist.
> We were wondering if similarly the deletion of a table was also possible
> when deleting the associated feature type and I found this discussion:
> https://sourceforge.net/p/geoserver/mailman/message/36221224/
> Does anybody know if a proposal had been submitted? I couldn't find it on
> the GitHub wiki but I might have missed it.
> Many thanks, Cécile
>
> --
> *camp**to**camp*
>
> *Cécile Vuilleumier*
>
> Geospatial developer
> www.camptocamp.com
>
> ___
> 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 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
>
>
>
>
> --
>
> Gabriel Roldán
>
> ___
> 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 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  339 8844549

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

---

Con riferimento alla normativa s

Re: [Geoserver-users] Greetings

[Andrea Aime]

Hi Simon,
the Mosaic JDBC plugin was dropped years ago because we lacked a maintainer
for it.
The documentation is versioned, the current one should not contain
information about that plugin anymore:
https://docs.geoserver.org/latest/en/user/

If you find any outdated link, please use the "edit" button available in
the right side of the page:

[image: image.png]

It will open and editor, you can correct the link, saving will create
documentation Pull Request with the update

Best regards
Andrea


On Tue, Feb 13, 2024 at 2:29 AM Šimon Janovič  wrote:

> I'm a Slovak student,
>
> and I've been using Geoserver for a while and the newest stable version of
> it doesn't run on firefox allegedly due to recursive redirections or so it
> said. Geoserver 2.24.0 is the last version that worked on Firefox.
>
> Firefox is stricter about security than other browsers and I think it's a
> matter of time before other browsers up their security measures as well. So
> could you consider testing your webapp on Firefox, too? Thanks. I searched
> the usage of Firefox and due to the low percentage of usage I understand
> why you wouldn't really mind to test on Firefox.
>
> Is the Photo Mosaic JDBC plugin still up to date? Or is it canceled? Your
> documentation isn't very exhaustive and it contains plenty of outdated
> links that don't work anymore.
>
> I appreciate the time you spent reading this. I hope I helped. I'm going
> to downgrade back to the last version that worked for me.
>
> Have a nice day
>
>  -  Šimon Janovič
> ___
> 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  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] Deleting database table through REST API

[Andrea Aime]

Hi Cécile,
I don't see the feature being implemented in the code.

The wiki page you're looking for is this one:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-fixes,-improvements-and-new-features-in-GeoServer

Cheers
Andrea


On Mon, Feb 12, 2024 at 10:39 AM Cécile Vuilleumier <
cecile.vuilleum...@camptocamp.com> wrote:

> Hi all
> When creating a feature type in a database datastore with the REST API,
> GeoServer will create the corresponding table if it does not exist.
> We were wondering if similarly the deletion of a table was also possible
> when deleting the associated feature type and I found this discussion:
> https://sourceforge.net/p/geoserver/mailman/message/36221224/
> Does anybody know if a proposal had been submitted? I couldn't find it on
> the GitHub wiki but I might have missed it.
> Many thanks, Cécile
>
> --
> *camptocamp*
>
> *Cécile Vuilleumier *
> Geospatial developer
> www.camptocamp.com
> ___
> 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  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] Anyone interested in co-funding Geoparquet suppport in GeoServer?

[Andrea Aime]

Hi all,
at Geosolutions we are looking for partners that would be interested in
joining a group to co-fund support for GeoParquet in GeoServer. We
already have interested parties to cover some of the cost, but we need more
to support the full development.

If you are interested, could you contact me and Simone (cc'ed)?

Best regards
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] Time dimension - Exact Match Only option?

[Andrea Aime]

Hi Scott,
the nearest match is something that you have to enable explicitly, so it
won't be available if you don't enable it.
The default value is always there, but you can specify a value by hand that
does not match anything.
In recent versions of GeoServer, you can match that with having GeoServer
throw an InvalidDimensionException
when there is no match:
https://docs.geoserver.org/latest/en/user/services/wms/webadmin.html#dimensions-settings

That's for WMS. I don't remember what WCS does, off the top of my head, but
I'd guess it also throws an exception
(I'm hopeful for WCS 2.0, less so for 1.1 and 1.0)

Cheers
Andrea

On Fri, Feb 9, 2024 at 10:01 PM Scott Lewis  wrote:

> Hello again, I had another question regarding some of the work I've been
> doing recently.
>
> I have an ImageMosaic store with various layers, and I've enable the
> "Time" dimension for these layers.  Is it possible to force an "exact
> match" only for queries against these layers (particularly with WCS), and
> not have a default or "nearest match" value?  The reason is that because
> the time dimension information is not part of the resulting output TIF, the
> user would have no way of knowing if the data they requested actually
> matched the time they queried for, so I'd rather it return something to
> tell the user "there is no data for this time" than just return a default
> file.
>
> As always, thanks!
>
> Scott Lewis
> NSIDC
> ___
> 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  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] Run with jetty and extensions

[Andrea Aime]

Don't modify the pom.xml, just add "-Pnetcdf" to the command line instead:

mvn jetty:run -Pnetcdf

Cheers
Andrea


On Mon, Jan 29, 2024 at 2:35 PM Amirhossein Nikfal 
wrote:

> The problem can be solved by adding the gs-netcdf artifact to the list of
> dependencies in pom.xml.
>
> On Thu, Jan 25, 2024 at 5:14 PM mark  wrote:
>
>> Op 25-01-2024 om 11:35 schreef Amirhossein Nikfal:
>> > According to the documentation
>> > <
>> https://docs.geoserver.org/latest/en/developer/maven-guide/index.html#running-the-web-module-with-jetty>,
>> by the command "/mvn jetty:run/", the web module can be run. However, the
>> compiled extensions are not available in this case.
>>
>> perhaps adding the profile that activates building the extension helps?
>> ( I haven't tried)
>>
>> -M
>>
>>
>>
>> ___
>> 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 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  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] [Geoserver-devel] 2024 roadmap blog post

[Andrea Aime]

Hi Roar,
thanks a lot for the offer!

Currently, we have no idea as to when the Jakarta EE rewrite will take
place, we'll first have to perform a number
of upgrades before that happens. It's however very likely that we'll have
to do a large-ish code sprint around that
topic, as we'll have to switch, in a single shot, Wicket 10, Spring 6
(along with Spring security), Jetty 12, and indeed
move everything to Jakarta EE. As a result, some planning will happen once
the earlier items are done (phase I and II):
https://github.com/geoserver/geoserver/wiki/Jakarta-EE

Cheers
Andrea

On Fri, Jan 12, 2024 at 7:49 AM Roar Brænden 
wrote:

> Hello,
>
> Happy new year!
>
> I've seen the post and road map and if all that will come through during
> the year. I would say that 2024 is a very good year.
> I would very much be a part of that effort. The one header that seems most
> appropriate for me to be a part of, is the Jakarta EE rewriting.
>
> Looking forward to see what's the future of GeoServer.
>
> Best wishes,
>
> Roar Brænden
>
>
> 11. jan. 2024 kl. 08:37 skrev Peter Smythe :
>
> Good day GeoServer users
>
> Happy new year and welcome to 2024 from the GeoServer team!
>
> I wonder how many of you keep an eye on the GeoServer blog
> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/5vI33yXCEQG-g5DW9p6Ja0mejWetE5S1Rb0JE5ERkmhLGCgBtoWzBqsBMWASiICbhDxKFH3P3-faLZQfyqCMUUemLnooOZ5CM1Z7t4Zbv_sedSLCMTCaCRKqMaZTrDr88gcevt8_A6ZmFwHwefJX6MicUPS__n7ZDYtbV5X4BIMWTG6C5c9uvoW4gKd6NKaDhKIqv2Dlg79TNiZPPJ8ubE_TRF7507BGSm14c7XGkKu0x_pLzIw5vW79Wd-CEWGaPxEYTrQbo4913mvKPJnFTIR_U3aOHeT6kOMS-Q>?
>
>
> This year the Project Steering Committee has put a lot of effort into
> documenting the plans for 2024 as there are a lot of technology upgrades
> that must be made: spring-framework 6, spring-security 6, wicket 10,
> JakartaEE, Java 17, ImageN, the list is very long ...
>
> Please take  a few minutes to read Jody's detailed post, so that you know
> what help we need:
> https://geoserver.org/behind%20the%20scenes/2024/01/03/roadmap.html
> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/sVufbZpqTeh2ZhV0W9yNAUfXUIRxfLuSF45PHDegOQ3dlcLSZQTnaQ6NnbtWfLvyl2SuhwN0tn4exCVkQzLdHUZ2AWuhV6WY2JOgP5NsLu0prnkSKfyYniBUmEvbhD0Du7bvwM2Yp9xAPQeu6gevC8KKYj28CrUpupR-keHuWnimBDlDdDqU6EQXKZTccLqU_tA8CSVkDLerHiM-R-GnOlwEOJLO1Ohfi6wWIDYPDxZRS8i8MWRYljq1sTsQDmhKopGd0S7qcf8Illta4XceOmxb9NZj5LgwWnDpsOHU5F-BOHRacfV5dkTGMuIuTeknYbHVg4rBBlthH0Ibn36hyojNFJhzltVE2_66V_00>
>
> If you're not a developer, don't worry! We need testers - users like you
> who are familiar with GeoServer's GUI and functionality. We would love you
> to reply to this email with an offer to help.
>
> Oh, and we're fund raising too - please read that section too, and make a
> request to your company's finance department.
>
> Here's to an extra successful GeoServer community in 2024!
>
> Peter
> ___
> Geoserver-devel mailing list
> geoserver-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
> _______
> Geoserver-devel mailing list
> geoserver-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


-- 

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

Re: [Geoserver-users] Issues with GWC and Google Global Mercator (900913) after adding custom SRS

[Andrea Aime]

 projection issue? Have we defined this incorrectly?
> Is anyone successfully using both 9437 and 900913 with GWC?
>
> This is the first custom SRS we've defined so I'm not sure whether the
> same disappearing Google Mercator issue would occur with an alternate SRS.
>
> We're running Geoserver version 2.24.0
>
> Thanks in advance for your help, this one has me stumped!
>
>
>
> This email is confidential, and is for the intended recipient only.
> Access, disclosure, copying, distribution, or reliance on any of it by
> anyone outside the intended recipient organisation is prohibited and may be
> a criminal offence. Please delete if obtained in error and email
> confirmation to the sender. The views expressed in this email are not
> necessarily the views of the University of Tasmania, unless clearly
> intended otherwise.
> ___
> 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  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] -EXT- Conversion meters to kilometers or feet in DWithin filtering

[Andrea Aime]

Hi,
yes, having it would be useful. Thinking out loud, it should then be used
in ContentFeatureSource to pre-process filters
for stores that can't implement their own native unit conversions, maybe
with a "canConvertUnits" method similar to the
already existing ones, "canFilter", "canSort", "canLimit" and so on

Cheers
Andrea

On Fri, Dec 15, 2023 at 4:37 PM Lahr-Vivaz, Emilio <
emilio.lahr-vi...@ga-ccri.com> wrote:

> Ah, good to know. We've actually implemented this in GeoMesa[1], using the
> Geodetic calculator (so it also works in GeoMesa stores, in addition to
> Postgis and Oracle). Is that something people would be interested in
> porting over to GeoTools/GeoServer? There's an optimized check for very
> close and far points that probably only works with EPSG:4326, but maybe
> could be generalized some (or removed). I'd be happy to rewrite it in Java
> if it's useful.
>
> Thanks,
>
> Emilio
>
> [1]:
> https://github.com/locationtech/geomesa/blob/main/geomesa-filter/src/main/scala/org/locationtech/geomesa/filter/expression/FastDWithin.scala
> --
> *From:* Andrea Aime 
> *Sent:* Friday, December 15, 2023 9:52 AM
> *To:* Lahr-Vivaz, Emilio 
> *Cc:* geoserver-users@lists.sourceforge.net <
> geoserver-users@lists.sourceforge.net>
> *Subject:* Re: [Geoserver-users] -EXT- Conversion meters to kilometers or
> feet in DWithin filtering
>
>
> WARNING:  This message is from an external source.  Evaluate the message
> carefully BEFORE clicking on links or opening attachments.
> Hi Emilio,
> almost correct, the unit conversion is implemented only in selected data
> stores, e.g. posgis and oracle,
> while all other stores are unable to deal with differences in units.
> The same goes for distances in km with units in degrees, that works I
> believe only with postgis when using
> the geography data type.
>
> It's been like that for the past 20 years... nobody steps up to do it.
> It's too large of a task to perform in spare time,
> and those that may sponsor are typically using postgis and oracle already.
>
> Cheers
> Andrea
>
> On Fri, Dec 15, 2023 at 3:17 PM Lahr-Vivaz, Emilio <
> emilio.lahr-vi...@ga-ccri.com> wrote:
>
> I believe that dwithin ignores the units, and will always evaluate the
> distance in the units of the layer's CRS, e.g. for EPSG:4326 it uses
> degrees.
>
> Thanks,
>
> Emilio
> --
> *From:* geospatial techno 
> *Sent:* Friday, December 15, 2023 8:11 AM
> *To:* geoserver-users@lists.sourceforge.net <
> geoserver-users@lists.sourceforge.net>
> *Subject:* -EXT-[Geoserver-users] Conversion meters to kilometers or feet
> in DWithin filtering
>
>
> WARNING:  This message is from an external source.  Evaluate the message
> carefully BEFORE clicking on links or opening attachments.
> I have used the WMS service with the CQL filter in GeoServer. Currently, I
> want to use the "DWithin" spatial operators to filter features by default
> GeoServer data ("sf:archsites" layer). I specifically need to filter a
> specific point (593250, 4923867) using a radius of 10,000 meters.
> I want to substitute meters with something like kilometers.
>
> The issue is that these two commands should produce the same results in
> the output, however in geoserver, it doesn't work this way. Why?
>
> Here are the CQL filter codes:
> - CQL_FILTER=DWithin(the_geom,Point(593250 4923867),1,meters)
> - CQL_FILTER=DWithin(the_geom,Point(593250 4923867),10,kilometers)
>
> Regards
> ___
> 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  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolut

Re: [Geoserver-users] -EXT- Conversion meters to kilometers or feet in DWithin filtering

[Andrea Aime]

Hi Emilio,
almost correct, the unit conversion is implemented only in selected data
stores, e.g. posgis and oracle,
while all other stores are unable to deal with differences in units.
The same goes for distances in km with units in degrees, that works I
believe only with postgis when using
the geography data type.

It's been like that for the past 20 years... nobody steps up to do it. It's
too large of a task to perform in spare time,
and those that may sponsor are typically using postgis and oracle already.

Cheers
Andrea

On Fri, Dec 15, 2023 at 3:17 PM Lahr-Vivaz, Emilio <
emilio.lahr-vi...@ga-ccri.com> wrote:

> I believe that dwithin ignores the units, and will always evaluate the
> distance in the units of the layer's CRS, e.g. for EPSG:4326 it uses
> degrees.
>
> Thanks,
>
> Emilio
> --
> *From:* geospatial techno 
> *Sent:* Friday, December 15, 2023 8:11 AM
> *To:* geoserver-users@lists.sourceforge.net <
> geoserver-users@lists.sourceforge.net>
> *Subject:* -EXT-[Geoserver-users] Conversion meters to kilometers or feet
> in DWithin filtering
>
>
> WARNING:  This message is from an external source.  Evaluate the message
> carefully BEFORE clicking on links or opening attachments.
> I have used the WMS service with the CQL filter in GeoServer. Currently, I
> want to use the "DWithin" spatial operators to filter features by default
> GeoServer data ("sf:archsites" layer). I specifically need to filter a
> specific point (593250, 4923867) using a radius of 10,000 meters.
> I want to substitute meters with something like kilometers.
>
> The issue is that these two commands should produce the same results in
> the output, however in geoserver, it doesn't work this way. Why?
>
> Here are the CQL filter codes:
> - CQL_FILTER=DWithin(the_geom,Point(593250 4923867),1,meters)
> - CQL_FILTER=DWithin(the_geom,Point(593250 4923867),10,kilometers)
>
> Regards
> ___
> 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  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] R: ReprojectGeometry WPS problem from 2.22.0 GeoServer version using application/json input

[Andrea Aime]

On Mon, Nov 6, 2023 at 3:25 PM Daniele Maggiolo via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> HI,
>
> will this bug be fixed in future versions of GeoServer?
>

My guess is that yes, it will. But if you want to control "when", then see
this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-fixes,-improvements-and-new-features-in-GeoServer

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] Change log level configuration for geowebcache

[Andrea Aime]

Hi Alexandre,
it should be a matter of creating a new logging configuration file by copy
of an existing one,
name it "GEOWEBCACHE_DEBUG.xml", and then tweak the packages at high
logging level to be the GWC ones.

Cheers
Andrea

On Sat, Nov 11, 2023 at 12:08 PM Alexandre Gacon 
wrote:

> Hello,
>
> Is it possible to change the log level configuration for the geowebcache
> embedded with geoserver?
>
> I have configured an external wms layer into geowebcache with the REST API
> and I have errors when I try to get tiles.
>
> The layer:
> 
> 
> true
> true
> test_ign
> 
> image/png
> image/jpeg
> 
> 
> 
> EPSG:4326
> 
> 
> EPSG:900913
> 
> 
> 
> 4
> 4
> 
> 0
> 0
> 
> 0
> 
> 
> https://data.geopf.fr/wms-r/wms?SERVICE=WMS
> 
> ORTHOIMAGERY.ORTHOPHOTOS
> 
>
> The error stack
> 10 Nov 14:29:39 ERROR  [geowebcache.GeoWebCacheDispatcher] - All backends
> (1) failed. Reason: Unexpected response code from backend: 400 for
> https://data.geopf.fr/wms-r/wms?SERVICE=WMS.  Last request: '
> https://data.geopf.fr/wms-r/wms?SERVICE=WMS'.
> http://localhost:8080/geoserver/gwc/service/wmts
> 10 Nov 14:29:39 ERROR  [geowebcache.GeoWebCacheDispatcher] - Request failed
> org.geowebcache.GeoWebCacheException: All backends (1) failed. Reason:
> Unexpected response code from backend: 400 for
> https://data.geopf.fr/wms-r/wms?SERVICE=WMS.  Last request: '
> https://data.geopf.fr/wms-r/wms?SERVICE=WMS'.
> at
> org.geowebcache.layer.wms.WMSHttpHelper.makeRequest(WMSHttpHelper.java:154)
>
> I woud like to know which request is sent
>
> --
> Alexandre Gacon
> ___
> 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  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] Group raster values in SLD

[Andrea Aime]

Hi,
I'm working on a new vendor option that will land soon on the GeoServer
developer series,
which will allow exactly that sort of duplicate removal.

In the meantime, you can probably fake it by having two rules, one intended
for rendering (using a vendor option named inclusion=mapOnly)
and a separate one only for the legend (inclusion)legendOnly). See more on
this topic here:

https://docs.geoserver.org/stable/en/user/styling/sld/extensions/rendering-selection.html

Cheers
Andrea



On Wed, Oct 18, 2023 at 2:14 PM Briones Garcia, Pedro  wrote:

> Hi all.
>
>
>
> I have an SLD file (attached file *file1.sld*) for drawing an image
> mosaic layer. There are nine raster pixel values that are represented with
> same symbol (color="#288228"). The resulting legend is attached
> *Leyend1.png* file.
>
>
>
> I would like to have only one category in the legend for all pixels with
> the same symbol as attached file leyend2.png shows, so I need to group all
> pixels values in one category.
>
>
>
> Any Idea how to do it with SLD without editing the source images?
>
>
>
> Thanks in advance
>
> [image:
> http://www.tragsa.es/SiteCollectionImages/Relaciones%20Institucionales%20(Prensa)/FIRMA%20OUTLOOK/2023tragsatec.png]
>
> *Briones Garcia, Pedro *
> JGAP Sist Inform Geográfica
> S.Información Geográfica / G.Sist.Inf. Geografica
>
> Grupo Tragsa - SEPI
>
>
>
> Calle Julián Camarillo 6B - 28037 Madrid
> Tel.: 913226489 - 88216 - Fax: 913226005
> p...@tragsa.es
> *www.tragsa.es * <https://www.tragsa.es/>
>
>
>
>
> *AVISO LEGAL * <https://www.tragsa.es/es/Paginas/aviso-legal-correo.aspx>
>
>
> *POLITICA DE PRIVACIDAD, de conformidad con el Reglamento UE 2016/679 y la
> Ley Orgánica 3/2018 *
> <https://www.tragsa.es/es/Paginas/politica-privacidad-correo.aspx>
>
>
> ___
> 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  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

[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=1.0.0=image/png=mylayer_options=countMatched:true=EPSG:4326=769=496=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=GetMap=image%2Fpng=true=mylayer=application%2Fvnd.ogc.se_inimage=EPSG%3A4326=769=496=44.042435837063046%2C15.364493754777163%2C44.04309992763117%2C15.365523966875822
>>> <http://geoserver.local/geoserver/myworkspace/wms?SERVICE=WMS=1.3.0=GetMap=image%2Fpng=true=mylayer=application%2Fvnd.ogc.se_inimage=EPSG%3A4326=769=496=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=1.0.0=image/png=mylayer_options=countMatched:true=EPSG%3A4326&=796=496=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 onl

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

[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=GetMap=image%2Fpng=true=mylayer=application%2Fvnd.ogc.se_inimage=EPSG%3A4326=769=496=44.042435837063046%2C15.364493754777163%2C44.04309992763117%2C15.365523966875822
> <http://geoserver.local/geoserver/myworkspace/wms?SERVICE=WMS=1.3.0=GetMap=image%2Fpng=true=mylayer=application%2Fvnd.ogc.se_inimage=EPSG%3A4326=769=496=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=1.0.0=image/png=mylayer_options=countMatched:true=EPSG%3A4326&=796=496=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] Anybody working on OGC API Features datastore?

[Andrea Aime]

If you need it now, there is the ogr datastore community module
<https://docs.geoserver.org/stable/en/user/community/ogr-store/index.html>.
It supports any OGR format,
so you should be able to use the OGC API Features reader

Cheers
Andrea

On Mon, Oct 2, 2023 at 3:53 PM Rahkonen Jukka <
jukka.rahko...@maanmittauslaitos.fi> wrote:

> Hi,
>
>
>
> In a couple of years old blog post
> http://geotoolsnews.blogspot.com/2020/09/ there is a wish for potential
> developers:
> “We invite developers to contribute to the following work-in-progress:
>
>- A new DataStore to access ogc-api features
>
> Has anybody started to develop that datastore?
>
>
>
> -Jukka Rahkonen-
> ___
> 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  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] [Externo] GetLegendGraphic issue working with layer group style.

[Andrea Aime]

gt;> proceden de TRACASA INSTRUMENTAL, S.L. y se dirige exclusivamente a su
>> destinatario, puede contener información privada o confidencial amparada
>> por el secreto de empresa, y a la que sólo tiene el derecho de acceder el
>> destinatario. Si no es Vd. el destinatario indicado, o la persona
>> responsable de su entrega al mismo, deberá abstenerse de examinar su
>> contenido y queda notificado de que la utilización, divulgación y/o copia
>> sin autorización está prohibida en virtud de la legislación vigente. Si ha
>> recibido este mensaje por error, le rogamos que nos lo comunique
>> inmediatamente mediante correo electrónico a esta misma dirección, y
>> proceda a su destrucción segura. TRACASA INSTRUMENTAL, S.L. es el
>> responsable de tratamiento de los datos de carácter personal facilitados
>> que se utilizarán con la finalidad de mantener comunicaciones con usted.
>> Tiene la posibilidad de ejercitar los derechos de acceso, rectificación,
>> limitación del tratamiento, supresión y portabilidad, mediante solicitud
>> dirigida por escrito, acreditando su identidad a la dirección electrónica
>> d...@itracasa.es. Puede consultar información adicional y detallada sobre
>> nuestra política de protección de datos de nuestra web www.itracasa.es.
>> ___
>> 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 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  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] GeoServer 2.24-RC released. Please help us test it

[Andrea Aime]

In the meantime... fixed: https://osgeo-org.atlassian.net/browse/GEOT-7465

Cheers
Andrea

On Fri, Sep 29, 2023 at 4:11 PM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> Interesting, might be a side effect of the removal of the EPSG assumption
> (to allow IAU CRSs to be used).
> Can you open a Jira ticket?
>
> Cheers
> Andrea
>
>
>
> On Wed, Sep 27, 2023 at 9:10 AM Georg Weickelt <
> georg.weick...@ibedelmann.de> wrote:
>
>> Hi,
>>
>> I installed the RC, everything seems to work fine, however I get a lot of
>> warnings in the log:
>>
>> 27 Sep. 08:59:09 WARN   [wms.capabilities] - Unable to decode CRS:84
>> org.geotools.api.referencing.NoSuchAuthorityCodeException: Authority "WEB
>> MAP SERVICE CRS" is unknown or doesnt match the supplied hints. Maybe it is
>> defined in an unreachable JAR file?
>>
>> The data is in Postgis, EPSG 25833 and is also queried by the client QGIS
>> in the same coordinate system.
>>
>> Best Regards
>>
>> Georg
>>
>> --
>> ibe Ingenieurbüro Edelmann Ingenieurgesellschaft mbH,
>> An der Wiedemuth 12, 02708 Löbau
>> Telefon (03585) 4789-0, Telefax (03585) 4789-49
>> Geschäftsführer: Dipl.-Ing. Frank Edelmann
>> Amtsgericht Dresden HRB 5676
>> StNr.: 208/111/02602
>> Sie haben das Recht im Fall von Art. 21 Absatz 1 und 2 DSGVO der 
>> Datenverarbeitung zu widersprechen.www.ibedelmann.de
>>
>> Am 26.09.2023 um 16:36 schrieb Andrea Aime:
>>
>> Hi all,
>> the GeoServer 2.24 Release Candidate is out, you can read about the news
>> here:
>>
>> https://geoserver.org/announcements/2023/09/25/geoserver-2-24-RC-released.html
>>
>> Please help up test it so that we have a solid 2.24.0 release
>>
>> Best Regards
>> 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.nethttps://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>> ___
>> 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

Re: [Geoserver-users] GeoServer 2.24-RC released. Please help us test it

[Andrea Aime]

If I remember correctly, we have had some issue with the docker release
script
not handling RC correctly? Like, it's not doing the right thing when it
sees "2.24-RC" in the version
and ended up tagging it as part of 2.24.x instead (which I assume has been
overwritten by a proper
nightly build by now).

Jody was mentioning it in the last PSC call, I believe the script is this
one:
https://github.com/geoserver/docker/blob/master/build/release.sh

Cheers
Andrea

On Fri, Sep 29, 2023 at 12:22 PM Peter Smythe  wrote:

> Is there perhaps a docker image of 2.24-RC available as a standard
> offering, or must that be set up manually?
>
> I see that a year ago, Jody followed up the announcement with:
>
> If you like docker please try:
>>
>> docker pull docker.osgeo.org/geoserver:2.22-RC
>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/k3NFsP2O5WcYZvetAuAOm1pwXn9RJVcnyMhcFSTzDIkWxPea6og_foY_AA5YSzj4YYq5e848SM8LnSswQpC4Miauq4IRf81n1zzGi74tdrfROpt5Dp-fsWfTNyCcgbb45Sbi_qU9RLQCv1e3xriTDTO7CTqzygNEcua2VAw8kop3rve3xNpLXynw0jiw3vABOXPH7TtwgIEWZW00Hz_rUIKFK2b48pWfmN6Y57dyfHyyCAp5XQ4xmkUy4jDs1w>
>> docker run -it -p 80:8080 docker.osgeo.org/geoserver:2.22-RC
>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/e9rJwa_OKfKRi4Kv-GlQ6J87zPjXSliZXtCiTqv7cGxvDTmOS4BCH9c19EJphG-dAh2wOcKOZWSbVaUDVDBJ0kr3DpQySA8X5Fi2wKCd8sT5kzAciG-KhqS1lQH5UoT_rUhrZ0H6T2iC_2LSaGFx8s3mIBdT0L6BszKbpJXt6_Zp9C_bmYMKQ6lmVoZww3DwMwbALZZ6MzotkdOlmHaXWX9q6JZQl0p6nqcIMTkeH66-b9DRAvJkasjvuzK1QQ>
>>
>>
> And
> https://docker.osgeo.org/#browse/search/docker=format%3Ddocker%20AND%20attributes.docker.imageName%3Dgeoserver%20AND%20version%3D*RC*
> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/wk7VIyflecIK0lY1SDqYP0xj41Rk8G-U2kgGG8dRfiLuAzo08ffShA5zBpYhKCTPbQLazjEx8yZDRGv9EdAveJoDLSsEkSqmxuaAl5zeyf1BOBtZhUAuiZWMLLJKE0L4Ge5C9GX2r8Ba2QHPt0lhp2SA1FmTdeCb7GDhrypNMRlBd9ODkE243HLl2W0FKT3eZj40a_lPeS1Z2T77zmB_9YDJ6HloYG6v6LirYQA3y0pu0YnA1BpNCI9dzIg9expiCftYgcebr408HeMO8CgKn-kKfWEf1OEFNcgQXQz4wT5bK_mhQ-d_RpA0PEJNCMAx2YdJy8gPHud_DOblmBVEpO3Vxwm6yQ9n0uTzLlk9p04zC-sRT4Y5CWRiqYg9zu8CjokiG6KkMLJ8W6MZOwc>
> shows both 2.22 and 2.23 release candidates, but not 2.24-RC
>
> We would like to assist with the RC testing, if it is available.
>
> Peter
>
> On Tue, 26 Sept 2023 at 16:43, Andrea Aime <
> andrea.a...@geosolutionsgroup.com> wrote:
>
>> Hi all,
>> the GeoServer 2.24 Release Candidate is out, you can read about the news
>> here:
>>
>> https://geoserver.org/announcements/2023/09/25/geoserver-2-24-RC-released.html
>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/XWGQi_JGR9SEH-iuw4idNU5gEzH1C2GpJcqql-DThrpgRnvMIVZrU8q3peYce5AKVolcxy3XNeYG5lDSQ3qhrla4FqtcZT6lyt_SEIU2ZxTwX2p1xvaVNGwzwTySWxAdYOT6mVEZVFzsQeSX_3GBkTXEg5CLAVLzDcLgL-pVsJ58BSgPQ25Xj1k4v_9Af0EYyuXpp0VU7jFvAdlvAOG41S0hrWHBWBp7MjaeczvqW0lW_mBa2exJk6K2kR9GfjiYG7s9k6aUxwHhmwF8QiUGSHLc8Fy_XjOEvzTZ9_l3BGBsQ_Fm3M7-oYs>
>>
>> Please help up test it so that we have a solid 2.24.0 release
>>
>> Best Regards
>> Andrea
>>
>>
>> ==
>> GeoServer Professional Services from the experts!
>>
>> Visit http://bit.ly/gs-services-us
>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/oF82q3ZtqfgIwlEWarO4m2y6iJ7cYi-Su6DaCTrhNXV_Gd2ICS4Lyf6IILZKvTzLkk1woL92ydZzk7rL8k61lCXLSAdfLYVecIX6-4lM7lctf__teudx7MogceIVAPIcetyWXHW_x-_eURbXVeLKNyZrH1hKuFWyYIkd0mxL5dK3hA_8bY-3VNudGWEQ4ZzhxWBmxwM5GgXCEfmhRb379TPAEI-G60f3C9qQhAWLMA>
>> 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/
>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/IsV-LdGyY1JA1wXxKCq-LJYQl08swn5An3YUg3jrb2LForXFMwDQEapegVhHyRdB_ZqVmEqMPEJt72DziN-WG2rEtXorE_wUxiAI-Wy3DkMDfRA6dfpupJHdBULRX-lzOnRR2OK8_pHRozV3yayp1Yz5SuC_1Ggk2VLc-dhh-VhipUyeZj4Xdf_8y5r2Dcsvt_Z2CMexf4Zqu5af0GOSf0iq1ceekoqgp6mF5GmTSut16u_DqQ>
>>
>> http://twitter.com/geosolutions_it
>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/mjDlvgj5CyOOVycGiDld1drYctJ1SW2yCTG3xOAjZW0pborMaO7cakE9SlUHwHcAhf99qJypzM9lgxsdaLLxDOjYBC7YXrzzcxmF_f6RjJhF9XiH2vGKEzOCmFGhKNRaepwBl0j2uc1bHbMXiJTDUgZlsJVylLn2YhWA1YPa8yImBOXFKUwBTqESZWkLToNzWdxr1ve3dGFtD8GPyBzlQO9y6hmbX7aLcBYJiHTAfeUt9mIxsw>
>>
>> ---
>>
>> 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 destinata

Re: [Geoserver-users] GeoServer 2.24-RC released. Please help us test it

[Andrea Aime]

Interesting, might be a side effect of the removal of the EPSG assumption
(to allow IAU CRSs to be used).
Can you open a Jira ticket?

Cheers
Andrea



On Wed, Sep 27, 2023 at 9:10 AM Georg Weickelt 
wrote:

> Hi,
>
> I installed the RC, everything seems to work fine, however I get a lot of
> warnings in the log:
>
> 27 Sep. 08:59:09 WARN   [wms.capabilities] - Unable to decode CRS:84
> org.geotools.api.referencing.NoSuchAuthorityCodeException: Authority "WEB
> MAP SERVICE CRS" is unknown or doesnt match the supplied hints. Maybe it is
> defined in an unreachable JAR file?
>
> The data is in Postgis, EPSG 25833 and is also queried by the client QGIS
> in the same coordinate system.
>
> Best Regards
>
> Georg
>
> --
> ibe Ingenieurbüro Edelmann Ingenieurgesellschaft mbH,
> An der Wiedemuth 12, 02708 Löbau
> Telefon (03585) 4789-0, Telefax (03585) 4789-49
> Geschäftsführer: Dipl.-Ing. Frank Edelmann
> Amtsgericht Dresden HRB 5676
> StNr.: 208/111/02602
> Sie haben das Recht im Fall von Art. 21 Absatz 1 und 2 DSGVO der 
> Datenverarbeitung zu widersprechen.www.ibedelmann.de
>
> Am 26.09.2023 um 16:36 schrieb Andrea Aime:
>
> Hi all,
> the GeoServer 2.24 Release Candidate is out, you can read about the news
> here:
>
> https://geoserver.org/announcements/2023/09/25/geoserver-2-24-RC-released.html
>
> Please help up test it so that we have a solid 2.24.0 release
>
> Best Regards
> 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.nethttps://lists.sourceforge.net/lists/listinfo/geoserver-users
>
> ___
> 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  339 8844549

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

---

Con riferimento alla no

[Geoserver-users] GeoServer 2.24-RC released. Please help us test it

[Andrea Aime]

Hi all,
the GeoServer 2.24 Release Candidate is out, you can read about the news
here:
https://geoserver.org/announcements/2023/09/25/geoserver-2-24-RC-released.html

Please help up test it so that we have a solid 2.24.0 release

Best Regards
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] -EXT- Trouble getting SLD property function to work with namespaced properties

[Andrea Aime]

Read the full message, the answer does not change though, see my other
reply 

Cheers
Andrea


On Mon, Sep 25, 2023 at 10:33 PM Reffett, Christopher <
christopher.reff...@ga-ccri.com> wrote:

> Sorry folks, accidentally hit send on that too early. Here's the message I
> wanted to send:
>
> Hello all,
>
> I'm trying to make an SLD where a user can change the label field at
> runtime, but I'm running into problems getting the "property" function to
> work as expected with my data source. The source is producing complex
> features, and they show up in geoserver as namespaced. If I prefix a
> property with the namespace in , everything works as
> expected, but when I try to use , I hit errors.
>
> A snippet like this works fine:
> 
>   namespace:myFeature
> 
>
> This fails with "The style specified an attribute named
> 'namespace:myFeature', not found in the 'namespace:layer' layer" (and
> similarly fails if I pass in a valid namespace-prefixed property name in
> the request):
> 
>   
> 
>   userDefinedLabel
>   namespace:myFeature
> 
>   
> 
>
> I've tried a few different variations on the above (for example, removing
> prefixes or adding the full URL of the prefix) without success. The latter
> recipe also worked fine on a simple feature with no namespace, it's just
> the complex feature with the namespace that caused things to break. I've
> been digging through Google all day but have not found anything applicable
> to this scenario. I'd appreciate any suggestions that you all have on what
> I might be doing wrong here.
>
> I am using GeoServer 2.17.3 with OpenJDK 1.8.0_272 Server running in a
> Linux container. I know, they're old - unfortunately upgrades to newer
> versions are not a priority right now.
>
> Best,
> Chris Reffett
> --
> *From:* Reffett, Christopher 
> *Sent:* Monday, September 25, 2023 4:10 PM
> *To:* geoserver-users@lists.sourceforge.net <
> geoserver-users@lists.sourceforge.net>
> *Subject:* -EXT-[Geoserver-users] Trouble getting SLD property function
> to work with namespaced properties
>
>
> WARNING:  This message is from an external source.  Evaluate the message
> carefully BEFORE clicking on links or opening attachments.
> Hello all,
>
> I'm trying to write an SLD but am having trouble getting the "property"
> function to work as expected. In short, I have a layer that has namespaced
> fields (it's coming from a data source that produces complex features) and
> am trying to make the label on those features able to be set by an env
> variable in a request.
> This wor
>
> I am using geoserver 2.17.3 - sorry, I know it's out of date, it'll be
> some time before we can update.
> ___
> 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  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 b

Re: [Geoserver-users] Trouble getting SLD property function to work with namespaced properties

[Andrea Aime]

Hi Christopher,
that GeoServer is a security liability, I advise to replace it as soon as
possible.

That said, the property function cannot work against complex features with
namespaced properties, as it does not have a namespace
context to work against. Off the top of my head, I would not know how to
pass one into it, but with some research and code
changes, it may be possible in the end (TBD). Like, maybe one could pass
the namespace of a single property as a new function
argument, but if the path traverses properties in different namespaces,
then a map from prefix to URI would be needed.

Cheers
Andrea


On Mon, Sep 25, 2023 at 10:27 PM Reffett, Christopher <
christopher.reff...@ga-ccri.com> wrote:

> Hello all,
>
> I'm trying to write an SLD but am having trouble getting the "property"
> function to work as expected. In short, I have a layer that has namespaced
> fields (it's coming from a data source that produces complex features) and
> am trying to make the label on those features able to be set by an env
> variable in a request.
> This wor
>
> I am using geoserver 2.17.3 - sorry, I know it's out of date, it'll be
> some time before we can update.
> ___
> 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  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] HTTPS to GeoServer Docker

[Andrea Aime]

In my experience HTTPS is managed in a proxy in front of GeoServer, which
can be set up
using a docker-compose with the proxy being another docker image.

Here is an example of a compose with a proxy from the GeoSolutions docker
image repository:
https://github.com/geosolutions-it/docker-geoserver/blob/master/docker-compose.yml

Slap on top of it an example of how to set up SSL certificates for nginx (a
much more command find) and you're in business.
E.g. first link returned by a Google search:
https://faun.pub/setting-up-ssl-certificates-for-nginx-in-docker-environ-e7eec5ebb418?gi=ca3c5d6589f0

Cheers
Andrea




On Tue, Sep 19, 2023 at 8:57 PM Adam Cooper 
wrote:

> I am exploring options for a relatively low-usage service requiring low
> levels of infrastructure setup and maintenance (the data is related to a
> local history society).
>
> GeoServer docker image appears to be perfect except that I observe it
> serves unencrypted data. This is not acceptable in 2023 on the grounds
> of security and privacy. I have not been able to find how to start the
> container such that HTTPS is the exclusive means of access.
>
> Is this possible? (I think it really should be!)
>
> Thanks in advance, Adam
>
>
>
>
> ___
> 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  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] Monitor extension throws AccessDeniedException

[Andrea Aime]

I haven't witness it happen, but as far as I can see, the security system
is refusing access to the
layer because the current request does not contain any more the context of
the original WMS request:
it's not seen as a WMS request anymore, because it's happening after the
request is done, in a
post processing task (a different thread).

I guess one could use ThreadLocalTransfer to transfer over the context of
the original request into the
background thread, there are examples of that in the codebase (e..g, in the
WPS module, which uses
background threads for everything).

Cheers
Andrea


On Wed, Sep 20, 2023 at 12:50 PM Peter Smythe  wrote:

> Hi all
>
> The Monitor extension
> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/tX6qrfylNQ_VzgtK-9vu7h9msUEDhclz9VN8YgKVbEFrjHQXPsi1c4rM7Me-kxR_QAZsaw6zOI5sylbPqKpmLsQH2GzePSpXpwcKyaSGusoecmAvS8QpcxsfMjHLtXLIihB3HKdw9tq1ooPRhVz7wK8uJOSEEPXih2osZJW58xgbrJ9F-CMvcZVonp47EaKfWQ4KSQ0x2isIwoPsSuQCCaPnwyeajLNRhfUgH4wyBzTPo6aoG-gGaVx3x_lFmiOZjxsmdYM0CsFMW-aPzELyncKpI-kjB6KkIO0Odp1RpUD72DSn1g>
> is populating the GeoServer logs (PRODUCTION_LOGGING) with these error
> messages, yet the (very standard) GetMap requests are being executed
> correctly, without any errors, returning images with status code 200.  The 
> AuthKey
> module
> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/wKvNyqyiFKGYuYfijXahQ6pd9HIk4nNylrV4ISVzMxnAMFW3l3Z0eZzeO9JKVUvplx8RFyqmwnKO_khgGt40Udn29ChIccOO6QpMh61OeFQo7Q4Qm5MWeswi6mOGDAY92LKZkFRwYlFZvKE0rN1u_XgDcBt3XrkrqLKBQKxEW0J_FtWgQRrEwyULDTXj9c9D4fukPwztRTaNsbGKzbslys1CdYBgy-oIqk_OrFYn1SNHNUNNd20t4ZKl3tFnOUzpr_QIWM6u0b90YgsWydZyrl2OdEbOjPKGeNqSmom3otJPnA>
> is used, same as any other layer/workspace.  Is this possibly a bug in the
> monitor extension, or a misconfiguration on our side?  I believe the
> configuration is standard:
>
> $ cat monitor.properties
> storage=memory
> mode=history
> sync=async
> maxBodySize=1024
> bboxLogCrs=EPSG:4326
> bboxLogLevel=no_wfs
>
> Is there any way to fix the problem or to configure it not to throw these
> exceptions?
>
> Thanks
>
> Peter
>
> 20 Sep 09:46:45 WARN   [geoserver.monitor] - Post process task failed
> org.springframework.security.access.AccessDeniedException: Cannot access
> __ with the current privileges
> at
> org.geoserver.security.SecureCatalogImpl.unauthorizedAccess(SecureCatalogImpl.java:1072)
> at
> org.geoserver.security.SecureCatalogImpl.buildWrapperPolicy(SecureCatalogImpl.java:1046)
> at
> org.geoserver.security.SecureCatalogImpl.buildWrapperPolicy(SecureCatalogImpl.java:925)
> at
> org.geoserver.security.SecureCatalogImpl.checkAccess(SecureCatalogImpl.java:715)
> at
> org.geoserver.security.SecureCatalogImpl.checkAccess(SecureCatalogImpl.java:603)
> at
> org.geoserver.security.SecureCatalogImpl.getLayerByName(SecureCatalogImpl.java:361)
> at
> org.geoserver.catalog.impl.AbstractFilteredCatalog.getLayerByName(AbstractFilteredCatalog.java:265)
> at
> org.geoserver.catalog.impl.AbstractCatalogDecorator.getLayerByName(AbstractCatalogDecorator.java:466)
> at
> org.geoserver.catalog.impl.LocalWorkspaceCatalog.getLayerByName(LocalWorkspaceCatalog.java:257)
> at
> org.geoserver.monitor.LayerNameNormalizer.run(LayerNameNormalizer.java:44)
> at
> org.geoserver.monitor.MonitorFilter$PostProcessTask.run(MonitorFilter.java:302)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> ___
> 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  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 protezi

Re: [Geoserver-users] Dynamic generated image url in SLD not working in 2.23.2

[Andrea Aime]

On Fri, Sep 1, 2023 at 11:34 AM Karsten Darré via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> Do any of you have an idea of what has changed in 2.23.2?
>

New security check, described in the GeoServer 2.23.2 release announcement:
https://geoserver.org/announcements/2023/07/21/geoserver-2-23-2-released.html
and documented in detail here:
https://docs.geoserver.org/maintain/en/user/security/urlchecks.html

You'll have to whitelist the host that generates the dynamic images

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] geoserver authentication with saml protocol

[Andrea Aime]

Interesting, good news!

The "red tape" for a maintainer is caring for the module: doing what they
can to review PRs, answering user questions,
vetting Jira tickets. But none of them applies to a community module, it's
for core and extensions module only

Cheers
Andrea

On Tue, Aug 29, 2023 at 5:47 PM Carsten Klein  wrote:

> Ciao and Hello,
>
> maybe I could have a look at the SAML community module in the near future.
> We're about to renew our web application's authentication mechanisms and it
> seems like we're moving towards Keycloak or something similar. Forwarding
> authentication information to GeoServer is a must have in some of our
> projects. This module could be a suitable starting point.
>
> @Andrea: what's red tape good for and why do "persons of interest" not get
> it?
>
> Cheers
> Carsten
> Am 29.08.2023 um 17:30 schrieb Andrea Aime:
>
> On Tue, Aug 29, 2023 at 5:11 PM Jody Garnett 
> wrote:
>
>> Ah, we should remove from docs also then.
>>
>
> I don't see it:
> https://docs.geoserver.org/latest/en/user/community/index.html#community
>
> You probably found it in the "stable" series, 2.23.x, where the module has
> not been deleted (it's gone from main, hence, from all future version):
> https://docs.geoserver.org/stable/en/user/community/index.html#community
>
> Cheers
> Andrea
>
>
>
>>
>> On Tue, Aug 29, 2023 at 2:58 PM Andrea Aime <
>> andrea.a...@geosolutionsgroup.com> wrote:
>>
>>> An important note though, that module has been removed from the main
>>> branch, as nobody
>>> has been taking care of it for years.
>>> That said, it can be revived, we just one one developer to step up
>>> becoming its new "person of interest"
>>> (like a maintainer, but without red tape).
>>>
>>> Cheers
>>> Andrea
>>>
>>> On Tue, Aug 29, 2023 at 2:09 PM Jody Garnett 
>>> wrote:
>>>
>>>> Do you mean
>>>> https://docs.geoserver.org/2.23.x/en/user/community/saml/index.html
>>>>
>>>> The community modules are available to compile (so self serve rather
>>>> than supported)
>>>>
>>>> Jody
>>>>
>>>> On Tue, Aug 29, 2023 at 11:14 AM yvan.riou--- via Geoserver-users <
>>>> geoserver-users@lists.sourceforge.net> wrote:
>>>>
>>>>> Is there an available extension to make an authentication in geoserver
>>>>> by connecting to an identity provider (like a web sso) through a saml
>>>>> protocol ?
>>>>>
>>>>> Thank you for your wonderful geoserver :)
>>>>>
>>>>> Have a nice day :)
>>>>>
>>>>> Envoyé depuis mon mobile
>>>>> ___
>>>>> 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
>>>>>
>>>> --
>>>> --
>>>> Jody Garnett
>>>> ___
>>>> 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/l

Re: [Geoserver-users] geoserver authentication with saml protocol

[Andrea Aime]

On Tue, Aug 29, 2023 at 5:11 PM Jody Garnett  wrote:

> Ah, we should remove from docs also then.
>

I don't see it:
https://docs.geoserver.org/latest/en/user/community/index.html#community

You probably found it in the "stable" series, 2.23.x, where the module has
not been deleted (it's gone from main, hence, from all future version):
https://docs.geoserver.org/stable/en/user/community/index.html#community

Cheers
Andrea



>
> On Tue, Aug 29, 2023 at 2:58 PM Andrea Aime <
> andrea.a...@geosolutionsgroup.com> wrote:
>
>> An important note though, that module has been removed from the main
>> branch, as nobody
>> has been taking care of it for years.
>> That said, it can be revived, we just one one developer to step up
>> becoming its new "person of interest"
>> (like a maintainer, but without red tape).
>>
>> Cheers
>> Andrea
>>
>> On Tue, Aug 29, 2023 at 2:09 PM Jody Garnett 
>> wrote:
>>
>>> Do you mean
>>> https://docs.geoserver.org/2.23.x/en/user/community/saml/index.html
>>>
>>> The community modules are available to compile (so self serve rather
>>> than supported)
>>>
>>> Jody
>>>
>>> On Tue, Aug 29, 2023 at 11:14 AM yvan.riou--- via Geoserver-users <
>>> geoserver-users@lists.sourceforge.net> wrote:
>>>
>>>> Is there an available extension to make an authentication in geoserver
>>>> by connecting to an identity provider (like a web sso) through a saml
>>>> protocol ?
>>>>
>>>> Thank you for your wonderful geoserver :)
>>>>
>>>> Have a nice day :)
>>>>
>>>> Envoyé depuis mon mobile
>>>> ___
>>>> 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
>>>>
>>> --
>>> --
>>> Jody Garnett
>>> ___
>>> 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  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 emai

Re: [Geoserver-users] geoserver authentication with saml protocol

[Andrea Aime]

An important note though, that module has been removed from the main
branch, as nobody
has been taking care of it for years.
That said, it can be revived, we just one one developer to step up becoming
its new "person of interest"
(like a maintainer, but without red tape).

Cheers
Andrea

On Tue, Aug 29, 2023 at 2:09 PM Jody Garnett  wrote:

> Do you mean
> https://docs.geoserver.org/2.23.x/en/user/community/saml/index.html
>
> The community modules are available to compile (so self serve rather than
> supported)
>
> Jody
>
> On Tue, Aug 29, 2023 at 11:14 AM yvan.riou--- via Geoserver-users <
> geoserver-users@lists.sourceforge.net> wrote:
>
>> Is there an available extension to make an authentication in geoserver by
>> connecting to an identity provider (like a web sso) through a saml protocol
>> ?
>>
>> Thank you for your wonderful geoserver :)
>>
>> Have a nice day :)
>>
>> Envoyé depuis mon mobile
>> ___
>> 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
>>
> --
> --
> Jody Garnett
> ___
> 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  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] WFS srsName format

[Andrea Aime]

Hi Cecile,
you're forcing that syntax in your request, which is using the east/north
ordered syntax in the Query srsName attribute (used for reprojection).
Remove it, or use the urn syntax in it as well, and you should get back the
experimental URN along with the EPSG database axis order.
See also:
https://docs.geoserver.org/main/en/user/services/wfs/axis_order.html

Cheers
Andrea




On Fri, Aug 11, 2023 at 4:50 PM Cécile Vuilleumier <
cecile.vuilleum...@camptocamp.com> wrote:

> Hello all,
>
> Using GeoServer version: 2.22.2, I am doing WFS requests from a client
> application (with WFS version 1.1.0), and the client fails to parse the
> responses because of the srsName attribute format. According to the doc*,
> the format for srsName should be urn:x-ogc:def:crs:EPSG:4326 with WFS
> 1.1.0 and 2.0.0, but GeoServer seems to always return something in the
> format http://www.opengis.net/gml/srs/epsg.xml#4326. I also checked in my
> server config for WFS and made sure the SRS Style was set to "OGC
> Experimental URN".
>
> Here is my POST request payload:
>
> http://www.opengis.net/wfs;
> <http://www.opengis.net/wfs>
> service="WFS"
> version="1.1.0"
> outputFormat="GML3"
> maxFeatures="20"
> xsi:schemaLocation="http://www.opengis.net/wfs
> http://schemas.opengis.net/wfs/1.1.0/wfs.xsd;
> <http://www.opengis.net/wfshttp://schemas.opengis.net/wfs/1.1.0/wfs.xsd>
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> <http://www.w3.org/2001/XMLSchema-instance>>
>  "http://gis; <http://gis>>
> http://www.opengis.net/ogc;
> <http://www.opengis.net/ogc>>
> 
> shape
> http://www.opengis.net/gml;
> <http://www.opengis.net/gml> srsName="EPSG:2056">
> 2661449.9
> 1239830.000305176
> 2661509.9
> 1239890.000305176
> 
> 
> 
> 
> 
>
> And the response:
>
> 
> http://www.w3.org/2001/XMLSchema;
> <http://www.w3.org/2001/XMLSchema>
> xmlns:wfs="http://www.opengis.net/wfs; <http://www.opengis.net/wfs>
> xmlns:gml="http://www.opengis.net/gml; <http://www.opengis.net/gml>
> xmlns:gis="http://gis; <http://gis>
> xmlns:si="http://www.w3.org/2001/XMLSchema-instance;
> <http://www.w3.org/2001/XMLSchema-instance>
> numberOfFeatures="1"
> timeStamp="2023-08-11T13:16:41.918Z"
> xsi:schemaLocation="http://gis
> http://geoserver:8080/geoserver/gis/wfs?service=WFSversion=1.1.0request=DescribeFeatureTypetypeName=gis%3Alayer1
> http://www.opengis.net/wfs
> http://geoserver:8080/geoserver/schemas/wfs/1.1.0/wfs.xsd;
> <http://gishttp://geoserver:8080/geoserver/gis/wfs?service=WFSversion=1.1.0request=DescribeFeatureTypetypeName=gis%3Alayer1http://www.opengis.net/wfshttp://geoserver:8080/geoserver/schemas/wfs/1.1.0/wfs.xsd>
> >
> 
> 
> 1 B0
> 270.
> 
>  "http://www.opengis.net/gml/srs/epsg.xml#2056;
> <http://www.opengis.net/gml/srs/epsg.xml#2056> srsDimension="2">
> 2661466.6601 1239877.4467
> 
> 
> 
> 
> 
>
> I've also tried with WFS 2.0.0 / GML 3.2, the srsName still comes in the
> URL format.
> Does anyone have an idea what could be the issue? Many thanks in advance.
> Cécile
>
> *Documentation:
>
> https://docs.geoserver.org/2.22.x/en/user/services/wfs/basics.html#differences-between-wfs-versions
> https://docs.geoserver.org/main/en/user/services/wfs/webadmin.html#gml
> --
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
>
> *Cécile Vuilleumier *
> Geospatial developer
>
> *Camptocamp SA*
> Route de la Chaux 4
> Bâtiment A (Feuille)
> 1030 Bussigny
> Switzerland
> +41 62 544 03 77 (direct)
> +41 21 619 10 10 (central)
> www.camptocamp.com
> ___
> 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

Re: [Geoserver-users] Get WFS on a group layer

[Andrea Aime]

Hi Tiago,
layer groups are incompatible with the WFS protocol.
Each "feature type" reported in the capabilities must have a single GML
schema, but layers in a group typically have different schemas.
As a result, the GeoServer WFS implementation does not advertise layer
groups, nor offers a way to call them directly.

That said, one can ask for multiple feature types in a single GetFeature
request, by enumerating the desired target types, e.g:

https://gs-main.geosolutionsgroup.com/geoserver/ows?service=WFS=1.0.0=GetFeature=ogcapi%3Atasmania_roads,cite:tasmania_water_bodies

As you can see, the result is probably confusing, as all features are
lumped into a single collection, it's up to the client
to be ready to parse this mixup (the same happens when requisition GeoJSON,
buf if one was to ask for shapefile,
then they would get a zip file with two separate shapefiles instead)

Cheers
Andrea

On Wed, Aug 9, 2023 at 3:05 PM Tiago Vieira  wrote:

> Hi,
>
> Can anyone help me understand if I can make a WFS getFeatures request to a
> group layer?
>
> Thank you,
> *Tiago Vieira*
> ___
> 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  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] openapi

[Andrea Aime]

The OGC API modules are community modules, which means, they are not part
of any release, but should
be used with nightly builds.
They often work mixing a release with the nightly of a module, but there
are no guarantees.

I've checked with the docker image, using both the nightly of 2.23.x and
the ogcapi module for 2.23.x (it's still
a monolith there, in the dev series it's split by service). This is what
I've done:

>  docker pull docker.osgeo.org/geoserver:2.23.x
>  docker run -it -p8080:8080   --env INSTALL_EXTENSIONS=true   --env
COMMUNITY_EXTENSIONS="ogcapi"   docker.osgeo.org/geoserver:2.23.x

The OGC API works fine in the above setup, using both a nightly of
GeoServer, along with the corresponding
OGC API community module.

The error you're getting seems to be related to an incompatibility with the
Jackson library... and indeed during the
last month, it has been upgraded: you have the 2.23.1 release that is not a
match for the jars found in the OGC API module.

You can wait for 2.23.2, which should work, at least for some time, or keep
on using nightly builds, and keep things aligned.
If you want the latest updates regarding OGC APIs, best to use the
development series anyways, it has got a number
of fixes/improvements that will not be backported to 2.23.x.

Cheers
Andrea


On Thu, Jul 13, 2023 at 7:48 PM Verbeeck Bart (AIV) <
bart.verbe...@vlaanderen.be> wrote:

> Dear list
>
>
>
> The openapi url seems not to work in version 2.23.1, in the development
> version 2.24  it works
>
>
>
>
>
> https://*/ogc/features/v1/openapi?f=text%2Fhtml
>
>
>
>
>
> {
>
>   "type": "NoApplicableCode",
>
>   "title": "'com.fasterxml.jackson.core.StreamReadConstraints
> com.fasterxml.jackson.dataformat.yaml.YAMLParser.streamReadConstraints()'"
>
> }
>
>
>
> Is this a bug or known issue?
>
>
>
> Bart
> ___
> 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  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] ImageMosaic plugin no longer available

[Andrea Aime]

Ciao Fabio,
the image mosaic module is part of core GeoServer, you don't need to
install any plugin.

I'm wondering if you're thinking about the imagemosaic-jdbc module instead,
which allowed
to mosaic raster data stored in databases? That has indeed been retired,
the original developer
stopped contributing to that module back in 2016, and a few years ago,
after asking if anyone
would be up to maintain it, or would be interested in sponsor someone to
learn and support
the module own code, we dropped it, first down to community module status,
and then remove it
altogether.

If you are interested it can be still resurrected, provided someone shows
up to be the maintainer of
the module, or sponsoring is made available to support one of the core
developers to dust off the
code, make it build again, and become proficient enough with it to maintain
it.
If anyone is interested in either possibility, please do let us know.

Cheers
Andrea


On Fri, Jul 7, 2023 at 10:55 PM Fabio Corsi <
fabio1299.discussionli...@gmail.com> wrote:

> I’m trying to upgrade a docker installation of Geoserver from 2.17 to 2.23
>
> My installation uses the Kartoza docker images, and loads a number of
> plugins on deploy.
>
> It seems that the ImageMosaic plugin is no longer available on the
> standard Sourceforge  repository for any version of Geoserver past 2.17.
>
> The plugin seems to still be supported (
> https://docs.geoserver.org/stable/en/user/data/raster/imagemosaic/index.html),
> so I’m wondering how to install it in Docker images later than 2.17.
>
> Thanks for your advice.
>
> ___
> 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  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] Remove Layer Preview from Login Page (SOLVED)

[Andrea Aime]

On Sat, Jul 1, 2023 at 3:37 PM Ian Turton  wrote:

>
> Please make the change to the documentation, then everyone will benefit
> from your work
>
>
With a big red warning stating that's not proper security, please: it will
only fool users that can't build OGC requests.

Cheers
Andrea

-- 

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 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] Inclusion mapOnly not working?

[Andrea Aime]

Text symbolizers are not being represented in png legend anyways, as far as
I know?
Unless... are you talking about the JSON legend output format?

Cheers
Andrea

On Thu, Jun 22, 2023 at 10:02 PM Jonathan D  wrote:

> It seems in Geoserver 22.0 and above that:
>
> mapOnly
>
> is not working (excluding the symbolizer from the legend) when included
> inside a  element.
>
> Can anyone else confirm this is the case?
> ___
> 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  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] Legend height and with

[Andrea Aime]

Nope, it's hard coded:

https://github.com/geoserver/geoserver/blob/main/src/wms/src/main/java/org/geoserver/wms/capabilities/Capabilities_1_3_0_Transformer.java#L1687

Cheers
Andrea

On Wed, Jun 28, 2023 at 9:21 AM Karsten Darré via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> Hello Geoserver Users
>
>
>
> Is there any way to exclude the height and width of the legend URL in
> capability documents?
>
>
>
> Med venlig hilsen / Best regards
>
>
>
> *Karsten Darré*
>
> GIS-udvikler
>
>
>
> LIFA A/S
>
> GeoData
>
>
>
>
> ___
> 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  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] GeoServer stop support for older WCS versions

[Andrea Aime]

Funny enough, I was wondering some days ago if we could move the WCS 1.0
and 1.1
out of core, and make them optional extensions (still part of releases,
just not in the base package).
After some checks, I've found that QGIS WCS support is still limited to 1.0
and 1.1 <https://github.com/qgis/QGIS/issues/45584>, so...nope, they have
to stay in core.

Cheers
Andrea

On Thu, Jun 29, 2023 at 12:39 AM Bessette-Halsema, Dominique E via
Geoserver-users  wrote:

> Hello
>
>
>
> Is there a risk that newer versions of Geoserver will ever drop support
> for the older WCS versions?  For example WCS 1.0.0?
>
>
>
>
>
> Dominique Bessette
>
>
> ___
> 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  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] Remove Layer Preview from Login Page

[Andrea Aime]

On Wed, Jun 28, 2023 at 7:55 AM Carsten Klein  wrote:

> And also, that's not the point. The problem is, that those company's
> security officers *can see* this obvious "security hole" and focus on
> that. Since they also have no ideas about WMS they just don't see that
> removing anonymous access to Layer Preview is no real solution (and its a
> long hard way to make them see...). So, they keep insisting on removing it.
> Don't you experience the same in your businesses? A company's security
> requests often are far from rational but paranoid :)
>

We normally don't do "security by obscurity", at least not by choice,
closing the main door, but leaving the back window open.
If you enable WFS only to some users, they can also download KML from it,
but it will be without any styling, just data, unlike the KML you could get
from WMS.

I don't believe a solution exists to block a specific output format for
only certain users, but if I had to do it, I'd extend GeoFence
to handle that case as well.

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 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] h2gis and Geoserver 2.22-2.23

[Andrea Aime]

Chris, think about it well, because the H2 version 1 database is already
removed from
GeoServer core, and in time (pending funding), it will be removed from the
rest of GeoServer as well,
and eventually the H2 datastore will die too.

So it's high time to start looking into a migration to some other solution:
GeoPackage if you have
to do it right now, or the latest H2Gis in the medium term, or if you know
you'll never use the
other modules that need H2 version 1 (e.g., NetCDF/Grib)

Best regards
Andrea

On Tue, Jun 27, 2023 at 5:34 PM Chris Mugdan 
wrote:

> Hi Mark,
>
> Thank you for your response. Either way it would be a pain for us
> because the H2 database is now heavily embedded in our product. We shall
> have to ponder the direction we take. I shall examine geopackage.
>
> Cheers,
> Chris
>
> On 27/06/2023 3:26 pm, mark wrote:
> > Op 23-06-2023 om 12:22 schreef Chris Mugdan:
> >> The question is: can I get all this to work with Geoserver 2.23 or
> >> 2.24? Since there are issues with the latest h2gis, can we make the
> >> version we are currently using (1.3.2) work or are there some basic
> >> incompatibilities that render our current version of h2gis, H2 and
> >> supporting classes useless?
> >
> > newer versions of GeoTools/Geoserver use a newer version of JTS that
> > is incompatible with older versions; this is mostly package names
> > though, so if you were to start of with the original obisgis
> > geotool/geoserver code you could maybe migrate that to be compatible
> > with eg 2.23.x geoserver.
> > Some other things in Geotools have changed; but there's documentation
> > on that: https://docs.geotools.org/stable/userguide/welcome/upgrade.html
> >
> > It could be painful and you may be better off reconsidering the
> > datastore and workflow to eg. use geopackage instead
> >
> > Mark
> >
> >
> > ___
> > 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 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  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
_

Re: [Geoserver-users] Styled marks shape dot does not work in geoserver version 2.23.1

[Andrea Aime]

Thinking out loud, could it be that something environmental changed then?
Like, for example, the JDK in use?

Cheers
Andrea

On Thu, Jun 22, 2023 at 9:43 AM Ian Turton  wrote:

> I can confirm that the dot pattern doesn't seem to work in 2.22.2 either
> but the relevant code (
> https://github.com/geotools/geotools/blame/379ae1335ebfba758a03b61be97a20be838900e3/modules/library/render/src/main/java/org/geotools/renderer/style/ShapeMarkFactory.java#L47)
> doesn't seem to have changed in more than 5 years.
>
> Looking at the logs seems to indicate that the renderer looks through some
> (all) the MarkFactories and finds the mark and draws it
>
> 22 Jun 08:30:34 TRACE  [renderer.style] - fetching mark of name shape://dot
> 22 Jun 08:30:34 TRACE  [renderer.style] - Could not find the symbol,
> returning null
> 22 Jun 08:30:34 TRACE  [renderer.style] - fetching mark of name shape://dot
> 22 Jun 08:30:34 TRACE  [renderer.style] - applying stroke to mark
>
> So it looks like something odd is happening, if you can raise a bug
> someone may look at it, though probably not this coming week as its FOSS4G
>
> Ian
>
>
>
> On Thu, 22 Jun 2023 at 07:41, Daniele Maggiolo 
> wrote:
>
>> Hi, the result I get is a polygon without filling with dots.
>>
>> If I use shape://slash it works like it always did in all versions
>> (showing me the lines as a fill of the polygon). The only one I can't get
>> to work anymore is shape://dot (in 2.23.1 version).
>>
>>
>>
>> Daniele
>>
>>
>>
>>
>>
>> *Da:* Ian Turton 
>> *Inviato:* martedì 20 giugno 2023 18:11
>> *A:* Daniele Maggiolo 
>> *Cc:* geoserver-users@lists.sourceforge.net
>> *Oggetto:* Re: [Geoserver-users] Styled marks shape dot does not work in
>> geoserver version 2.23.1
>>
>>
>>
>> can you give us any clues as to what doesn't work? is nothing drawn? does
>> the program crash? is a penguin produced?
>>
>>
>>
>> What does the log file show any interesting information? what if you turn
>> logging up to GeoTools-dev level and try again?
>>
>>
>>
>> Ian
>>
>>
>>
>> On Tue, 20 Jun 2023 at 16:05, Daniele Maggiolo via Geoserver-users <
>> geoserver-users@lists.sourceforge.net> wrote:
>>
>> Hi,
>>
>> I noticed that the styled mark shape://dot doesn't work in GeoServer
>> version 2.23.1.
>>
>> I've tried both creating a style with CSS and SLD. In version 2.22.2
>> everything worked fine.
>>
>> Below is an example of a style created using CSS.
>>
>>
>>
>> @mode 'Auto';
>> @styleTitle 'Test';
>> @styleAbstract 'Test';
>>
>> /* @title Test
>> * @abstract Test
>> */
>> *{
>>   stroke: #a0a0f5;
>>   stroke-width: 1;
>>   fill: symbol("shape://dot");
>> :fill {
>> size: 5;
>> stroke: #a0a0f5;
>> stroke-width: 1;
>>   fill: #a0a0f5;
>> }
>> }
>>
>>
>>
>> ___
>> 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
>>
>>
>>
>> --
>>
>> Ian Turton
>>
>
>
> --
> Ian Turton
> _______
> 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 Profes

Re: [Geoserver-users] [GeoWebCache/GS] Cache-Recycling

[Andrea Aime]

On Wed, Jun 21, 2023 at 4:44 PM Ian Turton  wrote:

> Again GeoServer has no way of knowing (without a lot of work) which tiles
> are invalid with a style change so it needs to redraw all of them
>

A comparison of two SLD trees would be possible, figuring out if the edits
changed the tiles, but as you say,
it's going to be complicated. Having the automatic tile drop automation
admin controllable (on/off) is certainly easier.

There are some classes of edits that could be identified, which do not
affect, or just partially affect, the tiles:

   - Changes rule names, titles and the like
   - Changes in a rule that is active only in a given scale range (just
   drop tiles in such range)
   - Changes in a rule that matches only certain features (attribute
   filter), figure out their bbox if there is a quick way to do so, only drop
   in the bbox

As said, far away from trivial... a parallel scan of the two SLD object
trees would have to be implemented, which goes
hunt for certain types of differences.

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] [GeoWebCache/GS] Cache-Recycling

[Andrea Aime]

On Mon, Jun 19, 2023 at 2:24 PM  wrote:

> Hi GeoServer-experts,
>
> I am running a fairly large GS-deployment on k8s with the included,
> preseeded GWC.
> I noticed that changing SLD-files results in invalidating the cache-Folder
> and deleting the whole preseeded cache. I was hit by this "feature" in the
> past once.
>
> So 2 questions in this context:
>
> 1) Is it possible to deactivate this feature by myself to that I can
> decide when I will recreate the new Cache?
>

No, it's hard coded. Could be made configurable with some development.


> 2) Does the removal of the preseeded Cache also for changing
> Min/MaxScaleDenominators inside the SLDs and in the GWC-layer-config?
>

It's quite primitive, does not check what type of change you made, just
cleans everything that might be affected.
This catalog listener has pretty much stayed unchanged in the last 10
years. It's the classic "we'll do a basic implementation
now and surely someone will pop up to contribute a smarter implementation
down the road", and years later the answer is still "nope, not yet".

Not all hope is lost though, see this document on how to make it happen:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-fixes,-improvements-and-new-features-in-GeoServer

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] Outdated log4j 1.2 in 2.23.1 distribution

[Andrea Aime]

Hi,
yes, it's an assembly leftover, as far as I know, you can safely remove it.
See also:

   - https://osgeo-org.atlassian.net/browse/GEOS-10874
   - https://github.com/geoserver/geoserver/pull/6956

(the Windows binary is based on the bin package, hence, they both contain
that same extra file)

Cheers
Andrea

On Tue, Jun 20, 2023 at 1:46 PM Demian Katz via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> Hello, everyone!
>
>
>
> I’ve been working on cleaning out old versions of Log4j on my servers, and
> I just discovered that the latest Geoserver “Platform Independent Binary”
> (v2.23.1) is still shipping with log4j 1.2 bundled in, even though it also
> includes log4j 2.17.2 and the bridge configuration. I’m guessing this may
> be some kind of packaging error; deleting the old log4j 1.2 jar does not
> seem to have interfered with the operation of my instance.
>
>
>
> I tried to access the issue tracker to see if anyone else had reported
> this, but I had trouble getting in – apologies if I made a newbie error
> somewhere, or if I’m misunderstanding what I’m seeing. In any case, I just
> thought someone in the community might want to know about this!
>
>
>
> And here’s some evidence to demonstrate what I’m seeing – my command line
> from this morning when I downloaded a fresh .zip file and confirmed that
> the extra log4j jar still seems to be in there:
>
>
>
> $ wget
> https://sourceforge.net/projects/geoserver/files/GeoServer/2.23.1/geoserver-2.23.1-bin.zip
>
> […]
>
> 2023-06-20 07:40:06 (3.67 MB/s) - ‘geoserver-2.23.1-bin.zip’ saved
> [119749074/119749074]
>
>
>
> $ unzip -l geoserver-2.23.1-bin.zip  | grep log4j
>
>302511  05-04-2022 12:29
> webapps/geoserver/WEB-INF/lib/log4j-api-2.17.2.jar
>
>   1811089  05-04-2022 12:29
> webapps/geoserver/WEB-INF/lib/log4j-core-2.17.2.jar
>
>303443  05-04-2022 14:30
> webapps/geoserver/WEB-INF/lib/log4j-1.2-api-2.17.2.jar
>
> 30948  05-04-2022 13:17
> webapps/geoserver/WEB-INF/lib/log4j-jul-2.17.2.jar
>
> 12844  05-04-2022 12:29
> webapps/geoserver/WEB-INF/lib/log4j-jcl-2.17.2.jar
>
> 24248  05-04-2022 13:21
> webapps/geoserver/WEB-INF/lib/log4j-slf4j-impl-2.17.2.jar
>
>302511  05-04-2022 12:29   lib/log4j-api-2.17.2.jar
>
>   1811089  05-04-2022 12:29   lib/log4j-core-2.17.2.jar
>
>303443  05-04-2022 14:30   lib/log4j-1.2-api-2.17.2.jar
>
> 30948  05-04-2022 13:17   lib/log4j-jul-2.17.2.jar
>
> 12844  05-04-2022 12:29   lib/log4j-jcl-2.17.2.jar
>
> 24248  05-04-2022 13:21   lib/log4j-slf4j-impl-2.17.2.jar
>
>489884  05-04-2020 06:46   lib/log4j-1.2.17.jar
>
>   289  05-04-2023 12:28   resources/log4j.properties
>
>
>
> I hope this is helpful!
>
>
>
> - Demian
> ___
> 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  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 y

Re: [Geoserver-users] filtering a wms layer intersecting a polygon

[Andrea Aime]

On Thu, Jun 8, 2023 at 11:04 PM Julien Robitaille 
wrote:

> Hello!
> I am trying to figure out if what I want to do is possible. I have a
> raster layer of surface current data. Since some of the data overlaps the
> land, I want to be able to filter out the pixels that appear on land. I
> thought of doing it by adding to our geoserver a vector polygon vector
> layer representing the water bodies.
> And I would like to be able to intersect my raster layer with that vector
> layer. Is this possible to perform, maybe with the cross-layer filtering
> <https://docs.geoserver.org/2.22.x/en/user/extensions/querylayer/index.html#wms-examples>plugin?
> The thing is that I am not sure if technically it is possible to filter a
> raster layer based on a vector.
>

What you're trying to do is not understood as filtering in GeoServer, but
clipping.
You can provide a clip geometry inline in the WMS request, using the "clip"
vendor parameter:
https://docs.geoserver.org/latest/en/user/services/wms/vendor.html#clip

Works both against rasters and vectors. The polygon must be simple enough
to fit in the URL

Regards
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] Question about the OSM map of geoserver.org

[Andrea Aime]

Hi Alexandre,
I'm not aware of plans, but at the same time, I was not aware of the
differences either,
maybe someone else in the company updated the map.

If you feel like updating the map, make a PR against osm-style, the repo is
open
<https://github.com/geosolutions-it/osm-styles#found-an-issue-contribute-a-fix>
to external contributions
<https://github.com/geosolutions-it/osm-styles#found-an-issue-contribute-a-fix>
.

Cheers
Andrea


On Wed, Jun 14, 2023 at 10:03 AM Alexandre Gacon 
wrote:

> Hi,
>
> The OSM map available on geoserver.org seems more elaborated than the one
> provided on https://github.com/geosolutions-it/osm-styles (for example
> you draw the boundaries and you have the name of the countries). From the
> capability URL of the server, it seems that you have added data from
> natural earth too.
>
> @Andrea, do you plan to update the github repo?
>
> --
> Alexandre Gacon
> ___
> 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  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] Error configuring external WFS layers

[Andrea Aime]

he.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
>
> at
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:770)
>
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1415)
>
> at
> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
>
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown
> Source)
>
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
> Source)
>
> at
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>
> at java.lang.Thread.run(Unknown Source)
>
> Caused by: java.lang.reflect.InvocationTargetException
>
> at sun.reflect.GeneratedMethodAccessor595.invoke(Unknown Source)
>
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>
> at java.lang.reflect.Method.invoke(Unknown Source)
>
> at
> org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:258)
>
> ... 122 more
>
> Caused by: java.lang.RuntimeException: Error occurred while building the
> resources for the configuration page
>
> at
> org.geoserver.web.data.layer.NewLayerPage.buildLayerInfo(NewLayerPage.java:435)
>
> at
> org.geoserver.web.data.layer.NewLayerPage$9.onClick(NewLayerPage.java:324)
>
> at
> org.geoserver.web.wicket.SimpleAjaxLink$1.onClick(SimpleAjaxLink.java:47)
>
> at
> org.apache.wicket.ajax.markup.html.AjaxLink$1.onEvent(AjaxLink.java:85)
>
> at
> org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:155)
>
> at
> org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:601)
>
> ... 126 more
>
> Caused by: java.lang.IllegalArgumentException: *Client does not support
> any of the server supported output formats for DESCRIBE_FEATURETYPE*
>
> at
> org.geotools.data.wfs.internal.AbstractWFSStrategy.getDefaultOutputFormat(AbstractWFSStrategy.java:390)
>
> at
> org.geotools.data.wfs.internal.WFSRequest.(WFSRequest.java:73)
>
> at
> org.geotools.data.wfs.internal.DescribeFeatureTypeRequest.(DescribeFeatureTypeRequest.java:28)
>
> at
> org.geotools.data.wfs.internal.WFSClient.createDescribeFeatureTypeRequest(WFSClient.java:358)
>
> at
> org.geotools.data.wfs.WFSDataStore.getRemoteFeatureType(WFSDataStore.java:203)
>
> at
> org.geotools.data.wfs.WFSDataStore.getRemoteSimpleFeatureType(WFSDataStore.java:262)
>
> at
> org.geotools.data.wfs.WFSFeatureSource.buildFeatureType(WFSFeatureSource.java:361)
>
> at
> org.geotools.data.store.ContentFeatureSource.getAbsoluteSchema(ContentFeatureSource.java:328)
>
> at
> org.geotools.data.store.ContentFeatureSource.getSchema(ContentFeatureSource.java:297)
>
> at
> org.geotools.data.store.ContentDataStore.getSchema(ContentDataStore.java:293)
>
> at
> org.geoserver.feature.retype.RetypingDataStore.updateMap(RetypingDataStore.java:214)
>
> at
> org.geoserver.feature.retype.RetypingDataStore.getFeatureSource(RetypingDataStore.java:169)
>
> at
> org.geoserver.feature.retype.RetypingDataStore.getFeatureSource(RetypingDataStore.java:325)
>
> at
> org.geoserver.feature.retype.RetypingDataStore.getFeatureSource(RetypingDataStore.java:47)
>
> at
> org.geoserver.catalog.CatalogBuilder.buildFeatureType(CatalogBuilder.java:326)
>
> at
> org.geoserver.web.data.layer.NewLayerPage.buildLayerInfo(NewLayerPage.java:425)
>
> ... 131 more
>
> An error occurred while loading the page
>
>
>
> Any Ideas?
>
>
>
> Capabilities url:
>
> http://ovc.catastro.meh.es/INSPIRE/wfsCP.aspx?service=WFS=GetCapabilities
>
>
>
> Thanks in advance.
>
> [image:
> http://www.tragsa.es/SiteCollectionImages/Relaciones%20Institucionales%20(Prensa)/FIRMA%20OUTLOOK/2023tragsatec.png]
>
> *Briones Garcia, Pedro *
> JGAP Sist Inform Geográfica
> S.Información Geográfica / G.Sist.Inf. Geografica
>
> Grupo Tragsa - SEPI
>
>
>
> Calle Julián Camarillo 6B - 28037 Madrid
> Tel.: 913226489 - 88216 - Fax: 913226005
> p...@tragsa.es
> *www.tragsa.es * <https://www.tragsa.es/>
>
>
>
>
> *AVISO LEGAL * <https://www.tragsa.es/es/Paginas/aviso-legal-correo.aspx>
>
>
> *POLITICA DE PRIVACIDAD, de conformidad con el Reglamento UE 2016/679 y la
> Ley Orgánica 3/2018 *
> <https://www.tragsa.es/es/Paginas/politica-privacidad-correo.aspx>
>
&

Re: [Geoserver-users] Use translation in Layer Preview ?

[Andrea Aime]

On Fri, Jun 2, 2023 at 11:29 AM Alexandre Gacon 
wrote:

> Hello,
>
> What do you think about the idea to use the selected language in the UI to
> ask GeoServer to display the correct languages for items when a translation
> is possible?
>

Nice idea. Since titles and legends are not really used in the preview
outputs, I'm guessing you're mostly referring to map labelling/symbology,
right?
Then, "when translation is possible" is the tricky bit, it would require
analyzing the contents of the SLD, as it's all based on dynamic functions
<https://docs.geoserver.org/stable/en/user/styling/sld/language.html>,
and make a guess based on some common usage patterns. (e.g., using the
language function inside recode, but it could also be using
a tree of if_then_else for example).

As simpler alternative, just blinding add the language= in the request
based on the combo box, and let the style do its thing,
hoping it was set up to produce some output regardless of the choice being
made. For example, look at this, taken from the
<https://docs.geoserver.org/stable/en/user/styling/sld/language.html#using-the-language-function>
documentation
<https://docs.geoserver.org/stable/en/user/styling/sld/language.html#using-the-language-function>
:

 

  


name_default
en
name_en
it
name_it
fr
name_fr
  


  #00



The above SLD generates labels for cases with no LANGUAGE parameter, and
for en, it, fr values. If you input something
else (e.g. ger/de) then you'd get no label at all. Figuring out if the SLD
has general defaults seems roughly as hard as
coming up with a list of languages it would support.

Cheres
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] Using WFS Schema mapping to remove namespace?

[Andrea Aime]

On Mon, Jun 5, 2023 at 12:32 PM Brad Hards  wrote:

> I do want the namespace on the top level item, but not on the attributes,
> so
> something like:
>
>
> 
> 
> 
> 
>  gml:MultiSurface>
> Admin-0 country
> 5
> 6
> ...
> Admin-0 country
> 
> 
> 
>

This is really weird... and would be valid only if "ne" is made the default
namespace,
in addition to being also declared on the "ne" prefix. So odd that I'm not
sure it's even completely valid LOL.
Unless you are implying that stuff like scalerank is not associated to any
namespace at all... which
again I'm not sure is valid or not, schema compliance wise).


>
> It looks like WFS Schema Mapping (
> https://docs.geoserver.org/stable/en/user/
> services/wfs/schemamapping.html
> <https://docs.geoserver.org/stable/en/user/services/wfs/schemamapping.html>)
> might be able to help, but I'm not sure what
> the changes to the schema file would need to look like.
>
> Can anyone suggest a way forward, or confirm this is a dead end and I'll
> need
> to use something heavier (like app-schema, which I'm a bit scared of)?
>

I doubt either would work, since they are both schema driven systems... but
who knows.
What might give you enough control is features-templating
<https://docs.geoserver.org/stable/en/user/community/features-templating/index.html>,
where you basically have a template engine that might give you enough
control over the output (no promises, never tried to do something like
you're looking for).

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] Geoserver doesn't sync roles from Keycloak

[Andrea Aime]

Hi Emanuele,
I have no direct experience with the Keycloak plugin, but quickly scanning
the code,
it definitely tries to fetch roles, by making extra requests to the
Keycloak server, around here:
https://github.com/geoserver/geoserver/blob/e48780cacce179dc4d70ea6f1928f25f236e50ab/src/community/security/keycloak/src/main/java/org/geoserver/security/keycloak/KeycloakRESTClient.java#L92

I see there is some logging, so setting the log level to "geoserver
developer logging" might give you
something to work on.

If it's not enough a step by step debug session is needed... if that's the
case, see here:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-fixes,-improvements-and-new-features-in-GeoServer

Cheers
Andrea

On Wed, May 24, 2023 at 3:24 PM 
wrote:

> Hi,
>
> I'm trying to build an infrastucturewith GeoServer which uses Keycloak as
> a service for authentication and managing roles. I'm using this
> <https://docs.geoserver.org/2.23.x/en/user/community/keycloak/index.html> 
> documentation
> to enable Keycloak and it seems to work with the authentication part, but i
> can't seem to be able to make geoserver sync with Keycloak roles.
> I followed step by step the guide, although the keycloak interface has
> changed from the images in the guide, but i can't find a way to make it
> work.
>
> I created the roles in keycloak, assigned them to some users. In Geoserver
> I added a new Keycloak Role Service, added to the authentication filter,
> set it to active role service, but it doesn't sync the roles.
>
> I don't know how to find out what the problem is and the online
> documentation / blogs are very scarce.
>
> I'm using Geoserver 2.22.3 with Keycloak plugin version 2.22-SNAPSHOT.
>
> Thank you in advance for the support,
> Emanuele.
> ___
> 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  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] GetFeatureInfo costumize

[Andrea Aime]

Hi,
if your GeoServer installation is recent enough, there ia a vendor
parameter you can add in the SLD,
to have labels show up. See the documentation here:

https://docs.geoserver.org/latest/en/user/tutorials/GetFeatureInfo/raster.html

Cheers
Andrea

On Thu, May 25, 2023 at 11:10 AM Miguel Ángel Parrilla Godínez via
Geoserver-users  wrote:

> Hello team,
>
> https://tinyurl.com/2k5jbawh
>
>
>
> We have published a raster image with Geoserver with a sld. The sld gives
> a category per intervals of pixel values.
>
>
>
> Is it possible to show in the get feature info the label of the sld, for
> instance ‘*Pendiente baja – orientación N’ *instead of the pixel value.
>
>
>
> Thanks.
>
> Miguel Ángel.
>
>
>
> --
>
> AVISO LEGAL: Este correo y en su caso su(s) archivo(s) adjunto(s),
> proceden de TRACASA INSTRUMENTAL, S.L. y se dirige exclusivamente a su
> destinatario, puede contener información privada o confidencial amparada
> por el secreto de empresa, y a la que sólo tiene el derecho de acceder el
> destinatario. Si no es Vd. el destinatario indicado, o la persona
> responsable de su entrega al mismo, deberá abstenerse de examinar su
> contenido y queda notificado de que la utilización, divulgación y/o copia
> sin autorización está prohibida en virtud de la legislación vigente. Si ha
> recibido este mensaje por error, le rogamos que nos lo comunique
> inmediatamente mediante correo electrónico a esta misma dirección, y
> proceda a su destrucción segura. TRACASA INSTRUMENTAL, S.L. es el
> responsable de tratamiento de los datos de carácter personal facilitados
> que se utilizarán con la finalidad de mantener comunicaciones con usted.
> Tiene la posibilidad de ejercitar los derechos de acceso, rectificación,
> limitación del tratamiento, supresión y portabilidad, mediante solicitud
> dirigida por escrito, acreditando su identidad a la dirección electrónica
> d...@itracasa.es. Puede consultar información adicional y detallada sobre
> nuestra política de protección de datos de nuestra web www.itracasa.es.
> ___
> 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  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