Re: [Geoserver-users] url checks timing out system

2024-07-10 Thread Bessette-Halsema, Dominique E via Geoserver-users 
It appears I am getting an OverlappingFileLockException on line 80 in the 
org.geoserver.platform.resource.FileLockProvider class

   while (currLock == null && count < maxLockAttempts) {
// the file output stream can also fail to be acquired due 
to the
// other nodes deleting the file
currFos = new FileOutputStream(file);
try {
currLock = currFos.getChannel().lock();
} catch (OverlappingFileLockException | IOException e) {
IOUtils.closeQuietly(currFos);
try {
Thread.sleep(20);
} catch (InterruptedException ie) {
// ok, moving on
}
} // this one is also thrown with a message "avoided fs 
deadlock"

count++;
}

The file that is locked is the filelock/#.lock file in the data directory.  
Do you know what may be causing this?


Dominique Bessette

From: Bessette-Halsema, Dominique E via Geoserver-users 

Sent: Wednesday, July 10, 2024 12:28 PM
To: 'GeoServer Users' 
Subject: [Geoserver-users] url checks timing out system

Hello I have using GeoServer 2. 24. 4 on Windows with Java 11. When I make a 
WMS getCapabilities request for a workspace that only contains postgis layers 
it eventually times out. I would like to note we are having no issues on linux, 
this only
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
Please use caution with links, attachments, and any requests for credentials.
ZjQcmQRYFpfptBannerEnd
Hello

I have using GeoServer 2.24.4 on Windows with Java 11.  When I make a WMS 
getCapabilities request for a workspace that only contains postgis layers it 
eventually times out.  I would like to note we are having no issues on linux, 
this only seems to be a windows problem and I have no issues making a WFS or 
WCS getCapabilities call.  I have also tried disabling URL checks and enabling 
URL checks to allow all strings, but neither have made a difference.


I attached the full error but here is a snippet

10 Jul 17:57:34 DEBUG  [resource.FileLockProvider] - Lock 
security/urlchecks.xml mapped onto 
F:\mysystem\gis\geoserver\external\filelocks\01708370114427b013e293238f5a0daff5937969.lock
 released by thread 786
10 Jul 17:57:34 DEBUG  [resource.MemoryLockProvider] - Released lock key 
security/urlchecks.xml mapped to index 300
10 Jul 17:57:34 WARN   [wms.capabilities] - Error getting LegendURL dimensions 
from sample
java.lang.RuntimeException: Error while checking URL 
file:///F:/mysystem/gis/geoserver/external/styles/icons/legend/text/text.png
at 
deployment.geoserver.war//org.geoserver.security.urlchecks.GeoServerURLChecker.confirm(GeoServerURLChecker.java:65)
at 
deployment.geoserver.war//org.geotools.data.ows.URLCheckers.confirm(URLCheckers.java:208)
at 
deployment.geoserver.war//org.geotools.data.ows.URLCheckers.confirm(URLCheckers.java:112)
at 
deployment.geoserver.war//org.geotools.renderer.lite.StyledShapePainter.paint(StyledShapePainter.java:419)
…..

Caused by: java.lang.IllegalStateException: Failed to get a lock on key 
security/urlchecks.xml after 6000 attempts
at 
deployment.geoserver.war//org.geoserver.platform.resource.FileLockProvider.acquire(FileLockProvider.java:95)
at 
deployment.geoserver.war//org.geoserver.platform.resource.GlobalLockProvider.acquire(GlobalLockProvider.java:47)
at 
deployment.geoserver.war//org.geoserver.platform.resource.FileSystemResourceStore$FileSystemResource.lock(FileSystemResourceStore.java:189)
at 
deployment.geoserver.war//org.geoserver.platform.resource.FileSystemResourceStore$FileSystemResource.in(FileSystemResourceStore.java:209)
at 
deployment.geoserver.war//org.geoserver.platform.FileWatcher.read(FileWatcher.java:59)
at 
deployment.geoserver.war//org.geoserver.security.urlchecks.URLCheckDAO.lambda$getConfiguration$4(URLCheckDAO.java:117)
at 
deployment.geoserver.war//org.geoserver.security.urlchecks.URLCheckDAO.configurationAction(URLCheckDAO.java:70)
at 
deployment.geoserver.war//org.geoserver.security.urlchecks.URLCheckDAO.getConfiguration(URLCheckDAO.java:114)
at 
deployment.geoserver.war//org.geoserver.security.urlchecks.URLCheckDAO.isEnabled(URLCheckDAO.java:198)
at 
deployment.geoserver.war//org.geoserver.security.urlchecks.GeoServerURLChecker.confirm(GeoServerURLChecker.java:46)

Dominique Bessette
Senior Software Engineer

T   619.881.2748
dominique.besse...@gdit.com<mailto:dominique.besse...@gdit.com>
1615 Murray Canyon Rd. #600
San Diego, CA 92108
www.gdit.com<http://www.gdit.com>

___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to t

[Geoserver-users] url checks timing out system

2024-07-10 Thread Bessette-Halsema, Dominique E via Geoserver-users 
Hello

I have using GeoServer 2.24.4 on Windows with Java 11.  When I make a WMS 
getCapabilities request for a workspace that only contains postgis layers it 
eventually times out.  I would like to note we are having no issues on linux, 
this only seems to be a windows problem and I have no issues making a WFS or 
WCS getCapabilities call.  I have also tried disabling URL checks and enabling 
URL checks to allow all strings, but neither have made a difference.


I attached the full error but here is a snippet

10 Jul 17:57:34 DEBUG  [resource.FileLockProvider] - Lock 
security/urlchecks.xml mapped onto 
F:\mysystem\gis\geoserver\external\filelocks\01708370114427b013e293238f5a0daff5937969.lock
 released by thread 786
10 Jul 17:57:34 DEBUG  [resource.MemoryLockProvider] - Released lock key 
security/urlchecks.xml mapped to index 300
10 Jul 17:57:34 WARN   [wms.capabilities] - Error getting LegendURL dimensions 
from sample
java.lang.RuntimeException: Error while checking URL 
file:///F:/mysystem/gis/geoserver/external/styles/icons/legend/text/text.png
at 
deployment.geoserver.war//org.geoserver.security.urlchecks.GeoServerURLChecker.confirm(GeoServerURLChecker.java:65)
at 
deployment.geoserver.war//org.geotools.data.ows.URLCheckers.confirm(URLCheckers.java:208)
at 
deployment.geoserver.war//org.geotools.data.ows.URLCheckers.confirm(URLCheckers.java:112)
at 
deployment.geoserver.war//org.geotools.renderer.lite.StyledShapePainter.paint(StyledShapePainter.java:419)
.

