geoserver-users — Project anouncements and support for geoserver users

Re: [Geoserver-users] GeoWebCache number of tiles in different SRID

[Andrea A. <and...@ge...>]

Hi,
because the two gridsets are not aligned, scale wise... check the gridset
definitions, at zoom level 12:

   - EPSG:4326 has a scale of 1:136k
   - EPSG:3857 has a scale of 1:68k

It all starts at zoom level 0... the first covers the entire planet with 2
tiles side by side, the second uses a single tile to
cover almost of all the planet (polar caps excluded).

Generally speaking, grisets zoom levels are not comparable with each other.

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, Aug 6, 2024 at 1:18 PM Briones Garcia, Pedro <pb...@tr...> wrote:

> Hello everybody.
>
>
>
> I am generating tiles with GeoWebCache integrated with GeoServer. Can
> someone explain me why when generating tiles of the *same area* in
> EPSG:4326 there are approximately double or triple as many files as in
> EPSG:900913 (same as EPSG:3857)?
>
>
>
> Example screenshots are attached for zoom level 12, although it occurs at
> all levels.
>
>
>
> Regards
>
>
>
> [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 JULIAN CAMARILLO 6 B - 28006 Madrid
> Tel.: 913226489 - 88216 - Fax: 913226005
> pb...@tr...
> *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
>
>
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

[Geoserver-users] GeoWebCache number of tiles in different SRID

[Briones G. P. <pb...@tr...>]

Hello everybody.

I am generating tiles with GeoWebCache integrated with GeoServer. Can someone explain me why when generating tiles of the same area in EPSG:4326 there are approximately double or triple as many files as in EPSG:900913 (same as EPSG:3857)?

Example screenshots are attached for zoom level 12, although it occurs at all levels.

Regards

[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 JULIAN CAMARILLO 6 B - 28006 Madrid
Tel.: 913226489 - 88216 - Fax: 913226005
pb...@tr...<mailto:pb...@tr...>
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] Unable to update GML Multisurface after GeoServer upgrade

[Matthew C. <mch...@da...>]

Good plan.  You caught me being lazy... And also hoping I was just doing something dumb.  I'll report back.

Thanks for all you do, Jody!
Matt
________________________________
From: Jody Garnett <jod...@gm...>
Sent: Thursday, August 1, 2024 11:40 AM
To: Matthew Charton <mch...@da...>
Cc: geo...@li... <geo...@li...>
Subject: Re: [Geoserver-users] Unable to update GML Multisurface after GeoServer upgrade

It would help if you could identify when (what version upgrade) it stopped working in?

You can find out quickly by testing 2.21 (1/2 way bwtween) and then test higher (or lowere) depending on if it works.

Once you find that out you can look at the release notes for the update that breaks things.  And then we can look for any bug fixes or features that may be involved.

Since it’s a .NET error it feels like the problem may be with the server (or something) rather than in GeoServer which is written in Java and not .NET.

(dot Net is a silly name / who starts a word with the end of a sentence - someone at Microsoft does not like grammar and is getting revenge).

- -
Jody Garnett


On Thu, Aug 1, 2024 at 9:05 AM Matthew Charton <mch...@da...<mailto:mch...@da...>> wrote:
Sorry for the crosspost from GIS Stackexchange (https://gis.stackexchange.com/questions/483890/unable-to-update-gml-multisurface-after-geoserver-upgrade), but the conversation there fizzled out.

We are testing a (much needed) upgrade from GeoServer 2.17.2 to 2.25.1. We are currently stumped as to why we can't seem to be able to update or insert a multisurface using the same WFS transaction as with 2.17. I'm sure there is something simple we are missing here, so I'm hoping someone can point us in the right direction.
Here is an example transaction that is failing:

<wfs:Transaction service="WFS" version="1.1.1" xmlns:ogc="http://www.opengis.net/ogc" xmlns:wfs="http://www.opengis.net/wfs" xmlns:gml="http://www.opengis.net/gml" xmlns:MyWorkspace="http://mydomain.com/myworkspace">
    <wfs:Update typeName="MyWorkspace:MyLayer">
        <wfs:Property>
            <wfs:Name>Item_Name</wfs:Name>
            <wfs:Value><![CDATA[Bob]]></wfs:Value>
        </wfs:Property>
        <!--other properties-->
        <wfs:Property>
            <wfs:Name>SHAPE</wfs:Name>
            <wfs:Value>
                <gml:MultiSurface srsName='http://www.opengis.net/gml/srs/epsg.xml#4326'>
                    <gml:surfaceMembers>
                        <gml:Polygon>
                            <gml:exterior>
                                <gml:LinearRing>
                                    <gml:posList>-92.6834743019173 35.2264426107788 -92.6830394566101 35.2264555548522 -92.68301875 35.2266209299999 -92.6834852899999 35.22663787 -92.6834743019173 35.2264426107788</gml:posList>
                                </gml:LinearRing>
                            </gml:exterior>
                        </gml:Polygon>
                        <gml:Polygon>
                            <gml:exterior>
                                <gml:LinearRing>
                                    <gml:posList>-92.6830420474193 35.2264347826591 -92.6827235345709 35.2264521083911 -92.68272353 35.2266102100001 -92.68301873 35.22662093 -92.6830420474193 35.2264347826591</gml:posList>
                                </gml:LinearRing>
                            </gml:exterior>
                        </gml:Polygon>
                    </gml:surfaceMembers>
                </gml:MultiSurface>
            </wfs:Value>
        </wfs:Property>
        <ogc:Filter>
            <PropertyIsEqualTo>
                <PropertyName>OBJECTID</PropertyName>
                <Literal><![CDATA[100832369]]></Literal>
            </PropertyIsEqualTo>
        </ogc:Filter>
    </wfs:Update>
</wfs:Transaction>




And here is what I feel is the relevant error logged in GeoServer:


ERROR  [geoserver.wfs] - Transaction failed
org.geoserver.wfs.WFSTransactionException: Update error: Error occured updating features
...
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: A .NET Framework error occurred during execution of user-defined routine or aggregate "geometry":
System.FormatException: 24114: The label MULTISURFACE (((-92. in the input well-known text (WKT) is not valid. Valid labels are POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, GEOMETRYCOLLECTION, CIRCULARSTRING, COMPOUNDCURVE, CURVEPOLYGON and FULLGLOBE (geography Data Type only).

Developer level logging shows the following "info" log:


    INFO   [geoserver.wfs] -
Request: transaction
    service = WFS
    version = 1.1.1
    baseUrl = http://myurl:myport/geoserver/
    group[0] = wfs:update=net.opengis.wfs.impl.UpdateElementTypeImpl@2f8c1c44 (filter: [[ OBJECTID = 100832369 ]], handle: null, inputFormat: <unset>, srsName: null, typeName: {http://myurl/myworkspace}mylayer)group[0]<http://myurl/myworkspace%7Dmylayer)group%5B0%5D> = wfs:delete=net.opengis.wfs.impl.DeleteElementTypeImpl@645e0daf (filter: [[ OBJECTID = 100832371 ]], handle: null, typeName: {http://myurl/myworkspace}mylayer<http://myurl/myworkspace%7Dmylayer>)
    update[0]:
        property[0]:
            ... several redacted properties and values ...
            name = SHAPE
            value = MULTIPOLYGON (((-92.6834743019173 35.2264426107788, -92.6830394566101 35.2264555548522, -92.68301875 35.2266209299999, -92.6834852899999 35.22663787, -92.6834743019173 35.2264426107788)), ((-92.6830420474193 35.2264347826591, -92.6827235345709 35.2264521083911, -92.68272353 35.2266102100001, -92.68301873 35.22662093, -92.6830420474193 35.2264347826591)))
        filter = [[ OBJECTID = 100832369 ]]
        inputFormat = x-application/gml:3
        typeName = {http://myurl/myworkspace}mylayer<http://myurl/myworkspace%7Dmylayer>
    delete[0]:
        filter = [[ OBJECTID = 100832371 ]]
        typeName = {http://myurl/myworkspace}mylayer<http://myurl/myworkspace%7Dmylayer>
    releaseAction = ALL
INFO   [geoserver.servlets] - OutputStream was successfully aborted.

(Note, I am doing a delete in the same transaction here in this log which I'm not showing in the example transaction above, but it happens without it as well.)

Very interesting that the geometry is already converted to multipolygon here. Not sure why it isn't hitting SQL as a multipolygon.

I have tried altering the WFS version of the transaction and specifying GML version and even changing to explicitly using multipolygon instead of multisurface, but I'm to the point that I'm just shooting in the dark.

This is a bit of a showstopper for us with the upgrade, so any help would be very much appreciated.

Thanks,
Matt

_______________________________________________
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


Geo...@li...<mailto:Geo...@li...>
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Unable to update GML Multisurface after GeoServer upgrade

[Jody G. <jod...@gm...>]

It would help if you could identify when (what version upgrade) it stopped
working in?

You can find out quickly by testing 2.21 (1/2 way bwtween) and then test
higher (or lowere) depending on if it works.

Once you find that out you can look at the release notes for the update
that breaks things.  And then we can look for any bug fixes or features
that may be involved.

Since it’s a .NET error it feels like the problem may be with the server
(or something) rather than in GeoServer which is written in Java and not
.NET.

(dot Net is a silly name / who starts a word with the end of a sentence -
someone at Microsoft does not like grammar and is getting revenge).

- -
Jody Garnett


On Thu, Aug 1, 2024 at 9:05 AM Matthew Charton <mch...@da...>
wrote:

> Sorry for the crosspost from GIS Stackexchange (
> https://gis.stackexchange.com/questions/483890/unable-to-update-gml-multisurface-after-geoserver-upgrade),
> but the conversation there fizzled out.
>
> We are testing a (much needed) upgrade from GeoServer 2.17.2 to 2.25.1. We
> are currently stumped as to why we can't seem to be able to update or
> insert a multisurface using the same WFS transaction as with 2.17. I'm sure
> there is something simple we are missing here, so I'm hoping someone can
> point us in the right direction.
> Here is an example transaction that is failing:
>
> <wfs:Transaction service="WFS" version="1.1.1" xmlns:ogc="http://www.opengis.net/ogc" xmlns:wfs="http://www.opengis.net/wfs" xmlns:gml="http://www.opengis.net/gml" xmlns:MyWorkspace="http://mydomain.com/myworkspace">
>     <wfs:Update typeName="MyWorkspace:MyLayer">
>         <wfs:Property>
>             <wfs:Name>Item_Name</wfs:Name>
>             <wfs:Value><![CDATA[Bob]]></wfs:Value>
>         </wfs:Property>
>         <!--other properties-->
>         <wfs:Property>
>             <wfs:Name>SHAPE</wfs:Name>
>             <wfs:Value>
>                 <gml:MultiSurface srsName='http://www.opengis.net/gml/srs/epsg.xml#4326'>
>                     <gml:surfaceMembers>
>                         <gml:Polygon>
>                             <gml:exterior>
>                                 <gml:LinearRing>
>                                     <gml:posList>-92.6834743019173 35.2264426107788 -92.6830394566101 35.2264555548522 -92.68301875 35.2266209299999 -92.6834852899999 35.22663787 -92.6834743019173 35.2264426107788</gml:posList>
>                                 </gml:LinearRing>
>                             </gml:exterior>
>                         </gml:Polygon>
>                         <gml:Polygon>
>                             <gml:exterior>
>                                 <gml:LinearRing>
>                                     <gml:posList>-92.6830420474193 35.2264347826591 -92.6827235345709 35.2264521083911 -92.68272353 35.2266102100001 -92.68301873 35.22662093 -92.6830420474193 35.2264347826591</gml:posList>
>                                 </gml:LinearRing>
>                             </gml:exterior>
>                         </gml:Polygon>
>                     </gml:surfaceMembers>
>                 </gml:MultiSurface>
>             </wfs:Value>
>         </wfs:Property>
>         <ogc:Filter>
>             <PropertyIsEqualTo>
>                 <PropertyName>OBJECTID</PropertyName>
>                 <Literal><![CDATA[100832369]]></Literal>
>             </PropertyIsEqualTo>
>         </ogc:Filter>
>     </wfs:Update>
> </wfs:Transaction>
>
>
>
>
>
> And here is what I feel is the relevant error logged in GeoServer:
>
> ERROR  [geoserver.wfs] - Transaction failed
> org.geoserver.wfs.WFSTransactionException: Update error: Error occured updating features
> ...
> Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: A .NET Framework error occurred during execution of user-defined routine or aggregate "geometry":
> System.FormatException: 24114: The label MULTISURFACE (((-92. in the input well-known text (WKT) is not valid. Valid labels are POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, GEOMETRYCOLLECTION, CIRCULARSTRING, COMPOUNDCURVE, CURVEPOLYGON and FULLGLOBE (geography Data Type only).
>
> Developer level logging shows the following "info" log:
>
>     INFO   [geoserver.wfs] -
> Request: transaction
>     service = WFS
>     version = 1.1.1
>     baseUrl = http://myurl:myport/geoserver/
>     group[0] = wfs:update=net.opengis.wfs.impl.UpdateElementTypeImpl@2f8c1c44 (filter: [[ OBJECTID = 100832369 ]], handle: null, inputFormat: <unset>, srsName: null, typeName: {http://myurl/myworkspace}mylayer)group[0] = wfs:delete=net.opengis.wfs.impl.DeleteElementTypeImpl@645e0daf (filter: [[ OBJECTID = 100832371 ]], handle: null, typeName: {http://myurl/myworkspace}mylayer)
>     update[0]:
>         property[0]:
>             ... several redacted properties and values ...
>             name = SHAPE
>             value = MULTIPOLYGON (((-92.6834743019173 35.2264426107788, -92.6830394566101 35.2264555548522, -92.68301875 35.2266209299999, -92.6834852899999 35.22663787, -92.6834743019173 35.2264426107788)), ((-92.6830420474193 35.2264347826591, -92.6827235345709 35.2264521083911, -92.68272353 35.2266102100001, -92.68301873 35.22662093, -92.6830420474193 35.2264347826591)))
>         filter = [[ OBJECTID = 100832369 ]]
>         inputFormat = x-application/gml:3
>         typeName = {http://myurl/myworkspace}mylayer
>     delete[0]:
>         filter = [[ OBJECTID = 100832371 ]]
>         typeName = {http://myurl/myworkspace}mylayer
>     releaseAction = ALL
> INFO   [geoserver.servlets] - OutputStream was successfully aborted.
>
> (Note, I am doing a delete in the same transaction here in this log which
> I'm not showing in the example transaction above, but it happens without it
> as well.)
>
> Very interesting that the geometry is already converted to multipolygon
> here. Not sure why it isn't hitting SQL as a multipolygon.
>
> I have tried altering the WFS version of the transaction and specifying
> GML version and even changing to explicitly using multipolygon instead of
> multisurface, but I'm to the point that I'm just shooting in the dark.
>
> This is a bit of a showstopper for us with the upgrade, so any help would
> be very much appreciated.
>
> Thanks,
> Matt
>
> _______________________________________________
> 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
>
>
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

[Geoserver-users] Unable to update GML Multisurface after GeoServer upgrade

[Matthew C. <mch...@da...>]

Sorry for the crosspost from GIS Stackexchange (https://gis.stackexchange.com/questions/483890/unable-to-update-gml-multisurface-after-geoserver-upgrade), but the conversation there fizzled out.

We are testing a (much needed) upgrade from GeoServer 2.17.2 to 2.25.1. We are currently stumped as to why we can't seem to be able to update or insert a multisurface using the same WFS transaction as with 2.17. I'm sure there is something simple we are missing here, so I'm hoping someone can point us in the right direction.
Here is an example transaction that is failing:

<wfs:Transaction service="WFS" version="1.1.1" xmlns:ogc="http://www.opengis.net/ogc" xmlns:wfs="http://www.opengis.net/wfs" xmlns:gml="http://www.opengis.net/gml" xmlns:MyWorkspace="http://mydomain.com/myworkspace">
    <wfs:Update typeName="MyWorkspace:MyLayer">
        <wfs:Property>
            <wfs:Name>Item_Name</wfs:Name>
            <wfs:Value><![CDATA[Bob]]></wfs:Value>
        </wfs:Property>
        <!--other properties-->
        <wfs:Property>
            <wfs:Name>SHAPE</wfs:Name>
            <wfs:Value>
                <gml:MultiSurface srsName='http://www.opengis.net/gml/srs/epsg.xml#4326'>
                    <gml:surfaceMembers>
                        <gml:Polygon>
                            <gml:exterior>
                                <gml:LinearRing>
                                    <gml:posList>-92.6834743019173 35.2264426107788 -92.6830394566101 35.2264555548522 -92.68301875 35.2266209299999 -92.6834852899999 35.22663787 -92.6834743019173 35.2264426107788</gml:posList>
                                </gml:LinearRing>
                            </gml:exterior>
                        </gml:Polygon>
                        <gml:Polygon>
                            <gml:exterior>
                                <gml:LinearRing>
                                    <gml:posList>-92.6830420474193 35.2264347826591 -92.6827235345709 35.2264521083911 -92.68272353 35.2266102100001 -92.68301873 35.22662093 -92.6830420474193 35.2264347826591</gml:posList>
                                </gml:LinearRing>
                            </gml:exterior>
                        </gml:Polygon>
                    </gml:surfaceMembers>
                </gml:MultiSurface>
            </wfs:Value>
        </wfs:Property>
        <ogc:Filter>
            <PropertyIsEqualTo>
                <PropertyName>OBJECTID</PropertyName>
                <Literal><![CDATA[100832369]]></Literal>
            </PropertyIsEqualTo>
        </ogc:Filter>
    </wfs:Update>
</wfs:Transaction>




And here is what I feel is the relevant error logged in GeoServer:


ERROR  [geoserver.wfs] - Transaction failed
org.geoserver.wfs.WFSTransactionException: Update error: Error occured updating features
...
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: A .NET Framework error occurred during execution of user-defined routine or aggregate "geometry":
System.FormatException: 24114: The label MULTISURFACE (((-92. in the input well-known text (WKT) is not valid. Valid labels are POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, GEOMETRYCOLLECTION, CIRCULARSTRING, COMPOUNDCURVE, CURVEPOLYGON and FULLGLOBE (geography Data Type only).

Developer level logging shows the following "info" log:


    INFO   [geoserver.wfs] -
Request: transaction
    service = WFS
    version = 1.1.1
    baseUrl = http://myurl:myport/geoserver/
    group[0] = wfs:update=net.opengis.wfs.impl.UpdateElementTypeImpl@2f8c1c44 (filter: [[ OBJECTID = 100832369 ]], handle: null, inputFormat: <unset>, srsName: null, typeName: {http://myurl/myworkspace}mylayer)group[0] = wfs:delete=net.opengis.wfs.impl.DeleteElementTypeImpl@645e0daf (filter: [[ OBJECTID = 100832371 ]], handle: null, typeName: {http://myurl/myworkspace}mylayer)
    update[0]:
        property[0]:
            ... several redacted properties and values ...
            name = SHAPE
            value = MULTIPOLYGON (((-92.6834743019173 35.2264426107788, -92.6830394566101 35.2264555548522, -92.68301875 35.2266209299999, -92.6834852899999 35.22663787, -92.6834743019173 35.2264426107788)), ((-92.6830420474193 35.2264347826591, -92.6827235345709 35.2264521083911, -92.68272353 35.2266102100001, -92.68301873 35.22662093, -92.6830420474193 35.2264347826591)))
        filter = [[ OBJECTID = 100832369 ]]
        inputFormat = x-application/gml:3
        typeName = {http://myurl/myworkspace}mylayer
    delete[0]:
        filter = [[ OBJECTID = 100832371 ]]
        typeName = {http://myurl/myworkspace}mylayer
    releaseAction = ALL
INFO   [geoserver.servlets] - OutputStream was successfully aborted.

(Note, I am doing a delete in the same transaction here in this log which I'm not showing in the example transaction above, but it happens without it as well.)

Very interesting that the geometry is already converted to multipolygon here. Not sure why it isn't hitting SQL as a multipolygon.

I have tried altering the WFS version of the transaction and specifying GML version and even changing to explicitly using multipolygon instead of multisurface, but I'm to the point that I'm just shooting in the dark.

This is a bit of a showstopper for us with the upgrade, so any help would be very much appreciated.

Thanks,
Matt

[Geoserver-users] GeoServer User Forum replaces geoserver-users mailing list

[Jody G. <jod...@gm...>]

GeoServer is updating our communication channels!

GeoServer User forum <https://discourse.osgeo.org/c/geoserver/user/51>:

   - Public forum, sign in with credentials you already have.
   - Search works, includes the complete mailing list history since 2004
   - Optional: Configure email notification to use as
   geo...@di... mailing-list


Community Support <https://geoserver.org/comm/> has instructions for how to
sign-in, and optional use as a mailing list.

The SourceForge mailing-list will be archived at the end of August. We will
transfer any received email to the forum at that time. For more information
see GSIP-225 <https://github.com/geoserver/geoserver/wiki/GSIP-225>.
- -
Jody Garnett

Re: [Geoserver-users] SLD Variable Replacement For Legend Entry Label

[Jody G. <jod...@gm...>]

 To work without code changes, perhaps use concatenate function to combine
"Less than ", with your other expressions ..

<ColorMapEntry ... label="${Concatenate('Less than ',env('valuea', 15},' to
> ',env('valueb', 25))" />
>


- -
Jody Garnett


On Jul 31, 2024 at 8:17:50 AM, Andrew Orzechowski <
and...@gm...> wrote:

> In an SLD style for my raster layer, I am able to utilize variable
> replacement to customize the label for a particular entry.  For example:
>
> <ColorMapEntry ... label="${env('value', 15)}" />
>
> This also works when I have multiple values, such as:
>
> <ColorMapEntry ... label="${env('valuea', 15} to ${env('valueb', 25)}" />
>
> However, if I have text in front of the substation it does not work, such
> as:
>
> <ColorMapEntry ... label="Less than ${env('value', 15)}" />
>
> Is this the desired behavior or a bug?  Or is there another way I should
> be doing this?
>
> If it is a bug, it appears that this behavior could be corrected by
> replacing "labelString.startsWith" with "labelString.contains" in
> LegendUtils::getLabel and enhancing the unit test to cover this 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
>
>
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

Re: [Geoserver-users] GeoServer questions

[Jody G. <jod...@gm...>]

 There may be a community module:
https://docs.geoserver.org/2.25.x/en/user/community/elasticsearch/index.html

In general cloud based datastore have trouble being supported as extensions
- as someone would need to pay for the service for automated tests to be
verified against.

The community module above is shared as source code only, not included in
our release process.

That said you can try out some community modules as nightly builds in order
to provide testing and feedback for our developers.

Using Docker:

docker run -it -p8080:8080 \
  --env INSTALL_EXTENSIONS=true \
  --env STABLE_EXTENSIONS="ysld,h2" \
  --env COMMUNITY_EXTENSIONS="elasticsearch" \
  docker.osgeo.org/geoserver:2.25.x

If you are interested in production use of Elasticsearch this is good
example of where sponsorship or commercial support can assist.
--
Jody Garnett


On Jul 31, 2024 at 1:18:37 PM, Jim Rogers <Jim...@bo...> wrote:

> Is there a plugin available to connect GeoServer with Elasticsearch?
>
>
>
> Thanks,
>
> Jim Rogers
>
>
>
> *From:* Jody Garnett <jod...@gm...>
> *Sent:* Tuesday, July 2, 2024 5:39 PM
> *To:* Jim Rogers <Jim...@bo...>
> *Cc:* Vagicherla, Vineela CTR DIA (US) <vin...@do...>;
> geo...@li...
> *Subject:* Re: [Geoserver-users] GeoServer questions
>
>
>
> *This email was sent from an external server*
>
> Jim I think both of those topics are covered in the use manual user
> getting started section.
>
>
>
> Can you let me know what have tried thus far?
>
> --
>
> Jody Garnett
>
>
>
>
>
> On Tue, Jul 2, 2024 at 12:12 PM Jim Rogers <Jim...@bo...> wrote:
>
> Would it be possible to provide instructions on how to set up a direct
> connection from out database to GeoServer?
>
>
>
> Also, how can we create OGC web services?
>
>
>
> Thanks,
>
> Jim Rogers
>
> _______________________________________________
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ianturton.com_talks_foss4g.html-23_&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=64rOp_q_edj6FGjJwENH7LCm8WCfU__224g7-07KUSY&m=uMQ1fmqLpWEDCpb5q3yHTvbMldqnAk5ixj2uAnEIfV1sItPEJ6nxW4jAaHNi6tV8&s=PgdCHamLHwyjZvtclAM6_515M518-uw9oI4TD4Ob4NE&e=>
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__geoserver.org_comm_userlist-2Dguidelines.html&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=64rOp_q_edj6FGjJwENH7LCm8WCfU__224g7-07KUSY&m=uMQ1fmqLpWEDCpb5q3yHTvbMldqnAk5ixj2uAnEIfV1sItPEJ6nxW4jAaHNi6tV8&s=2mMT0OcYE0VgebqWN9ZOauUwJPuMwArxJAYOIs2yOps&e=>
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_geoserver_geoserver_wiki_Successfully-2Drequesting-2Dand-2Dintegrating-2Dnew-2Dfeatures-2Dand-2Dimprovements-2Din-2DGeoServer&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=64rOp_q_edj6FGjJwENH7LCm8WCfU__224g7-07KUSY&m=uMQ1fmqLpWEDCpb5q3yHTvbMldqnAk5ixj2uAnEIfV1sItPEJ6nxW4jAaHNi6tV8&s=3ogBc2vEcZAlS2wqoVeBx-ArG7PVUndCaV0FopEEYXE&e=>
>
>
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_geoserver-2Dusers&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=64rOp_q_edj6FGjJwENH7LCm8WCfU__224g7-07KUSY&m=uMQ1fmqLpWEDCpb5q3yHTvbMldqnAk5ixj2uAnEIfV1sItPEJ6nxW4jAaHNi6tV8&s=bSjQ6lwIDCU8iEpmqgHBS5he8F-GiIm71Am26ZMVEXQ&e=>
>
>
> ------------------------------
>
> This email has been scanned for spam and viruses by Proofpoint Essentials.
> Click here
> <https://us3.proofpointessentials.com/app/report_spam.php?mod_id=11&mod_option=logitem&report=1&type=easyspam&k=k1&payload=53616c7465645f5f7c50abca8f9e625c02ac23833d1c18c35e11de3f4bd0e4607475e2198b33467ac1d4b8d7a5ca788152b716f6d3dad38de9b1f93b48d8d9aab465ef3adb3ad702d136b3440cff4b95b825b22de81802d615038ee58da64b10a098b10f538daf90b6ff6382af2d72def64532de0d4cf5a82d78f2caab7d84d041121a128bba24c818bccfbe85dcd5ed11208616b41cb0e755ded7c8338f7584>
> to report this email as spam.
>

Re: [Geoserver-users] GeoServer questions

[Jim R. <Jim...@bo...>]

Is there a plugin available to connect GeoServer with Elasticsearch?

Thanks,
Jim Rogers

From: Jody Garnett <jod...@gm...>
Sent: Tuesday, July 2, 2024 5:39 PM
To: Jim Rogers <Jim...@bo...>
Cc: Vagicherla, Vineela CTR DIA (US) <vin...@do...>; geo...@li...
Subject: Re: [Geoserver-users] GeoServer questions

This email was sent from an external server
Jim I think both of those topics are covered in the use manual user getting started section.

Can you let me know what have tried thus far?
--
Jody Garnett


On Tue, Jul 2, 2024 at 12:12 PM Jim Rogers <Jim...@bo...<mailto:Jim...@bo...>> wrote:
Would it be possible to provide instructions on how to set up a direct connection from out database to GeoServer?

Also, how can we create OGC web services?

Thanks,
Jim Rogers
_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:
- Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ianturton.com_talks_foss4g.html-23_&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=64rOp_q_edj6FGjJwENH7LCm8WCfU__224g7-07KUSY&m=uMQ1fmqLpWEDCpb5q3yHTvbMldqnAk5ixj2uAnEIfV1sItPEJ6nxW4jAaHNi6tV8&s=PgdCHamLHwyjZvtclAM6_515M518-uw9oI4TD4Ob4NE&e=>
- The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__geoserver.org_comm_userlist-2Dguidelines.html&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=64rOp_q_edj6FGjJwENH7LCm8WCfU__224g7-07KUSY&m=uMQ1fmqLpWEDCpb5q3yHTvbMldqnAk5ixj2uAnEIfV1sItPEJ6nxW4jAaHNi6tV8&s=2mMT0OcYE0VgebqWN9ZOauUwJPuMwArxJAYOIs2yOps&e=>

If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_geoserver_geoserver_wiki_Successfully-2Drequesting-2Dand-2Dintegrating-2Dnew-2Dfeatures-2Dand-2Dimprovements-2Din-2DGeoServer&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=64rOp_q_edj6FGjJwENH7LCm8WCfU__224g7-07KUSY&m=uMQ1fmqLpWEDCpb5q3yHTvbMldqnAk5ixj2uAnEIfV1sItPEJ6nxW4jAaHNi6tV8&s=3ogBc2vEcZAlS2wqoVeBx-ArG7PVUndCaV0FopEEYXE&e=>


Geo...@li...<mailto:Geo...@li...>
https://lists.sourceforge.net/lists/listinfo/geoserver-users<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_geoserver-2Dusers&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=64rOp_q_edj6FGjJwENH7LCm8WCfU__224g7-07KUSY&m=uMQ1fmqLpWEDCpb5q3yHTvbMldqnAk5ixj2uAnEIfV1sItPEJ6nxW4jAaHNi6tV8&s=bSjQ6lwIDCU8iEpmqgHBS5he8F-GiIm71Am26ZMVEXQ&e=>



________________________________

This email has been scanned for spam and viruses by Proofpoint Essentials. Click here<https://us3.proofpointessentials.com/app/report_spam.php?mod_id=11&mod_option=logitem&report=1&type=easyspam&k=k1&payload=53616c7465645f5f7c50abca8f9e625c02ac23833d1c18c35e11de3f4bd0e4607475e2198b33467ac1d4b8d7a5ca788152b716f6d3dad38de9b1f93b48d8d9aab465ef3adb3ad702d136b3440cff4b95b825b22de81802d615038ee58da64b10a098b10f538daf90b6ff6382af2d72def64532de0d4cf5a82d78f2caab7d84d041121a128bba24c818bccfbe85dcd5ed11208616b41cb0e755ded7c8338f7584> to report this email as spam.

[Geoserver-users] SLD Variable Replacement For Legend Entry Label

[Andrew O. <and...@gm...>]

In an SLD style for my raster layer, I am able to utilize variable
replacement to customize the label for a particular entry.  For example:

<ColorMapEntry ... label="${env('value', 15)}" />

This also works when I have multiple values, such as:

<ColorMapEntry ... label="${env('valuea', 15} to ${env('valueb', 25)}" />

However, if I have text in front of the substation it does not work, such
as:

<ColorMapEntry ... label="Less than ${env('value', 15)}" />

Is this the desired behavior or a bug?  Or is there another way I should be
doing this?

If it is a bug, it appears that this behavior could be corrected by
replacing "labelString.startsWith" with "labelString.contains" in
LegendUtils::getLabel and enhancing the unit test to cover this case.

[Geoserver-users] Note: GeoServer Docker Image Changes

[Nils B. <bu...@te...>]

Hi all,

last friday we merged a bigger change in the Docker Image repository: 
https://github.com/geoserver/docker/pull/45

This changes the base image, so we now use the official tomcat docker 
image as a base instead of installing tomcat ourselves. We succesfully 
tested all the functionality that the GeoServer image provides. 
Nonetheless - with the next GeoServer release (which also results in a 
new docker image) - minor adjustments might be necessary in your scenario.

Please note: The main change is the internal tomcat path. Previously it 
was something like (containing the tomcat version) 
"/opt/apache-tomcat-9.0.89". In future it will always be the same 
generic path "/usr/local/tomcat/" (as provided by the tomcat base 
image), which means: In case you use mounts to directories within the 
tomcat path, you will have to adjust them!

The current versions of GeoServer (2.25.3/2.24.4) were still built with 
the old approach, but all future releases will be built with the new 
base image.

Please let us know here if you encounter unexpected problems.

Best regards
Nils

[Geoserver-users] WPS Demo panel functionality in 2.24.4

[Alexander P. <gre...@gm...>]

After upgrade to 2.24.4, WPS requests made via the Demo panel do not
complete...

Anyone else experienced this?

Command line submissions work.

Thanks in advance!

Alex

[Geoserver-users] GeoServer 2.25, 3 is now available for download and upgrades

[Ian T. <ijt...@gm...>]

Please read the release announcement at
https://geoserver.org/announcements/2024/07/18/geoserver-2-25-3-released.html
to see what changes have been made.

-- 
Ian Turton

Re: [Geoserver-users] Problems with image mosaic data store

[Ville K. <vil...@ub...>]

Hi,

Thanks for the reply! I hadn't done that. I tried disabling URL check
altogether for the moment and it didn't help. I guess that rules out URL
checks?

Br,
Ville Koivisto

On Thu, Jul 18, 2024 at 8:01 PM Alexandre Gacon <ale...@gm...>
wrote:

> Have you configured the URL checks to allow access to the file://path
> described?
>
> Le jeu. 18 juil. 2024 à 18:56, Ville Koivisto via Geoserver-users <
> geo...@li...> a écrit :
>
>> Hi list,
>>
>> I'm having issues with all my image mosaic data stores which all present
>> the same error. This has come to be after updating geoserver to latest
>> version 2.25.2. Maybe someone has some pointers that could help? I omitted
>> file paths.
>>
>> <?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE
>> ServiceExceptionReport SYSTEM "
>> https://georaster.tampere.fi/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd">
>> <ServiceExceptionReport version="1.1.1" > <ServiceException>
>> java.io.IOException: Failed to create reader from file:///path and hints
>> Hints: FORCE_LONGITUDE_FIRST_AXIS_ORDER = true COMPARISON_TOLERANCE =
>> 1.0E-8 LENIENT_DATUM_SHIFT = true REPOSITORY =
>> org.geoserver.catalog.CatalogRepository@31c09115 FILTER_FACTORY =
>> FilterFactoryImpl FORCE_AXIS_ORDER_HONORING = http STYLE_FACTORY =
>> org.geotools.styling.StyleFactoryImpl@c582c32 EXECUTOR_SERVICE =
>> java.util.concurrent.ThreadPoolExecutor@3d4c069a[Running, pool size = 0,
>> active threads = 0, queued tasks = 0, completed tasks = 0] FEATURE_FACTORY
>> = org.geotools.feature.LenientFeatureFactoryImpl@463a4521
>> GRID_COVERAGE_FACTORY = GridCoverageFactory TILE_ENCODING = null Failed to
>> create reader from file:/// path and hints Hints:
>> FORCE_LONGITUDE_FIRST_AXIS_ORDER = true COMPARISON_TOLERANCE = 1.0E-8
>> LENIENT_DATUM_SHIFT = true REPOSITORY =
>> org.geoserver.catalog.CatalogRepository@31c09115 FILTER_FACTORY =
>> FilterFactoryImpl FORCE_AXIS_ORDER_HONORING = http STYLE_FACTORY =
>> org.geotools.styling.StyleFactoryImpl@c582c32 EXECUTOR_SERVICE =
>> java.util.concurrent.ThreadPoolExecutor@3d4c069a[Running, pool size = 0,
>> active threads = 0, queued tasks = 0, completed tasks = 0] FEATURE_FACTORY
>> = org.geotools.feature.LenientFeatureFactoryImpl@463a4521
>> GRID_COVERAGE_FACTORY = GridCoverageFactory TILE_ENCODING = null
>> </ServiceException></ServiceExceptionReport>
>>
>>
>> Best regards,
>> Ville Koivisto
>>
>>
>>
>> Ubigu Oy | Ltd
>> *Paikkatietoyhteiskunnan rakentajat | Builders of a spatial information
>> society*
>> Pellavatehtaankatu 8 E 59, FI-33100 Tampere
>> Linkedin <https://www.linkedin.com/company/ubigu-oy/> | Twitter
>> <https://twitter.com/ubigusto>
>> _______________________________________________
>> 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
>>
>>
>> Geo...@li...
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>

-- 

***  *
Ubigu Oy | Ltd
_Paikkatietoyhteiskunnan rakentajat | Builders of a 
spatial information society_
__
Pellavatehtaankatu 8 E 59, FI-33100 Tampere
Linkedin <https://www.linkedin.com/company/ubigu-oy/> | Twitter 
<https://twitter.com/ubigusto>

Re: [Geoserver-users] Problems with image mosaic data store

[Ville K. <vil...@ub...>]

Hi Andrea and others,

Thank you again for the message. I manually removed the index file, sample
data and properties file and allowed geoserver to create them from scratch.
This worked. It seems there were some breaking (?) changes in that between
the versions. Would be nice to figure out what, but I reckon I can just
check changelogs.

Thank you again!

Br,
Ville Koivisto

On Thu, Jul 18, 2024 at 9:40 PM Andrea Aime <
and...@ge...> wrote:

> Suggestion: set the logging level to "Geotools developer logging" and save
> the store again. The read the logs generated by that action, you should
> find the reason in there. If not, save and share here.
>
> Cheers
> Andrea
>
> Il gio 18 lug 2024, 18:57 Ville Koivisto via Geoserver-users <
> geo...@li...> ha scritto:
>
>> Hi list,
>>
>> I'm having issues with all my image mosaic data stores which all present
>> the same error. This has come to be after updating geoserver to latest
>> version 2.25.2. Maybe someone has some pointers that could help? I omitted
>> file paths.
>>
>> <?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE
>> ServiceExceptionReport SYSTEM "
>> https://georaster.tampere.fi/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd">
>> <ServiceExceptionReport version="1.1.1" > <ServiceException>
>> java.io.IOException: Failed to create reader from file:///path and hints
>> Hints: FORCE_LONGITUDE_FIRST_AXIS_ORDER = true COMPARISON_TOLERANCE =
>> 1.0E-8 LENIENT_DATUM_SHIFT = true REPOSITORY =
>> org.geoserver.catalog.CatalogRepository@31c09115 FILTER_FACTORY =
>> FilterFactoryImpl FORCE_AXIS_ORDER_HONORING = http STYLE_FACTORY =
>> org.geotools.styling.StyleFactoryImpl@c582c32 EXECUTOR_SERVICE =
>> java.util.concurrent.ThreadPoolExecutor@3d4c069a[Running, pool size = 0,
>> active threads = 0, queued tasks = 0, completed tasks = 0] FEATURE_FACTORY
>> = org.geotools.feature.LenientFeatureFactoryImpl@463a4521
>> GRID_COVERAGE_FACTORY = GridCoverageFactory TILE_ENCODING = null Failed to
>> create reader from file:/// path and hints Hints:
>> FORCE_LONGITUDE_FIRST_AXIS_ORDER = true COMPARISON_TOLERANCE = 1.0E-8
>> LENIENT_DATUM_SHIFT = true REPOSITORY =
>> org.geoserver.catalog.CatalogRepository@31c09115 FILTER_FACTORY =
>> FilterFactoryImpl FORCE_AXIS_ORDER_HONORING = http STYLE_FACTORY =
>> org.geotools.styling.StyleFactoryImpl@c582c32 EXECUTOR_SERVICE =
>> java.util.concurrent.ThreadPoolExecutor@3d4c069a[Running, pool size = 0,
>> active threads = 0, queued tasks = 0, completed tasks = 0] FEATURE_FACTORY
>> = org.geotools.feature.LenientFeatureFactoryImpl@463a4521
>> GRID_COVERAGE_FACTORY = GridCoverageFactory TILE_ENCODING = null
>> </ServiceException></ServiceExceptionReport>
>>
>>
>> Best regards,
>> Ville Koivisto
>>
>>
>>
>> Ubigu Oy | Ltd
>> *Paikkatietoyhteiskunnan rakentajat | Builders of a spatial information
>> society*
>> Pellavatehtaankatu 8 E 59, FI-33100 Tampere
>> Linkedin <https://www.linkedin.com/company/ubigu-oy/> | Twitter
>> <https://twitter.com/ubigusto>
>> _______________________________________________
>> 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
>>
>>
>> Geo...@li...
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>

-- 

***  *
Ubigu Oy | Ltd
_Paikkatietoyhteiskunnan rakentajat | Builders of a 
spatial information society_
__
Pellavatehtaankatu 8 E 59, FI-33100 Tampere
Linkedin <https://www.linkedin.com/company/ubigu-oy/> | Twitter 
<https://twitter.com/ubigusto>

Re: [Geoserver-users] Problems with image mosaic data store

[Andrea A. <and...@ge...>]

Suggestion: set the logging level to "Geotools developer logging" and save
the store again. The read the logs generated by that action, you should
find the reason in there. If not, save and share here.

Cheers
Andrea

Il gio 18 lug 2024, 18:57 Ville Koivisto via Geoserver-users <
geo...@li...> ha scritto:

> Hi list,
>
> I'm having issues with all my image mosaic data stores which all present
> the same error. This has come to be after updating geoserver to latest
> version 2.25.2. Maybe someone has some pointers that could help? I omitted
> file paths.
>
> <?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE
> ServiceExceptionReport SYSTEM "
> https://georaster.tampere.fi/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd">
> <ServiceExceptionReport version="1.1.1" > <ServiceException>
> java.io.IOException: Failed to create reader from file:///path and hints
> Hints: FORCE_LONGITUDE_FIRST_AXIS_ORDER = true COMPARISON_TOLERANCE =
> 1.0E-8 LENIENT_DATUM_SHIFT = true REPOSITORY =
> org.geoserver.catalog.CatalogRepository@31c09115 FILTER_FACTORY =
> FilterFactoryImpl FORCE_AXIS_ORDER_HONORING = http STYLE_FACTORY =
> org.geotools.styling.StyleFactoryImpl@c582c32 EXECUTOR_SERVICE =
> java.util.concurrent.ThreadPoolExecutor@3d4c069a[Running, pool size = 0,
> active threads = 0, queued tasks = 0, completed tasks = 0] FEATURE_FACTORY
> = org.geotools.feature.LenientFeatureFactoryImpl@463a4521
> GRID_COVERAGE_FACTORY = GridCoverageFactory TILE_ENCODING = null Failed to
> create reader from file:/// path and hints Hints:
> FORCE_LONGITUDE_FIRST_AXIS_ORDER = true COMPARISON_TOLERANCE = 1.0E-8
> LENIENT_DATUM_SHIFT = true REPOSITORY =
> org.geoserver.catalog.CatalogRepository@31c09115 FILTER_FACTORY =
> FilterFactoryImpl FORCE_AXIS_ORDER_HONORING = http STYLE_FACTORY =
> org.geotools.styling.StyleFactoryImpl@c582c32 EXECUTOR_SERVICE =
> java.util.concurrent.ThreadPoolExecutor@3d4c069a[Running, pool size = 0,
> active threads = 0, queued tasks = 0, completed tasks = 0] FEATURE_FACTORY
> = org.geotools.feature.LenientFeatureFactoryImpl@463a4521
> GRID_COVERAGE_FACTORY = GridCoverageFactory TILE_ENCODING = null
> </ServiceException></ServiceExceptionReport>
>
>
> Best regards,
> Ville Koivisto
>
>
>
> Ubigu Oy | Ltd
> *Paikkatietoyhteiskunnan rakentajat | Builders of a spatial information
> society*
> Pellavatehtaankatu 8 E 59, FI-33100 Tampere
> Linkedin <https://www.linkedin.com/company/ubigu-oy/> | Twitter
> <https://twitter.com/ubigusto>
> _______________________________________________
> 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
>
>
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

Re: [Geoserver-users] Problems with image mosaic data store

[Alexandre G. <ale...@gm...>]

Have you configured the URL checks to allow access to the file://path
described?

Le jeu. 18 juil. 2024 à 18:56, Ville Koivisto via Geoserver-users <
geo...@li...> a écrit :

> Hi list,
>
> I'm having issues with all my image mosaic data stores which all present
> the same error. This has come to be after updating geoserver to latest
> version 2.25.2. Maybe someone has some pointers that could help? I omitted
> file paths.
>
> <?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE
> ServiceExceptionReport SYSTEM "
> https://georaster.tampere.fi/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd">
> <ServiceExceptionReport version="1.1.1" > <ServiceException>
> java.io.IOException: Failed to create reader from file:///path and hints
> Hints: FORCE_LONGITUDE_FIRST_AXIS_ORDER = true COMPARISON_TOLERANCE =
> 1.0E-8 LENIENT_DATUM_SHIFT = true REPOSITORY =
> org.geoserver.catalog.CatalogRepository@31c09115 FILTER_FACTORY =
> FilterFactoryImpl FORCE_AXIS_ORDER_HONORING = http STYLE_FACTORY =
> org.geotools.styling.StyleFactoryImpl@c582c32 EXECUTOR_SERVICE =
> java.util.concurrent.ThreadPoolExecutor@3d4c069a[Running, pool size = 0,
> active threads = 0, queued tasks = 0, completed tasks = 0] FEATURE_FACTORY
> = org.geotools.feature.LenientFeatureFactoryImpl@463a4521
> GRID_COVERAGE_FACTORY = GridCoverageFactory TILE_ENCODING = null Failed to
> create reader from file:/// path and hints Hints:
> FORCE_LONGITUDE_FIRST_AXIS_ORDER = true COMPARISON_TOLERANCE = 1.0E-8
> LENIENT_DATUM_SHIFT = true REPOSITORY =
> org.geoserver.catalog.CatalogRepository@31c09115 FILTER_FACTORY =
> FilterFactoryImpl FORCE_AXIS_ORDER_HONORING = http STYLE_FACTORY =
> org.geotools.styling.StyleFactoryImpl@c582c32 EXECUTOR_SERVICE =
> java.util.concurrent.ThreadPoolExecutor@3d4c069a[Running, pool size = 0,
> active threads = 0, queued tasks = 0, completed tasks = 0] FEATURE_FACTORY
> = org.geotools.feature.LenientFeatureFactoryImpl@463a4521
> GRID_COVERAGE_FACTORY = GridCoverageFactory TILE_ENCODING = null
> </ServiceException></ServiceExceptionReport>
>
>
> Best regards,
> Ville Koivisto
>
>
>
> Ubigu Oy | Ltd
> *Paikkatietoyhteiskunnan rakentajat | Builders of a spatial information
> society*
> Pellavatehtaankatu 8 E 59, FI-33100 Tampere
> Linkedin <https://www.linkedin.com/company/ubigu-oy/> | Twitter
> <https://twitter.com/ubigusto>
> _______________________________________________
> 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
>
>
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

[Geoserver-users] Problems with image mosaic data store

[Ville K. <vil...@ub...>]

Hi list,

I'm having issues with all my image mosaic data stores which all present
the same error. This has come to be after updating geoserver to latest
version 2.25.2. Maybe someone has some pointers that could help? I omitted
file paths.

<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE
ServiceExceptionReport SYSTEM "
https://georaster.tampere.fi/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd">
<ServiceExceptionReport version="1.1.1" > <ServiceException>
java.io.IOException: Failed to create reader from file:///path and hints
Hints: FORCE_LONGITUDE_FIRST_AXIS_ORDER = true COMPARISON_TOLERANCE =
1.0E-8 LENIENT_DATUM_SHIFT = true REPOSITORY =
org.geoserver.catalog.CatalogRepository@31c09115 FILTER_FACTORY =
FilterFactoryImpl FORCE_AXIS_ORDER_HONORING = http STYLE_FACTORY =
org.geotools.styling.StyleFactoryImpl@c582c32 EXECUTOR_SERVICE =
java.util.concurrent.ThreadPoolExecutor@3d4c069a[Running, pool size = 0,
active threads = 0, queued tasks = 0, completed tasks = 0] FEATURE_FACTORY
= org.geotools.feature.LenientFeatureFactoryImpl@463a4521
GRID_COVERAGE_FACTORY = GridCoverageFactory TILE_ENCODING = null Failed to
create reader from file:/// path and hints Hints:
FORCE_LONGITUDE_FIRST_AXIS_ORDER = true COMPARISON_TOLERANCE = 1.0E-8
LENIENT_DATUM_SHIFT = true REPOSITORY =
org.geoserver.catalog.CatalogRepository@31c09115 FILTER_FACTORY =
FilterFactoryImpl FORCE_AXIS_ORDER_HONORING = http STYLE_FACTORY =
org.geotools.styling.StyleFactoryImpl@c582c32 EXECUTOR_SERVICE =
java.util.concurrent.ThreadPoolExecutor@3d4c069a[Running, pool size = 0,
active threads = 0, queued tasks = 0, completed tasks = 0] FEATURE_FACTORY
= org.geotools.feature.LenientFeatureFactoryImpl@463a4521
GRID_COVERAGE_FACTORY = GridCoverageFactory TILE_ENCODING = null
</ServiceException></ServiceExceptionReport>


Best regards,
Ville Koivisto

-- 

***  *
Ubigu Oy | Ltd
_Paikkatietoyhteiskunnan rakentajat | Builders of a 
spatial information society_
__
Pellavatehtaankatu 8 E 59, FI-33100 Tampere
Linkedin <https://www.linkedin.com/company/ubigu-oy/> | Twitter 
<https://twitter.com/ubigusto>

Re: [Geoserver-users] Release mapfish print v2

[Tiago V. <tix...@gm...>]

Hi Jody,

Please tell us when you release a new mapfish print version, for me to do
the rest on the geoserver side.

Thanks

*Tiago Vieira*


On Tue, 9 Jul 2024 at 03:17, Phil Scadden <P.S...@gn...> wrote:

> I do get my google tiles directly from google in approved way (and pay for
> them).  That is why I am more interested in a mapfish server managing all
> sorts of protocols rather that one tied to geoserver.  I am using leaflet
> as client and mixing and matching from all over the show. The big issue
> with esri vector tiles (which have sadly become very popular) is that the
> leaflet plugin can only handle web Mercator. I looked the issue and messy.
> I will look at geotools code and think about it some more.
>
>
>
> *From:* Jody Garnett <jod...@gm...>
> *Sent:* Tuesday, July 9, 2024 12:30 PM
> *To:* Phil Scadden <P.S...@gn...>
> *Cc:* geo...@li...
> *Subject:* Re: [Geoserver-users] Release mapfish print v2
>
>
>
>
>
> *CAUTION:* This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe:
>
> So you know that use of google tiles is not a thing we are supposed to do
> right? They really want you to use their javascript api - so that the tiles
> can be paid for (by your application user's privacy...).  There all kinds
> of technical ways around this of course, but ethical ways around it are
> suspect ...
>
>
>
> We have all kinds of code for messing with data if you wish to take on
> vector tiles. I think there is even something that reads them, and
> retrojects them for geowebcache, so it is all within reach if you want to
> play.
>
>
>
> Still the origional motivator that paid for printing (and thus PDF output
> also) was parties that had a regulated requirement to output paper maps at
> specific scales. I think we have moved beyond that now 🙂
>
>
> --
>
> Jody Garnett
>
>
>
>
>
> On Jul 8, 2024 at 3:23:46 PM, Phil Scadden <P.S...@gn...> wrote:
>
> For my 2c, I was excited when heard about mapfish a decade or so ago, but
> quickly lost interest because it lacked support for google tiles. If more
> map layers were supported, then I suspect there would be more interest. I
> have users of my webmaps (which depend on slightly better than browser
> screenshots) asking for higher res imagery. Layer support was the achilles
> heel. Better support for ESRI services and vector tiles would be needed for
> it to be really interesting. Since virtually all my webmapping deals with
> layers from multiple services, not just geoserver, a mapfish server that is
> only operating on a single geoserver instance is less interesting.
>
>
>
> *From:* Tiago Vieira <tix...@gm...>
> *Sent:* Tuesday, July 9, 2024 4:23 AM
> *To:* Jody Garnett <jod...@gm...>
> *Cc:* geo...@li...
> *Subject:* Re: [Geoserver-users] Release mapfish print v2
>
>
>
>
>
> *CAUTION:* This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe:
>
> 😀
>
>
>
> So, as far as I understand you are suggesting to bring the mapfish print
> to the community module of geoserver?
>
> Is it considered a community module or extension? Because it's on the
> extensions download page of geoserver. (
> https://geoserver.org/release/stable/ --> Cartography)
>
>
>
> I can give it a try on doing that.
>
>
>
> *Tiago Vieira*
>
>
>
>
>
> On Mon, 8 Jul 2024 at 15:59, Jody Garnett <jod...@gm...> wrote:
>
> I have nothing against the printing plugin - just that it needs some love
> 🙂
>
>
>
> What would be the best way to support this thing? If it is only the
> geoserver project using mapfish printv2 then the geoserver community should
> come up with a plan ... so I was presenting some plans :P​
>
>
>
> If you are making pull-requests then you have some technical capacity so
> you are *exactly* who we want to make plans with....
>
> --
>
> Jody Garnett
>
>
>
>
>
> On Jul 8, 2024 at 12:57:05 AM, Tiago Vieira <tix...@gm...> wrote:
>
> Hi Jody,
>
>
>
> This is the project that supports the "Printing" extension in geoserver,
> right?
>
> I don't know if many people use it, but in our project we use this
> printing plugin a long time ago :)
>
>
>
> Is there any alternative to have a vectorial print? And also, with this
> printv2 we are able to print maps with google maps tiles included.
>
>
>
> I think the functionality of naming the PDF Layers is essential, so an
> end-user will be able to have a human readable translation, instead of
> internal layer names.
>
>
>
> Thanks,
>
> *Tiago Vieira*
>
>
>
>
>
> On Mon, 8 Jul 2024 at 01:05, Jody Garnett <jod...@gm...> wrote:
>
> I have commit access; but really this project ended a long time ago.
>
>
>
> So you know of people who are interested in this functionality? It would
> be good to assemble an activity to update / migrate / or inokement
> something comparable in geotools.
>
> --
>
> Jody Garnett
>
>
>
>
>
> On Sun, Jul 7, 2024 at 1:04 PM Tiago Vieira <tix...@gm...> wrote:
>
> Hi,
>
>
>
> I don't know if this is the right mailing list to use, but do you know who
> can review the 3 PR in the mapfish print v2 github, and do a new release to
> upgrade the extensions of a next geoserver version.
>
> https://github.com/mapfish/mapfish-print-v2/pulls
>
>
>
>
>
> 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
>
>
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
> 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
>
>
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
> 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
>
>
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

Re: [Geoserver-users] GeoServer works fine with Apache Tomcat 10

[Jody G. <jod...@gm...>]

Please see this blog post:
https://geoserver.org/behind%20the%20scenes/2024/01/03/roadmap.html

We have not had sufficient response to stay on this with, but dinner of the
early stepping stones are ready for volunteers and funding.

--
Jody Garnett


On Wed, Jul 17, 2024 at 4:03 AM Carsten Klein <c....@da...> wrote:

> Hello there,
>
> I haven't found much on the mailing lists about GeoServer and Apache
> Tomcat 10, which already uses new Jakarte Servlet Specification 5.0 (using
> jakarta.servlet.* package names) so, you may find this post quite
> interesting.
>
> Since I'm using a new Ubuntu Server 24.04 LTS, which has actually dropped
> Tomcat 9.0 (and I didn't want to use a manually installed Tomcat 9.0 in
> /opt/tomcat), I've figured out a quite nice solution. The Apache Tomcat
> team has build a  tool named "Tomcat Migration Tool for Jakarta EE", which
> is able to transform compiled Java classes from old javax.servlet names to
> new jakarta.servlet package names. It can process whole WAR files,
> directories of JAR files as well as single class files.
>
> https://github.com/apache/tomcat-jakartaee-migration
>
> This tool is also available on Debian, Ubuntu and Fedora systems by
> installing the tomcat-jakartaee-migration package and invoking the
> javax2jakarta command.
>
> After having processed GeoServer's WEB-INF/lib directory with that tool,
> GeoServer 2.25.2 started within Apache Tomcat Server with no issues logged.
> Additionally, at first glance, GeoServer seems to *work* without issues as
> well. Thumbs up!
>
> The migration tool has been written in Java so, you should even be able to
> integrate it into GeoServer's build processes in order to produce a
> additional download packages compatible with Jakarta Servlet Specification
> 5.0 (jakarta.servlet.*).
>
> Cheers
> Carsten
> _______________________________________________
> 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
>
>
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

[Geoserver-users] GeoServer works fine with Apache Tomcat 10

[Carsten K. <c....@da...>]

Hello there,

I haven't found much on the mailing lists about GeoServer and Apache 
Tomcat 10, which already uses new Jakarte Servlet Specification 5.0 
(using jakarta.servlet.* package names) so, you may find this post quite 
interesting.

Since I'm using a new Ubuntu Server 24.04 LTS, which has actually 
dropped Tomcat 9.0 (and I didn't want to use a manually installed Tomcat 
9.0 in /opt/tomcat), I've figured out a quite nice solution. The Apache 
Tomcat team has build a tool named "Tomcat Migration Tool for Jakarta 
EE", which is able to transform compiled Java classes from old 
javax.servlet names to new jakarta.servlet package names. It can process 
whole WAR files, directories of JAR files as well as single class files.

https://github.com/apache/tomcat-jakartaee-migration

This tool is also available on Debian, Ubuntu and Fedora systems by 
installing the tomcat-jakartaee-migration package and invoking the 
javax2jakarta command.

After having processed GeoServer's WEB-INF/lib directory with that tool, 
GeoServer 2.25.2 started within Apache Tomcat Server with no issues 
logged. Additionally, at first glance, GeoServer seems to *work* without 
issues as well. Thumbs up!

The migration tool has been written in Java so, you should even be able 
to integrate it into GeoServer's build processes in order to produce a 
additional download packages compatible with Jakarta Servlet 
Specification 5.0 (jakarta.servlet.*).

Cheers
Carsten

Re: [Geoserver-users] GetTimeSeries: is it possible to customize CSV output value field name?

[Andrea A. <and...@ge...>]

Hi,
no, it's not customizable, it's hard coded to use the layer name.
It could be made customizable using a vendor parameter, but code needs to
be written for that to happen.

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, Jul 16, 2024 at 10:35 AM andy <abo...@gm...> wrote:

> Hi,
> I run this kind of query [1]
>
>
> wms?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetTimeSeries&LAYERS=lorem_S6_021:s6-01-02&STYLES=&WIDTH=40&HEIGHT=40&FORMAT=text/csv&INFO_FORMAT=text/csv&exceptions=&QUERY_LAYERS=lorem_S6_021:s6-01-02&CRS=EPSG%3A3857&BBOX=....&I=20&J=20&TIME=1970-01-01/2024-12-31
>
> And I have this sample output
>
> # X: 4143984.870326454
> # Y: 2501942.3064727117
> Time (UTC),lorem_S6_01:s6-01-02
> 2023-11-22T00:00:00.000Z,0.4559512734413147
> 2023-11-23T00:00:00.000Z,0.43369847536087036
> 2023-11-24T00:00:00.000Z,0.4384692907333374
> 2023-11-25T00:00:00.000Z,0.4204336702823639
>
> Is there a way to customize the value field name, to have "Lorem
> (temperatures)" instead of "lorem_S6_01:s6-01-02"
>
> Thank you,
>
> Andrea
>
> [1]
> https://docs.geoserver.org/stable/en/user/community/ncwms/index.html#ncwms-gettimeseries-operation
>
>
> _______________________________________________
> 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
>
>
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

[Geoserver-users] GetTimeSeries: is it possible to customize CSV output value field name?

[andy <abo...@gm...>]

Hi,
I run this kind of query [1]

wms?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetTimeSeries&LAYERS=lorem_S6_021:s6-01-02&STYLES=&WIDTH=40&HEIGHT=40&FORMAT=text/csv&INFO_FORMAT=text/csv&exceptions=&QUERY_LAYERS=lorem_S6_021:s6-01-02&CRS=EPSG%3A3857&BBOX=....&I=20&J=20&TIME=1970-01-01/2024-12-31

And I have this sample output

# X: 4143984.870326454
# Y: 2501942.3064727117
Time (UTC),lorem_S6_01:s6-01-02
2023-11-22T00:00:00.000Z,0.4559512734413147
2023-11-23T00:00:00.000Z,0.43369847536087036
2023-11-24T00:00:00.000Z,0.4384692907333374
2023-11-25T00:00:00.000Z,0.4204336702823639

Is there a way to customize the value field name, to have "Lorem
(temperatures)" instead of "lorem_S6_01:s6-01-02"

Thank you,

Andrea

[1] https://docs.geoserver.org/stable/en/user/community/ncwms/index.html#ncwms-gettimeseries-operation

Re: [Geoserver-users] Determining Geoserver patch version when using x.y-SNAPSHOT in context of CVE-2024-36401

[Jody G. <jod...@gm...>]

 Yeah the docs have a challenge of being generated not knowing the most
recently released version...

The manual you download for the 2.25.2 version has the correct examples:

   -
   https://sourceforge.net/projects/geoserver/files/GeoServer/2.25.2/geoserver-2.25.2-htmldoc.zip



We no longer publish online the docs for each release, only nightly docs,
so the online examples are always wrong.

This is something I fixed for mkdocs - compare:

   - sphinx-build:
   https://docs.geoserver.org/latest/en/user/installation/docker.html
   - mkdocs: https://jodygarnett.github.io/geoserver/installation/docker/


What do you mean about docker tags?
--
Jody Garnett


On Jul 11, 2024 at 10:36:06 PM, Alexandre Gacon <ale...@gm...>
wrote:

> I find the naming convention good enough but perhaps we should make the
> information shared by Mark more obvious, at least in the documentation.
>
> Perhaps we could also display it in the docker logs.
>
> Alexandre
>
> Le ven. 12 juil. 2024 à 00:45, Jody Garnett <jod...@gm...> a
> écrit :
>
>> Thanks for the fedback,
>>
>> I wonder if there is some Docker convention for marking nightly builds to
>> make it more obvious?
>> --
>> Jody Garnett
>>
>>
>> On Jul 11, 2024 at 3:10:20 PM, Maximilian Friedersdorff <
>> ma...@gw...> wrote:
>>
>>> On 11 July 2024 16:03:48 BST, Mark Prins <mc....@gm...> wrote:
>>>
>>> To be certain you will need to check the Git Revision shown on the About
>>> page of GeoServer after logging in and compare that to Github, looking at
>>> the Build Date is second best.
>>>
>>>
>>> This was my instinct too, I couldn't find the referenced revision for
>>> some reason, though that's on me.  I did compare the build date against the
>>> release date of 2.24.4 and convinced myself that I was more than likely
>>> safe.
>>>
>>> I've now pinned to 2.24.4 explicitly, on advice from previous posts to
>>> this thread.
>>>
>>> Just from the name of the tag, having done no reading at all (which is
>>> to say entirely my fault), I just assumed that 2.24.x meant: The latest
>>> patch on the 2.24 major.minor version.
>>>
>>> Max
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>> Geo...@li...
>>> 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
>>
>>
>> Geo...@li...
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>

Re: [Geoserver-users] Determining installed extensions

[Jody G. <jod...@gm...>]

That is an interesting idea, I expect a flag could be added to the module
status information to indicate if module was installed?


One caution the geoserver status page has a list of modules ... the list is
incomplete as not all extensions have the following snippet defined

    <bean id="gsMainModule" class="org.geoserver.platform.ModuleStatusImpl">
        <constructor-arg index="0" value="gs-main"/>
        <constructor-arg index="1" value="GeoServer Main"/>
    </bean>

It would be a good first time contribution item for a volunteer to double
check this.

This information is also available from REST API
http://localhost:8080/geoserver/rest/about/status  which may help with
automation.

The other thing you can check is the the rest API allows listing of jars
installed, you can look for gs-<extension> in the list ...
http://localhost:8080/geoserver/rest/about/manifest

It may be more effective to do a creative diff of these results?
--
Jody Garnett


On Jul 12, 2024 at 8:57:06 AM, Tom Chadwin <tom...@as...>
wrote:

> Hello
>
> Is there an approved method of determining which extensions have been
> installed since initial deployment? I compared Server Status > Modules with
> a vanilla install, but some installed extensions were not listed (Installer
> was an example). I can compare WEB-INF/lib with a bare installation, but
> wondered if there was a more user-friendly method.
>
> Thanks
>
> Tom
>
>
> --
>
>    - Book a call <https://www.astuntechnology.com/about/#meet-our-experts> with
>    one of us
>    - Sign up to our mailing list
>    <https://share-eu1.hsforms.com/14qmOhwtiSs-v_-tr0dDYIwf4gwl> for any
>    updates
>
> iShare - enterprise geographic intelligence platform
> <https://www.astuntechnology.com/cloud-products/ishare/>
> GeoServer, PostGIS and QGIS training
> <https://www.astuntechnology.com/training/>
> Open Source Support <https://www.astuntechnology.com/support/>
>
> Astun Technology Ltd t:+44 1372 744 009 contact us online
> <https://www.astuntechnology.com/contact-us/>
> web: astuntechnology.com  <https://www.astuntechnology.com/> twitter:
> @astuntech <https://twitter.com/astuntech>
> Company registration no. 5410695. Registered in England and Wales.
> Registered office: Penrose House, 67 Hightown Road, Banbury, OX16 9BE VAT
> no. 864201149.
> _______________________________________________
> 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
>
>
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>