[Geoserver-devel] PSC meetings notes, May 10th 2022

GeoTools / GeoServer PMC meeting - 2022-05-10Attending

   -

   Torben Barsballe
   -

   Stacy Acosta
   -

   Jody Garnett
   -

   Andrea Aime
   -

   Jukka Rahkonen

Actions from prior meetings:

   -

   AA: review Jody’s Log4j PR
   -

   AA: setup HTTPS and www.geoserver.org (AA to talk with SAC)

Agenda

   1.

   GeoServer Domain
   2.

   Build server care and feeding and upgrade
   3.

   GeoServer 2.21-RC
   4.

   GeoServer 2.21.0 release
   5.

   FeatureCollection.query(Query)
   6.

   GeoTools Extra Samples

Actions

   -

   andrea: email devel list for release volunteer
   -

   torben and jody: try and clean up a committed m2 repo

GeoServer Domain

Action follow-up for setup HTTPS and www.geoserver.org (AA to talk with SAC)

   -

   We require zone records to do this - follow-up with Planet again.
   -

   Also would like geowebcache domain

Build server care and feeding and upgrade

   -

   Ran out of disk space, see gitter for troubleshooting
   -

   each workspace is taking 1-2G in space (including doc builds)
   -

   2.21-M0 tag includes an m2 repo - making every git checkout massive
   -

      https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository

      -

      Force push on a tag (so not terrible rewrite of history)
      -

      action: torben and jody to try the above out (breakout session)
      -

   Jody proposed AX101 machine for new build server
   -

      Jeroen and Simone have offered to split costs

New Machine AX101 below proposed:

€65 AX61-NVME <https://www.hetzner.com/dedicated-rootserver/ax61-nvme&gt;

   -

   CPU: AMD Ryzen 3900 12 cores / 24 threads
   -

   RAM: 128 GB DDR4 ECC
   -

   Disk: 2x 1.92 TB NVMe SSD
   -

   Bandwidth: 1 Gbits, Unlimited

€115 SYS-6-SSD-256 <https://www.soyoustart.com/it/offerte/2201sys062.xml&gt;

   -

   CPU: AMD Epyc 7351p 16 cores / 32 threads
   -

   RAM: 256GB DDR4 ECC 2400MHz
   -

   Disk: SoftRAID 2x512GB NVME SSD
   -

   Bandwidth: 250 Mbps Unlimited

€113 AX101 <https://www.hetzner.com/dedicated-rootserver/ax101&gt;

   -

   CPU: AMD 5950X 16 cores / 32 threads
   -

   RAM: 128 GB DDR4 ECC
   -

   Disk: 2x 3.84 TB NVMe SSD
   -

   Bandwidth: 1 Gbits, Unlimited

€136 SYS-7-SSD-128 <https://www.soyoustart.com/it/offerte/2201sys070.xml&gt;

   -

   CPU: AMD Epyc 7451 24 cores / 48 threads
   -

   RAM: 128GB DDR4 ECC 2400MHz
   -

   Disk: SoftRAID 2 x 512GB NVME SSD

   -

   Bandwidth: 250 Mbps Unlimited

€165 AX161 <https://www.hetzner.com/dedicated-rootserver/ax161&gt; (was €131
base + €33 for disk)

   -

   CPU: AMD 5950X 32 cores / 64 threads
   -

   RAM: 128 GB DDR4 ECC
   -

   Disk: 2x 1.92 TB NVMe SSD
   -

   Bandwidth: 1 Gbits

€168 SYS-7-SSD-256

   -

   CPU: AMD Epyc 7451 24 cores / 48 threads
   -

   RAM: 256GB DDR4 ECC 2400MHz
   -

   Disk: SoftRAID 2 x 512GB NVME SSD

   -

   Bandwidth: 250 Mbps Unlimited

GeoServer 2.21-RC

Release Candidate is out
https://geoserver.org/announcements/2022/05/09/geoserver-2-21-RC-released.html

   -

   broken link noticed (new WPS and KML output settings, external output
   directory)
   -

   we want to thank implementer / customer for the final announcement
   -

   please take care with issue FixedFor and provide any indication of what
   was fixed

Asked the user list to test, need some testing please :slight_smile:

This is a really good release, love feature type customization.

GeoServer 2.21.0 release

We need a volunteer
https://github.com/geoserver/geoserver/wiki/Release-Schedule

   -

   This is just a normal release, all the work for new branches is the RC
   -

   Andrea is asking the devel list for a release manager

Round up of known issues:

   -

   Dispatcher is willing to log request body? And the new request header
   settings duplicate this functionality. Joseph is going to make a PR to fix
   before release :slight_smile:
   -

   Anything else? Please test log4j configurations
   -

   A couple hard coded fonts in the UI to cleanup

FeatureCollection.query(Query)

GeoTools has some hooks for optimizations:

   -

   Propose FeatureCollection.query(Query)
   -

   Feature collection has optimizations for Filter, Sort (single
   attribute), …
   -

      intended to be a fluent api for production of an internal query :slight_smile:
      -

   Most of the wrappers are doing one thing in memory, and lose track of
   the query.

Andrea will make a proposal, the goal is the ability to pass
FeatureCollection around.
GeoTiff Extra Samples

GeoTiff extra samples field bug (PR pending)

https://osgeo-org.atlassian.net/browse/GEOT-6452

Stacy working on creating a test case

The only currently available data source that reflects the issue is
internal proprietary data and not suitable for inclusion in a test case.

Consider using gdal_create can often be used for creating a test file that
is alike from the essential parts but with dummy contents

https://gdal.org/programs/gdal_create.html

An “easy” method would be to use option -if for "input file" to copy the
structure of a source file

The extra samples flag is a Tiff tag - we could also use -mo
{TAGNAME}=VALUE to add a TIFFTAG_EXTRASAMPLES tag to a test file manually.

EULA sent to jody, he could agree to access the sample data, and then
process as above.

Would that be sufficient for the Planet team? The new file would only
contain the tiff tags …

The issue appears to be due to the pixel data, rather than just the
metadata.

Extra pixel with RGB information, not part of A, extra data that must be
present and remain 0 (not part of RGB / A).

Follow-up on the prior discussion as to location of the fix - it actually
needs to be in imageio-ext
Chit Chat

Niels proposal is stuck:

   -

   Has two options, get a signed CLA, or proceed without one (the module
   then has some more restrictions as found code). Not a big deal …

Code sprint?

   -

   Bolsena! Invitation is open :slight_smile:

   -

   Want to do a CITE sprint? or rebook CITE sprint … (was proposed as thurs
   for a month)
   -

      Blocked on build server …

GeoConnections:

   -

   Opportunity sent to email list by Peter Rushforth, good candidate for
   ogcapi, MapML, …

Java 11 as the minimum supported version?

   -

   Some concerns …
   -

      Java 8 lasts longer 2026 :slight_smile:
      -

      Java 11 lasts until Java 2024
      -

      Java 17 lasts until 2026
      -

      Jakarta? Adjacent concern …
      -

      ImageN - may needed for Java 17 (replacing JAI)
      -

   Many libraries already switching to Java 11 minimum
   -

      Wicket, google libraries, etc …
      -

      Spring framework is hanging back at Java 8
      -

   Expect we will need to do this this year …
   -

      Propose switching 2.22.x in september
      (so main will would be switching .. now)