Caused by: java.lang.IllegalStateException: Failed to get a lock on key 
security/urlchecks.xml after 6000 attempts
at 
deployment.geoserver.war//org.geoserver.platform.resource.FileLockProvider.acquire(FileLockProvider.java:95)
at 
deployment.geoserver.war//org.geoserver.platform.resource.GlobalLockProvider.acquire(GlobalLockProvider.java:47)
at 
deployment.geoserver.war//org.geoserver.platform.resource.FileSystemResourceStore$FileSystemResource.lock(FileSystemResourceStore.java:189)
at 
deployment.geoserver.war//org.geoserver.platform.resource.FileSystemResourceStore$FileSystemResource.in(FileSystemResourceStore.java:209)
at 
deployment.geoserver.war//org.geoserver.platform.FileWatcher.read(FileWatcher.java:59)
at 
deployment.geoserver.war//org.geoserver.security.urlchecks.URLCheckDAO.lambda$getConfiguration$4(URLCheckDAO.java:117)
at 
deployment.geoserver.war//org.geoserver.security.urlchecks.URLCheckDAO.configurationAction(URLCheckDAO.java:70)
at 
deployment.geoserver.war//org.geoserver.security.urlchecks.URLCheckDAO.getConfiguration(URLCheckDAO.java:114)
at 
deployment.geoserver.war//org.geoserver.security.urlchecks.URLCheckDAO.isEnabled(URLCheckDAO.java:198)
at 
deployment.geoserver.war//org.geoserver.security.urlchecks.GeoServerURLChecker.confirm(GeoServerURLChecker.java:46)

Dominique Bessette
Senior Software Engineer

T   619.881.2748
dominique.besse...@gdit.com
1615 Murray Canyon Rd. #600
San Diego, CA 92108
www.gdit.com

10 Jul 17:57:34 DEBUG  [resource.FileLockProvider] - Lock 
security/urlchecks.xml mapped onto 
F:\NITES-Next\gis\geoserver\external\filelocks\01708370114427b013e293238f5a0daff5937969.lock
 released by thread 786
10 Jul 17:57:34 DEBUG  [resource.MemoryLockProvider] - Released lock key 
security/urlchecks.xml mapped to index 300
10 Jul 17:57:34 WARN   [wms.capabilities] - Error getting LegendURL dimensions 
from sample
java.lang.RuntimeException: Error while checking URL 
file:///F:/NITES-Next/gis/geoserver/external/styles/icons/legend/sigmet/sigmet_convective.png
at 
deployment.geoserver.war//org.geoserver.security.urlchecks.GeoServerURLChecker.confirm(GeoServerURLChecker.java:65)
at 
deployment.geoserver.war//org.geotools.data.ows.URLCheckers.confirm(URLCheckers.java:208)
at 
deployment.geoserver.war//org.geotools.data.ows.URLCheckers.confirm(URLCheckers.java:112)
at 
deployment.geoserver.war//org.geotools.renderer.lite.StyledShapePainter.paint(StyledShapePainter.java:419)
at 
deployment.geoserver.war//org.geoserver.wms.legendgraphic.BufferedImageLegendGraphicBuilder.renderRules(BufferedImageLegendGraphicBuilder.java:349)
at 
deployment.geoserver.war//org.geoserver.wms.legendgraphic.BufferedImageLegendGraphicBuilder.buildLegendGraphic(BufferedImageLegendGraphicBuilder.java:265)
at 
deployment.geoserver.war//org.geoserver.wms.legendgraphic.BufferedImageLegendGraphicBuilder.buildLegendGraphic(BufferedImageLegendGraphicBuilder.java:77)
at 
deployment.geoserver.war//org.geoserver.wms.legendgraphic.PNGLegendOutputFormat.produceLegendGraphic(PNGLegendOutputFormat.java:41)
at 
deployment.geoserver.war//org.geoserver.wms.legendgraphic.PNGLegendOutputFormat.produceLegendGraphic(PNGLegendOutputFormat.java:21)
at

[Geoserver-users] getMap with multiple elevations

2024-01-12 Thread Bessette-Halsema, Dominique E via Geoserver-users 
Hello, we are trying to make a getMap request to a layer group where we request 
multiple elevations (eg; elevation =2,10,20).   We are using an ImageMosiac 
store.


  1.  Is this possible?  I would like to verify that only single elevation 
requests are allowed.
  2.  Can you give us any helpful pointers on how to make it possible.  Where 
in the code we should look?  Or Is there a mechanism in GeoServer that makes 
several single getMap calls and combines the image?

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

[Geoserver-users] FixedLengthOverflowException when creating workspace

2023-12-06 Thread Bessette-Halsema, Dominique E via Geoserver-users 
Hello

I just updated to GeoServer 2.23.0 and I am seeing the following error whenever 
I POST a new workspace to GeoServer  "ERROR [org.geoserver.rest] (default 
task-46) : org.xnio.channels.FixedLengthOverflowException".  The workspace is 
still created, but I was wondering why this error is being thrown.  Any 
information would be helpful.

Here is my POST to 
https://:8443/geoserver/rest/workspaces

{
  "workspace": {
"name": "WW3-ghdfghfdgsd"
  }
}


More Logging:

2023-12-06 22:14:37,462 INFO  [org.geoserver.rest.catalog] (default task-46) 
Added workspace WW3-ghdfghfdgsd
2023-12-06 22:14:37,464 INFO  [org.geoserver.rest.catalog] (default task-46) 
POST workspace WW3-ghdfghfdgsd
2023-12-06 22:14:37,465 DEBUG [org.geoserver.rest.catalog] (default task-46) 
Automatically creating namespace for workspace WW3-ghdfghfdgsd
2023-12-06 22:14:37,466 DEBUG [org.geoserver.config] (default task-46) 
org.geoserver.catalog.event.impl.CatalogBeforeAddEventImpl@2856ae1
 :handlePreAddEvent
2023-12-06 22:14:37,467 DEBUG [org.geoserver.config] (default task-46) 
Persisting namespace WW3-ghdfghfdgsd
2023-12-06 22:14:37,468 DEBUG 
[org.geoserver.platform.resource.MemoryLockProvider] (default task-46) Mapped 
lock key workspaces/WW3-ghdfghfdgsd/namespace.xml to index 712. Acquiring lock.
2023-12-06 22:14:37,469 DEBUG 
[org.geoserver.platform.resource.MemoryLockProvider] (default task-46) Mapped 
lock key workspaces/WW3-ghdfghfdgsd/namespace.xml to index 712. Lock acquired
2023-12-06 22:14:37,469 DEBUG 
[org.geoserver.platform.resource.FileLockProvider] (default task-46) Mapped 
lock key workspaces/WW3-ghdfghfdgsd/namespace.xml to lock file 
/gis/geoserver/external/filelocks/98fea05bb3c6382490166aa73c588452ae5e7261.lock.
 Attempting to lock on it.
2023-12-06 22:14:37,470 DEBUG 
[org.geoserver.platform.resource.FileLockProvider] (default task-46) Lock 
workspaces/WW3-ghdfghfdgsd/namespace.xml acquired by thread 2509 on file 
/gis/geoserver/external/filelocks/98fea05bb3c6382490166aa73c588452ae5e7261.lock
2023-12-06 22:14:37,470 DEBUG 
[org.geoserver.platform.resource.FileLockProvider] (default task-46) Lock 
workspaces/WW3-ghdfghfdgsd/namespace.xml mapped onto 
/gis/geoserver/external/filelocks/98fea05bb3c6382490166aa73c588452ae5e7261.lock 
released by thread 2509
2023-12-06 22:14:37,470 DEBUG 
[org.geoserver.platform.resource.MemoryLockProvider] (default task-46) Released 
lock key workspaces/WW3-ghdfghfdgsd/namespace.xml mapped to index 712
2023-12-06 22:14:37,470 DEBUG 
[org.geoserver.platform.resource.MemoryLockProvider] (default task-46) Mapped 
lock key workspaces/WW3-ghdfghfdgsd/namespace.xml to index 712. Acquiring lock.
2023-12-06 22:14:37,470 DEBUG 
[org.geoserver.platform.resource.MemoryLockProvider] (default task-46) Mapped 
lock key workspaces/WW3-ghdfghfdgsd/namespace.xml to index 712. Lock acquired
2023-12-06 22:14:37,470 DEBUG 
[org.geoserver.platform.resource.FileLockProvider] (default task-46) Mapped 
lock key workspaces/WW3-ghdfghfdgsd/namespace.xml to lock file 
/gis/geoserver/external/filelocks/98fea05bb3c6382490166aa73c588452ae5e7261.lock.
 Attempting to lock on it.
2023-12-06 22:14:37,470 DEBUG 
[org.geoserver.platform.resource.FileLockProvider] (default task-46) Lock 
workspaces/WW3-ghdfghfdgsd/namespace.xml acquired by thread 2509 on file 
/gis/geoserver/external/filelocks/98fea05bb3c6382490166aa73c588452ae5e7261.lock
2023-12-06 22:14:37,472 DEBUG 
[org.geoserver.platform.resource.FileLockProvider] (default task-46) Lock 
workspaces/WW3-ghdfghfdgsd/namespace.xml mapped onto 
/gis/geoserver/external/filelocks/98fea05bb3c6382490166aa73c588452ae5e7261.lock 
released by thread 2509
2023-12-06 22:14:37,472 DEBUG 
[org.geoserver.platform.resource.MemoryLockProvider] (default task-46) Released 
lock key workspaces/WW3-ghdfghfdgsd/namespace.xml mapped to index 712
2023-12-06 22:14:37,472 DEBUG [org.geoserver.config] (default task-46) 
Persisted com.sun.proxy.$Proxy610 to workspaces/WW3-ghdfghfdgsd/namespace.xml
2023-12-06 22:14:37,472 DEBUG [org.geoserver.cluster.hazelcast] (default 
task-46) 127.0.0.1:5701 - Publishing event ADD 
[uuid:9396b062-8b12-4c83-83de-5204fdc400cd, object 
id:NamespaceInfoImpl--669348df:18c41298333:-7fed, name:WW3-ghdfghfdgsd]
2023-12-06 22:14:37,474 TRACE [org.geoserver.cluster.hazelcast] 
(hz.gscluster.event-4) 127.0.0.1:5701 - Skipping message generated locally: ADD 
(/127.0.0.1:5701) [uuid:9396b062-8b12-4c83-83de-5204fdc400cd, object 
id:NamespaceInfoImpl--669348df:18c41298333:-7fed, name:WW3-ghdfghfdgsd]
2023-12-06 22:14:37,475 DEBUG [org.geoserver.cluster.hazelcast] (default 
task-46) 127.0.0.1:5701 - Waiting for acks on 
9396b062-8b12-4c83-83de-5204fdc400cd
2023-12-06 22:14:37,478 DEBUG 
[org.geoserver.platform.resource.MemoryLockProvider] (default task-46) Mapped 
lock key global.xml to index 202. Acquiring lock.
2023-12-06 22:14:37,479 DEBUG

[Geoserver-users] GeoServer stop support for older WCS versions

2023-06-28 Thread Bessette-Halsema, Dominique E via Geoserver-users 
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

[Geoserver-users] End Attribute - Time Dim

2022-05-19 Thread Bessette-Halsema, Dominique E via Geoserver-users 
Hello

I have a feature based off a database table that I'm trying to add a Time 
Dimension with the "Attribute" and "End Attribute" set

The Presentation is 'Interval and Resolution'
The Resolution is '5 minutes'
The Default value is the 'domain nearest to the reference value'
The Reference Value is the 'current'

I can see the time dimension added to the getCapailbities 
"2022-05-19T17:50:00.000Z/2022-05-19T19:55:00.000Z/PT5M"

The issue is the max value for End Attribute is  "2022-05-19T23:38:00.000Z "  
why is the getCapabilities not displaying "2022-05-19T23:38:00.000Z" as the max 
interval?  I see that the "end attribute" is only valid for a vector.  Is a 
vector not any feature?

If I change 'Attribute' to the 'End Attribute' value I can see it.
2022-05-19T20:55:00.000Z/2022-05-19T23:38:00.000Z/PT5M

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

[Geoserver-users] GeoServer 2.15 Spring vulnerability

2022-03-24 Thread Bessette-Halsema, Dominique E via Geoserver-users 
Hello

I saw that we fixed the spring vulnerability issue in GeoServer 2.17.  Was 
GeoServer 2.15 even vulnerable to this attack?  We have some environments with 
2.15 and need to know if they require a patch or upgrade.

https://osgeo-org.atlassian.net/browse/GEOS-9477



Dominique Bessette
Senior Software Engineer


___
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] [EXTERNAL] - RE: WPS gs:Clip Topology Exception

2022-03-24 Thread Bessette-Halsema, Dominique E via Geoserver-users 
There are several ways to set the CRS in the Geometry, but this probably wont 
fix your problem. I just worry that the code is setting your Geometry to the 
default EPSG and that's why it cant figure it out.  Also there are some 
Geometry limits, like crossing the antemeridian.  If you are crossing the 
antemeridian you can try shifting your polygon from 180, -180 to 0, 360 or 
break it into 2 pieces.

You can do an EPSG check:  geometry.getSRID().

Example 1: create an Envelope and then create the Geometry
 Envelope impactEnvelope = new ReferencedEnvelope(newMinX, maxx, 
miny, maxy,
   CRS.decode("EPSG:4326"));
 Geometry myGeom = JTS.toGeometry(impactEnvelope).getEnvelope();;


example 2: use mathTransform
 MathTransform transform = CRS.findMathTransform(sourceCRS, 
targetCRS, false);
 Geometry targetGeometry = JTS.transform( myGeom, transform);

Hope this helps!

Dominique Bessette
Senior Software Engineer


From: Oscar Wu 
Sent: Thursday, March 24, 2022 11:23 AM
To: Bessette-Halsema, Dominique E ; 
geoserver-users@lists.sourceforge.net
Subject: Re: [EXTERNAL] - RE: WPS gs:Clip Topology Exception


 [External: Use caution with links & attachments]

Hi Dominique,

Thank you very much for the suggestion.

I tried to explicitly define the EPSG in the getFeature request by adding 
srsName=EPSG:3005 to the url. The clipping geometry has no place to add SRS as 
it is only a geometry not a feature. However, I have made sure the coordinates 
in the clipping geometry are also generated under EPSG:3005. That being said, 
it unfortunately did not solve the issue.

Is there anything else I can try?

Thanks!

Oscar

From: Bessette-Halsema, Dominique E 
mailto:dominique.besse...@gdit.com>>
Sent: March 24, 2022 9:30 AM
To: Oscar Wu mailto:oscar...@crmltd.ca>>; 
geoserver-users@lists.sourceforge.net
 
mailto:geoserver-users@lists.sourceforge.net>>
Subject: [EXTERNAL] - RE: WPS gs:Clip Topology Exception


You may want to try specifying your EPSG in your Polygon and getFeature request



Dominique Bessette

Senior Software Engineer



From: Oscar Wu mailto:oscar...@crmltd.ca>>
Sent: Wednesday, March 23, 2022 1:02 PM
To: 
geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] WPS gs:Clip Topology Exception





 [External: Use caution with links & attachments]



Hi everyone,



First time posting here, thank you for your understanding if I am not 
explaining my situation well.



I've been trying to use the built-in gs:Clip to extract some public layers 
based on a polygon defined by coordinates. The process seemed to work well with 
a couple of layers until I tried it with one particular layer.



Here's the xml in the POST request:

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

  gs:Clip

  



  features

Re: [Geoserver-users] WPS gs:Clip Topology Exception

2022-03-24 Thread Bessette-Halsema, Dominique E via Geoserver-users 
You may want to try specifying your EPSG in your Polygon and getFeature request

Dominique Bessette
Senior Software Engineer


From: Oscar Wu 
Sent: Wednesday, March 23, 2022 1:02 PM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] WPS gs:Clip Topology Exception


 [External: Use caution with links & attachments]

Hi everyone,

First time posting here, thank you for your understanding if I am not 
explaining my situation well.

I've been trying to use the built-in gs:Clip to extract some public layers 
based on a polygon defined by coordinates. The process seemed to work well with 
a couple of layers until I tried it with one particular layer.

Here's the xml in the POST request:

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

  gs:Clip

  



  features

  http://openmaps.gov.bc.ca/geo/pub/ows?service=WFSversion=2.0.0request=GetFeaturetypeName=WHSE_CADASTRE.PMBC_PARCEL_FABRIC_POLY_SVWoutputFormat=jsonbbox=715319.3721917,1028613.368105,735025.9926936,1041407.195003;
 method="GET"/>





  clip

  



  



  

  



  result



  



In this case, a TopologyException was thrown (the stack trace is attached in 
the email):

org.locationtech.jts.geom.TopologyException: found non-noded intersection 
between LINESTRING ( 737930.4267 1033205.5095, 737925.915 1033208.5901 ) and 
LINESTRING ( 737933.8941 1033203.0284, 737930.4267 1033205.5095 ) [ 
(737930.4267, 1033205.5095, NaN) ]

I'm using Geoserver 2.20.2, GeoTools 26.2 and WPS 1.0.0.

I have searched about this issue and learned that this is caused by invalid 
geometry which was explained here:
https://locationtech.github.io/jts/jts-faq.html#D1

Then I tried to create a customized WPS that 'clean' the input either using 
buffer(0) or the GeometryFixer in JTS before sending it to the clip process but 
neither of them solved the issue.

I have exhausted my solutions to this problem and I'm wondering if anyone have 
encountered a similar issue before? May I have some suggestions about what to 
look for next?

Thank you very much!

Regards,

Oscar
___
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] chaining issue with cropcoverage

2022-03-02 Thread Bessette-Halsema, Dominique E via Geoserver-users 
Hello

I noticed that when I chain cropcoverage  and jiffle in the SLD that at certain 
zoom levels the full image/png  is not displayed.  It looks like some tiles are 
missing but I added the parameter TILED=false.  I remember that someone 
mentioned chaining is not working properly.  Is this a side affect of the 
chaining?  Is there a bug report or patch for this?  I'm using GeoServer 2.18

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

[Geoserver-users] getMap with Clip does not update with Time

2022-02-18 Thread Bessette-Halsema, Dominique E via Geoserver-users 
Hello

I'm using a getMap call to a layergroup.  If I don't add the "clip" vendor 
parameter, I can see my the data changing with the time dimension.  If I add 
the "clip" the getMap call stops changing with the time dimension and it looks 
like it returns the data with the default time.  I'm using GeoServer 2.18.  Has 
this been looked at?  The comment in the wiki page stated "Currently this 
parameter is ignored for layers with Complex features." Is Jiffle styling a 
complex feature?  Is there a better way to crop or add a mask to a grid?

Example Call:
/geoserver/wms?SERVICE=WMS=GetMap
=1.1.1=image/png=EPSG:4326=2235=1077
=-147.392578125,-69.163979270242,245.47851562499,120.15242697976
=2022-02-18T18:00:00.000Z=true=false
=2.0=TestGrid.Cropped.386
=POLYGON+%28%28102.925+4.925%2C+102.925+55.175%2C+150.175+55.175%2C+150.175+4.925%2C+102.925+4.925%29%29

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

Re: [Geoserver-users] SLD is producing blurry image

2022-02-17 Thread Bessette-Halsema, Dominique E via Geoserver-users 
Just an FYI I think I figured it out by doing something like this (not fully 
tested)

The jiffle script:
  data = src[0];
  dest = (data  80.0 ) ? data : data*0 ;
//if it breaks the rule make that point 0 else leave it as the original data 
value

the colorMap:

 
 
 



Dominique Bessette
Senior Software Engineer
T   619.881.2478

From: Andrea Aime 
Sent: Thursday, February 17, 2022 1:18 AM
To: Bessette-Halsema, Dominique E 
Cc: GeoServer Users 
Subject: Re: [Geoserver-users] SLD is producing blurry image


 [External: Use caution with links & attachments]

The behavior you're experiencing seems the expected one:

  *   You have pixels covering a very large area, they are rendered as square 
blocks
  *   If you enable interporpolation, say bilinear, it's just acting on a 2x2 
pixel block, giving the blurry effect
Looks like you'd like to have a full interpolation algorithm acting on the 
image, say a Inverse Distance Weighted acting on the
pixel centers and treating them as sparse points instead, and work off larger 
pixel distances (eventually account for all those in the
view before
GeoServer does not have such an ability ... maybe one could try chaining the 
Barnes Surfaces algorithm, or modify the polygon extraction process to
allow for smoothing, and then chain that one too, but... rendering 
transformation chaining is not working very well in general

Looks like you need to go down this path: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-fixes,-improvements-and-new-features-in-GeoServer<https://urldefense.us/v3/__https:/github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-fixes,-improvements-and-new-features-in-GeoServer__;!!JRQnnSFuzw7wjAKq6ti6!jizqlPfXpVvW0LfS1Rl6oNeB2qelwmLgCuUvSX8-pXh7HkkyXU5hM6k8hIcWRNoMj21T8A$>

Cheers
Andrea



On Thu, Feb 17, 2022 at 12:33 AM Bessette-Halsema, Dominique E via 
Geoserver-users 
mailto:geoserver-users@lists.sourceforge.net>>
 wrote:
Hello

I have an sld that uses jiffle and the output is a 1 or a 0

I would like my style to appear “smoothed” out or interpolated on the map.  
When the colormap type=ramp and the map is zoomed out it appears smooth but 
when I start to zoom in it appears blurry (see attachement).   I understand I 
should use “type=”values”” to mark all the values of 1 red but then the image 
appears blocky (see attachment).  Is there a way I can assign the values of 1 
red and smooth out the edges?

http://www.opengis.net/sld<https://urldefense.us/v3/__http:/www.opengis.net/sld__;!!JRQnnSFuzw7wjAKq6ti6!jizqlPfXpVvW0LfS1Rl6oNeB2qelwmLgCuUvSX8-pXh7HkkyXU5hM6k8hIcWRNraeuDL7g$>
 
xmlns:sld=http://www.opengis.net/sld<https://urldefense.us/v3/__http:/www.opengis.net/sld__;!!JRQnnSFuzw7wjAKq6ti6!jizqlPfXpVvW0LfS1Rl6oNeB2qelwmLgCuUvSX8-pXh7HkkyXU5hM6k8hIcWRNraeuDL7g$>
 
xmlns:gml=http://www.opengis.net/gml<https://urldefense.us/v3/__http:/www.opengis.net/gml__;!!JRQnnSFuzw7wjAKq6ti6!jizqlPfXpVvW0LfS1Rl6oNeB2qelwmLgCuUvSX8-pXh7HkkyXU5hM6k8hIcWRNokxyWYuw$>
 
xmlns:ogc=http://www.opengis.net/ogc<https://urldefense.us/v3/__http:/www.opengis.net/ogc__;!!JRQnnSFuzw7wjAKq6ti6!jizqlPfXpVvW0LfS1Rl6oNeB2qelwmLgCuUvSX8-pXh7HkkyXU5hM6k8hIcWRNpROv8hVQ$>
 version="1.0.0">
  
TEst

  Testsld:Name>
  TSEts
  
name

  

  coverage


  script
  
  data = src[0];
  gph =  src[1]
  dted = src[2];
  dest = (( data  80.0 )  (gph  
dted) ) ? 1 : 0;
   

  


  

  
  


  

  

  



Thanks!
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#/<https://urldefense.us/v3/__http:/www.ianturton.com/talks/foss4g.html*/__;Iw!!JRQnnSFuzw7wjAKq6ti6!jizqlPfXpVvW0LfS1Rl6oNeB2qelwmLgCuUvSX8-pXh7HkkyXU5hM6k8hIcWRNpb130xzQ$>
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html<https://urldefense.us/v3/__http:/geoserver.org/comm/userlist-guidelines.html__;!!JRQnnSFuzw7wjAKq6ti6!jizqlPfXpVvW0LfS1Rl6oNeB2qelwmLgCuUvSX8-pXh7HkkyXU5hM6k8hIcWRNoiSH-xsw$>

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://url

Re: [Geoserver-users] SLD is producing blurry image

2022-02-17 Thread Bessette-Halsema, Dominique E via Geoserver-users 
Hello
I understand the styles are behaving as expected.  I was hoping someone could 
give me an idea on how to style it better to give me the output I would like.  
I’ll look at chaining the polygon extraction process and someone else mentioned 
using scale based rules.  Thanks!


Dominique Bessette

From: Andrea Aime 
Sent: Thursday, February 17, 2022 1:18 AM
To: Bessette-Halsema, Dominique E 
Cc: GeoServer Users 
Subject: Re: [Geoserver-users] SLD is producing blurry image


 [External: Use caution with links & attachments]

The behavior you're experiencing seems the expected one:

  *   You have pixels covering a very large area, they are rendered as square 
blocks
  *   If you enable interporpolation, say bilinear, it's just acting on a 2x2 
pixel block, giving the blurry effect
Looks like you'd like to have a full interpolation algorithm acting on the 
image, say a Inverse Distance Weighted acting on the
pixel centers and treating them as sparse points instead, and work off larger 
pixel distances (eventually account for all those in the
view before
GeoServer does not have such an ability ... maybe one could try chaining the 
Barnes Surfaces algorithm, or modify the polygon extraction process to
allow for smoothing, and then chain that one too, but... rendering 
transformation chaining is not working very well in general

Looks like you need to go down this path: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-fixes,-improvements-and-new-features-in-GeoServer<https://urldefense.us/v3/__https:/github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-fixes,-improvements-and-new-features-in-GeoServer__;!!JRQnnSFuzw7wjAKq6ti6!jizqlPfXpVvW0LfS1Rl6oNeB2qelwmLgCuUvSX8-pXh7HkkyXU5hM6k8hIcWRNoMj21T8A$>

Cheers
Andrea



On Thu, Feb 17, 2022 at 12:33 AM Bessette-Halsema, Dominique E via 
Geoserver-users 
mailto:geoserver-users@lists.sourceforge.net>>
 wrote:
Hello

I have an sld that uses jiffle and the output is a 1 or a 0

I would like my style to appear “smoothed” out or interpolated on the map.  
When the colormap type=ramp and the map is zoomed out it appears smooth but 
when I start to zoom in it appears blurry (see attachement).   I understand I 
should use “type=”values”” to mark all the values of 1 red but then the image 
appears blocky (see attachment).  Is there a way I can assign the values of 1 
red and smooth out the edges?

http://www.opengis.net/sld<https://urldefense.us/v3/__http:/www.opengis.net/sld__;!!JRQnnSFuzw7wjAKq6ti6!jizqlPfXpVvW0LfS1Rl6oNeB2qelwmLgCuUvSX8-pXh7HkkyXU5hM6k8hIcWRNraeuDL7g$>
 
xmlns:sld=http://www.opengis.net/sld<https://urldefense.us/v3/__http:/www.opengis.net/sld__;!!JRQnnSFuzw7wjAKq6ti6!jizqlPfXpVvW0LfS1Rl6oNeB2qelwmLgCuUvSX8-pXh7HkkyXU5hM6k8hIcWRNraeuDL7g$>
 
xmlns:gml=http://www.opengis.net/gml<https://urldefense.us/v3/__http:/www.opengis.net/gml__;!!JRQnnSFuzw7wjAKq6ti6!jizqlPfXpVvW0LfS1Rl6oNeB2qelwmLgCuUvSX8-pXh7HkkyXU5hM6k8hIcWRNokxyWYuw$>
 
xmlns:ogc=http://www.opengis.net/ogc<https://urldefense.us/v3/__http:/www.opengis.net/ogc__;!!JRQnnSFuzw7wjAKq6ti6!jizqlPfXpVvW0LfS1Rl6oNeB2qelwmLgCuUvSX8-pXh7HkkyXU5hM6k8hIcWRNpROv8hVQ$>
 version="1.0.0">
  
TEst

  Testsld:Name>
  TSEts
  
name

  

  coverage


  script
  
  data = src[0];
  gph =  src[1]
  dted = src[2];
  dest = (( data  80.0 )  (gph  
dted) ) ? 1 : 0;
   

  


  

  
  


  

  

  



Thanks!
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#/<https://urldefense.us/v3/__http:/www.ianturton.com/talks/foss4g.html*/__;Iw!!JRQnnSFuzw7wjAKq6ti6!jizqlPfXpVvW0LfS1Rl6oNeB2qelwmLgCuUvSX8-pXh7HkkyXU5hM6k8hIcWRNpb130xzQ$>
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html<https://urldefense.us/v3/__http:/geoserver.org/comm/userlist-guidelines.html__;!!JRQnnSFuzw7wjAKq6ti6!jizqlPfXpVvW0LfS1Rl6oNeB2qelwmLgCuUvSX8-pXh7HkkyXU5hM6k8hIcWRNoiSH-xsw$>

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.us/v3/__https:/github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer__;!!JRQnnSFuzw7wjAKq6ti6!jizqlPfXpVvW0LfS1Rl

Re: [Geoserver-users] SLD is producing blurry image

2022-02-17 Thread Bessette-Halsema, Dominique E via Geoserver-users 
Hello,
Can you please elaborate on what you mean by scale based rules?

Dominique Bessette
Senior Software Engineer
T   619.881.2478

From: Alexandre Gacon 
Sent: Wednesday, February 16, 2022 10:44 PM
To: Bessette-Halsema, Dominique E 
Cc: GeoServer Users 
Subject: Re: [Geoserver-users] SLD is producing blurry image


 [External: Use caution with links & attachments]

Did you try to use scale based rules to have the behaviour smooth at large 
scale and the other behaviour at smaller scale?

Alexandre
Le jeu. 17 févr. 2022 à 00:33, Bessette-Halsema, Dominique E via 
Geoserver-users 
mailto:geoserver-users@lists.sourceforge.net>>
 a écrit :
Hello

I have an sld that uses jiffle and the output is a 1 or a 0

I would like my style to appear “smoothed” out or interpolated on the map.  
When the colormap type=ramp and the map is zoomed out it appears smooth but 
when I start to zoom in it appears blurry (see attachement).   I understand I 
should use “type=”values”” to mark all the values of 1 red but then the image 
appears blocky (see attachment).  Is there a way I can assign the values of 1 
red and smooth out the edges?

http://www.opengis.net/sld<https://urldefense.us/v3/__http:/www.opengis.net/sld__;!!JRQnnSFuzw7wjAKq6ti6!k9MSx5X-8N-xgitSgJ3IspQcWQaBjX8-Ckvvk3xO--RNBjLTXb_5uo6_Z_Iu6GVMrczRig$>
 
xmlns:sld=http://www.opengis.net/sld<https://urldefense.us/v3/__http:/www.opengis.net/sld__;!!JRQnnSFuzw7wjAKq6ti6!k9MSx5X-8N-xgitSgJ3IspQcWQaBjX8-Ckvvk3xO--RNBjLTXb_5uo6_Z_Iu6GVMrczRig$>
 
xmlns:gml=http://www.opengis.net/gml<https://urldefense.us/v3/__http:/www.opengis.net/gml__;!!JRQnnSFuzw7wjAKq6ti6!k9MSx5X-8N-xgitSgJ3IspQcWQaBjX8-Ckvvk3xO--RNBjLTXb_5uo6_Z_Iu6GVUNAl9Kw$>
 
xmlns:ogc=http://www.opengis.net/ogc<https://urldefense.us/v3/__http:/www.opengis.net/ogc__;!!JRQnnSFuzw7wjAKq6ti6!k9MSx5X-8N-xgitSgJ3IspQcWQaBjX8-Ckvvk3xO--RNBjLTXb_5uo6_Z_Iu6GV--wWWhQ$>
 version="1.0.0">
  
TEst

  Testsld:Name>
  TSEts
  
name

  

  coverage


  script
  
  data = src[0];
  gph =  src[1]
  dted = src[2];
  dest = (( data  80.0 )  (gph  
dted) ) ? 1 : 0;
   

  


  

  
  


  

  

  



Thanks!
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#/<https://urldefense.us/v3/__http:/www.ianturton.com/talks/foss4g.html*/__;Iw!!JRQnnSFuzw7wjAKq6ti6!k9MSx5X-8N-xgitSgJ3IspQcWQaBjX8-Ckvvk3xO--RNBjLTXb_5uo6_Z_Iu6GXBqf7oew$>
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html<https://urldefense.us/v3/__http:/geoserver.org/comm/userlist-guidelines.html__;!!JRQnnSFuzw7wjAKq6ti6!k9MSx5X-8N-xgitSgJ3IspQcWQaBjX8-Ckvvk3xO--RNBjLTXb_5uo6_Z_Iu6GWr_1TCsw$>

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.us/v3/__https:/github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer__;!!JRQnnSFuzw7wjAKq6ti6!k9MSx5X-8N-xgitSgJ3IspQcWQaBjX8-Ckvvk3xO--RNBjLTXb_5uo6_Z_Iu6GUzOe9qvg$>


Geoserver-users@lists.sourceforge.net<mailto:Geoserver-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/geoserver-users<https://urldefense.us/v3/__https:/lists.sourceforge.net/lists/listinfo/geoserver-users__;!!JRQnnSFuzw7wjAKq6ti6!k9MSx5X-8N-xgitSgJ3IspQcWQaBjX8-Ckvvk3xO--RNBjLTXb_5uo6_Z_Iu6GUpAdaoTQ$>
___
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] jiffle Logical operators

2022-02-14 Thread Bessette-Halsema, Dominique E via Geoserver-users 
Can we do jiffle Logical operators or just math algebra?

Example.. Is this valid (untested) or would the '<' ruin the XML?

  
  

  coverage


  script
  
b = src[0];
c = src[1];
dest = (b < c ? 0:1);
  

  


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

Re: [Geoserver-users] ImageMosaic JDBC entering in null values for attributes

2022-01-24 Thread Bessette-Halsema, Dominique E via Geoserver-users 
Hello.  This code is in the imagemosaic and jdbc geotools v24 modules.  Sorry 
for the confusion

Dominique Bessette

From: Andrea Aime 
Sent: Saturday, January 22, 2022 9:12 AM
To: Bessette-Halsema, Dominique E 
Cc: GeoServer Users 
Subject: Re: [Geoserver-users] ImageMosaic JDBC entering in null values for 
attributes


 [External: Use caution with links & attachments]

Hi Dominique,
the imagemosaic jdbc module has been removed from both the GeoTools and 
GeoServer
source code, due to persistent lack of a maintainer. It's also generating no 
business for core
developers (which could have justified other developers picking up the module).
Long story short, the module is gone.

If you or someone from your organization is interested in stepping up and 
maintaining the module,
it can be restored from the version control. Same could happen if any of the 
core devs would get
business around it.

Cheers
Andrea


On Wed, Jan 19, 2022 at 12:35 AM Bessette-Halsema, Dominique E via 
Geoserver-users 
mailto:geoserver-users@lists.sourceforge.net>>
 wrote:
I also found in the logs that for the file that failed it could not find the 
property collectors

022-01-18 20:05:33,900 DEBUG [org.geotools.gce.imagemosaic] (default task-83) 
No properties collector have been found
2022-01-18 20:05:33,900 INFO  [org.geotools.gce.imagemosaic] (default task-83) 
Now indexing file 
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif

Dominique Bessette
Senior Software Engineer
T   619.881.2478

From: Bessette-Halsema, Dominique E via Geoserver-users 
mailto:geoserver-users@lists.sourceforge.net>>
Sent: Tuesday, January 18, 2022 2:15 PM
To: 
geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net>
Subject: Re: [Geoserver-users] ImageMosaic JDBC entering in null values for 
attributes


 [External: Use caution with links & attachments]

Is there a configuration or way to make it so the imagemosaic tables for the 
granules are “Not Null”?  This way at least the bad entry will be thrown out 
and all other ingested layers can be used.

Dominique

From: Bessette-Halsema, Dominique E via Geoserver-users 
mailto:geoserver-users@lists.sourceforge.net>>
Sent: Tuesday, January 18, 2022 12:54 PM
To: 
geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net>
Subject: [Geoserver-users] ImageMosaic JDBC entering in null values for 
attributes


 [External: Use caution with links & attachments]

Hello

I’m using ImageMosaic with the JDBC extension.  I found that when GeoServer is 
under heavy load, intermittently the JDBC code will insert null values for the 
attributes.  This causes the WMS getCapabilities to fail with the following 
Warning

WARN  [org.geoserver.wms.capabilities] (default task-91) Error writing 
metadata; skipping layer: AFGHAN-n2-a1.grad_mod_refr.ht_sfc: 
java.lang.NullPointerException

This essentially makes that layer unusable until the database entry is deleted. 
 I extracted the geotools jdbc code where it is setting the values to null.  
What I’m looking for is some insight into why this is happening or a possible 
fix.  Has this issue been documented?

2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83) 
exporting LogicFilter
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83) 
exporting SQL ComparisonFilter
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83) 
exporting PropertyName
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83) 
exporting PropertyName
2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) SELECT 
count(*) FROM 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" WHERE 
("location" = ? AND "location" IS NOT NULL )
2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) 1 = 
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,024 DEBUG [org.geotools.jdbc] (default task-83) SELECT 
"fid",ST_AsEWKB("the_geom") as 
"the_geom","location","validtime","analysis_time","elevation" FROM 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" LIMIT 1
2022-01-18 20:05:34,029 DEBUG [org.geotools.jdbc] (default task-83) SELECT 
ST_AsText(ST_Force2D(ST_Envelope(ST_Extent("the_geom"::geometry FROM 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc"
2022-01-18 20:05:34,029 WARN  [org.hibernate.orm.deprecation] (default task-55) 
HHH9022: Hibernate's legacy org.hibernate.Criteria API is deprecated; use 
the JPA javax.persistence.criteria.CriteriaQuery instead
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) SELECT 
"fid",ST_AsEWKB("

Re: [Geoserver-users] ImageMosaic JDBC entering in null values for attributes

2022-01-18 Thread Bessette-Halsema, Dominique E via Geoserver-users 
I also found in the logs that for the file that failed it could not find the 
property collectors

022-01-18 20:05:33,900 DEBUG [org.geotools.gce.imagemosaic] (default task-83) 
No properties collector have been found
2022-01-18 20:05:33,900 INFO  [org.geotools.gce.imagemosaic] (default task-83) 
Now indexing file 
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif

Dominique Bessette
Senior Software Engineer
T   619.881.2478

From: Bessette-Halsema, Dominique E via Geoserver-users 

Sent: Tuesday, January 18, 2022 2:15 PM
To: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] ImageMosaic JDBC entering in null values for 
attributes


 [External: Use caution with links & attachments]

Is there a configuration or way to make it so the imagemosaic tables for the 
granules are "Not Null"?  This way at least the bad entry will be thrown out 
and all other ingested layers can be used.

Dominique

From: Bessette-Halsema, Dominique E via Geoserver-users 
mailto:geoserver-users@lists.sourceforge.net>>
Sent: Tuesday, January 18, 2022 12:54 PM
To: 
geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net>
Subject: [Geoserver-users] ImageMosaic JDBC entering in null values for 
attributes


 [External: Use caution with links & attachments]

Hello

I'm using ImageMosaic with the JDBC extension.  I found that when GeoServer is 
under heavy load, intermittently the JDBC code will insert null values for the 
attributes.  This causes the WMS getCapabilities to fail with the following 
Warning

WARN  [org.geoserver.wms.capabilities] (default task-91) Error writing 
metadata; skipping layer: AFGHAN-n2-a1.grad_mod_refr.ht_sfc: 
java.lang.NullPointerException

This essentially makes that layer unusable until the database entry is deleted. 
 I extracted the geotools jdbc code where it is setting the values to null.  
What I'm looking for is some insight into why this is happening or a possible 
fix.  Has this issue been documented?

2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83) 
exporting LogicFilter
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83) 
exporting SQL ComparisonFilter
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83) 
exporting PropertyName
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83) 
exporting PropertyName
2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) SELECT 
count(*) FROM 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" WHERE 
("location" = ? AND "location" IS NOT NULL )
2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) 1 = 
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,024 DEBUG [org.geotools.jdbc] (default task-83) SELECT 
"fid",ST_AsEWKB("the_geom") as 
"the_geom","location","validtime","analysis_time","elevation" FROM 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" LIMIT 1
2022-01-18 20:05:34,029 DEBUG [org.geotools.jdbc] (default task-83) SELECT 
ST_AsText(ST_Force2D(ST_Envelope(ST_Extent("the_geom"::geometry FROM 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc"
2022-01-18 20:05:34,029 WARN  [org.hibernate.orm.deprecation] (default task-55) 
HHH9022: Hibernate's legacy org.hibernate.Criteria API is deprecated; use 
the JPA javax.persistence.criteria.CriteriaQuery instead
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) SELECT 
"fid",ST_AsEWKB("the_geom") as 
"the_geom","location","validtime","analysis_time","elevation" FROM 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" WHERE 
0 = 1
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 
the_geom to POLYGON ((47.4749994 19.025, 47.4749994 40.775, 
78.525 40.775, 78.525 19.025, 47.4749994 19.025))
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 0 
to POLYGON ((47.4749994 19.025, 47.4749994 40.775, 78.525 
40.775, 78.525 19.025, 47.4749994 19.025))
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 
location to 
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 1 
to 
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 
validtime to null
2022-01-18 20:05:34,03

Re: [Geoserver-users] ImageMosaic JDBC entering in null values for attributes

2022-01-18 Thread Bessette-Halsema, Dominique E via Geoserver-users 
Is there a configuration or way to make it so the imagemosaic tables for the 
granules are "Not Null"?  This way at least the bad entry will be thrown out 
and all other ingested layers can be used.

Dominique

From: Bessette-Halsema, Dominique E via Geoserver-users 

Sent: Tuesday, January 18, 2022 12:54 PM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] ImageMosaic JDBC entering in null values for 
attributes


 [External: Use caution with links & attachments]

Hello

I'm using ImageMosaic with the JDBC extension.  I found that when GeoServer is 
under heavy load, intermittently the JDBC code will insert null values for the 
attributes.  This causes the WMS getCapabilities to fail with the following 
Warning

WARN  [org.geoserver.wms.capabilities] (default task-91) Error writing 
metadata; skipping layer: AFGHAN-n2-a1.grad_mod_refr.ht_sfc: 
java.lang.NullPointerException

This essentially makes that layer unusable until the database entry is deleted. 
 I extracted the geotools jdbc code where it is setting the values to null.  
What I'm looking for is some insight into why this is happening or a possible 
fix.  Has this issue been documented?

2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83) 
exporting LogicFilter
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83) 
exporting SQL ComparisonFilter
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83) 
exporting PropertyName
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83) 
exporting PropertyName
2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) SELECT 
count(*) FROM 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" WHERE 
("location" = ? AND "location" IS NOT NULL )
2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) 1 = 
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,024 DEBUG [org.geotools.jdbc] (default task-83) SELECT 
"fid",ST_AsEWKB("the_geom") as 
"the_geom","location","validtime","analysis_time","elevation" FROM 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" LIMIT 1
2022-01-18 20:05:34,029 DEBUG [org.geotools.jdbc] (default task-83) SELECT 
ST_AsText(ST_Force2D(ST_Envelope(ST_Extent("the_geom"::geometry FROM 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc"
2022-01-18 20:05:34,029 WARN  [org.hibernate.orm.deprecation] (default task-55) 
HHH9022: Hibernate's legacy org.hibernate.Criteria API is deprecated; use 
the JPA javax.persistence.criteria.CriteriaQuery instead
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) SELECT 
"fid",ST_AsEWKB("the_geom") as 
"the_geom","location","validtime","analysis_time","elevation" FROM 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" WHERE 
0 = 1
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 
the_geom to POLYGON ((47.4749994 19.025, 47.4749994 40.775, 
78.525 40.775, 78.525 19.025, 47.4749994 19.025))
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 0 
to POLYGON ((47.4749994 19.025, 47.4749994 40.775, 78.525 
40.775, 78.525 19.025, 47.4749994 19.025))
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 
location to 
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 1 
to 
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 
validtime to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 2 
to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 
analysis_time to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 3 
to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 
elevation to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 4 
to null
2022-01-18 20:05:34,031 DEBUG [org.geotools.jdbc] (default task-83) Inserting 
new features with ps: INSERT INTO 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" ( 
"the_geom","location","validtime","analysis_time","elevation" ) VALUES ( 
ST_GeomFromWKB(?, 4326),?,?,?,?)
2022-01-18 20:05:34,031 DEBUG [org.geotools.jdbc] (default task-83) 1 =

[Geoserver-users] ImageMosaic JDBC entering in null values for attributes

2022-01-18 Thread Bessette-Halsema, Dominique E via Geoserver-users 
Hello

I'm using ImageMosaic with the JDBC extension.  I found that when GeoServer is 
under heavy load, intermittently the JDBC code will insert null values for the 
attributes.  This causes the WMS getCapabilities to fail with the following 
Warning

WARN  [org.geoserver.wms.capabilities] (default task-91) Error writing 
metadata; skipping layer: AFGHAN-n2-a1.grad_mod_refr.ht_sfc: 
java.lang.NullPointerException

This essentially makes that layer unusable until the database entry is deleted. 
 I extracted the geotools jdbc code where it is setting the values to null.  
What I'm looking for is some insight into why this is happening or a possible 
fix.  Has this issue been documented?

2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83) 
exporting LogicFilter
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83) 
exporting SQL ComparisonFilter
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83) 
exporting PropertyName
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83) 
exporting PropertyName
2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) SELECT 
count(*) FROM 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" WHERE 
("location" = ? AND "location" IS NOT NULL )
2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) 1 = 
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,024 DEBUG [org.geotools.jdbc] (default task-83) SELECT 
"fid",ST_AsEWKB("the_geom") as 
"the_geom","location","validtime","analysis_time","elevation" FROM 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" LIMIT 1
2022-01-18 20:05:34,029 DEBUG [org.geotools.jdbc] (default task-83) SELECT 
ST_AsText(ST_Force2D(ST_Envelope(ST_Extent("the_geom"::geometry FROM 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc"
2022-01-18 20:05:34,029 WARN  [org.hibernate.orm.deprecation] (default task-55) 
HHH9022: Hibernate's legacy org.hibernate.Criteria API is deprecated; use 
the JPA javax.persistence.criteria.CriteriaQuery instead
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) SELECT 
"fid",ST_AsEWKB("the_geom") as 
"the_geom","location","validtime","analysis_time","elevation" FROM 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" WHERE 
0 = 1
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 
the_geom to POLYGON ((47.4749994 19.025, 47.4749994 40.775, 
78.525 40.775, 78.525 19.025, 47.4749994 19.025))
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 0 
to POLYGON ((47.4749994 19.025, 47.4749994 40.775, 78.525 
40.775, 78.525 19.025, 47.4749994 19.025))
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 
location to 
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 1 
to 
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 
validtime to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 2 
to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 
analysis_time to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 3 
to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 
elevation to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 4 
to null
2022-01-18 20:05:34,031 DEBUG [org.geotools.jdbc] (default task-83) Inserting 
new features with ps: INSERT INTO 
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" ( 
"the_geom","location","validtime","analysis_time","elevation" ) VALUES ( 
ST_GeomFromWKB(?, 4326),?,?,?,?)
2022-01-18 20:05:34,031 DEBUG [org.geotools.jdbc] (default task-83) 1 = POLYGON 
((47.4749994 19.025, 47.4749994 40.775, 78.525 40.775, 78.525 
19.025, 47.4749994 19.025))
2022-01-18 20:05:34,031 DEBUG [org.geotools.jdbc] (default task-83) 2 = 
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,031 DEBUG [org.geotools.jdbc] (default task-83) 3 = null
2022-01-18 20:05:34,031 DEBUG [org.geotools.jdbc] (default task-83) 4 = null
2022-01-18 20:05:34,031 DEBUG [org.geotools.jdbc] (default task-83) 5 = null
2022-01-18 20:05:34,049 DEBUG [org.geotools.gce.imagemosaic] (default task-83) 
Done with file

[Geoserver-users] GeoTools ImageMosaic Resource Leak Question

2021-08-19 Thread Bessette-Halsema, Dominique E via Geoserver-users 
Hello

In the method:  
org.geotools.gce.imagemosaic.GranuleDescriptor.loadRaster(ImageReadParam, int, 
ReferencedEnvelope, MathTransform2D, RasterLayerRequest, Hints),

Starting at line 1031, there is a block of code as below:

// eventually gets closed in finally block, if possible (not deferred 
loading)
@SuppressWarnings("PMD.CloseResource")
ImageInputStream inStream = null;
ImageReader reader = null;
boolean cleanupInFinally = request.getReadType() != 
ReadType.JAI_IMAGEREAD;

The cleanupInFinally variable gets set to

  *   true when the request.getReadType() is NOT of ReadType.JAI_IMAGEREAD
  *   false when the request.getReadType() is of ReadType.JAI_IMAGEREAD

The finally block of the method is as below:

finally {
try {
if (cleanupInFinally && inStream != null) {
inStream.close();
}
} finally {
if (cleanupInFinally && reader != null) {
reader.dispose();
}
}
}


When request.getReadType() is of ReadType.JAI_IMAGEREAD and therefore 
cleanupInFinally gets set to false, the inStream and the reader do not get 
closed that would indicate resource leak.

Does the code rely on Garbage Collection to clean up these opened resources?



Dominique Bessette
Senior Software Engineer


___
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