[Geotools-devel] GeoTools PMC Meeting 2024-06-04

[Jody Garnett]

GeoTools / GeoServer PMC meeting - 2024-06-04Attending

   -

   Torben Barsballe
   -

   Jody Garnett
   -

   Jukka Rahkonnen
   -

   Dave Blasby
   -

   Peter Smythe
   -

   Andrea Aime


Actions from prior meetings:

   -

   N/A

Agenda

   -

   GeoTools Build Failure
   -

   Release Planning
   -

   Community modules assembly rework
   -

   Roadmap/Sprint planning

Actions

   -

   Team: (Done) Look at GeoTools build failure
   -

   Jody: (Done) Add Ticket/Release notes for Javadoc Java version
   requirements
   -

   Jody: To review Community modules assembly rework
   -

   Jody: Ask brad about A/B testing, and if modal dialog is a blocker
   -

   Jody: (Done) Andrea nominated for ImageN

GeoTools Build Failure

The javadoc:aggregate is failing a bit (sigh) not sure why.

assembly.yml succeeds

  mvn -B -DskipTests -Dfmt.skip=true javadoc:aggregate --file
modules/pom.xml

build-release.sh fails

build-release.sh fails:

  echo "building javadocs"

  pushd modules > /dev/null

  mvn $MAVEN_FLAGS -Dfmt.skip=true -DskipTests javadoc:aggregate

build server:
mvn -f modules/pom.xml -Djava.awt.headless=true
-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn
-Dmaven.repo.local=/var/lib/jenkins/workspace/geotools-main/.repository
javadoc:aggregate --batch-mode -Dspotless.apply.skip=true
-Dmaven.repo.local=m2

mvn -f modules/pom.xml javadoc:aggregate -Dspotless.apply.skip=true



Updated default maven to 3.9.7

   -

   This doesn’t seemed to have worked (though maybe jenkins needs a restart
   to pick up the environment change - will test that later)
   -

   Note, you can still configure and set custom maven versions through tools
   & tool settings <https://build.geoserver.org/manage/configureTools/> >
   Switching to the existing 3.9.5 install; also failed


Update updating Java from 11.0.4 to 11.0.22 and newer are working!

   -

   This is worth release notes!
   -

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

Release Planning

Release planning:

   -

   2.24.4 Peter / maintenance release
   -

   2.25.2 Jody / stable release (early release offered)

Community modules assembly rework

nice! refactor andrea!

   -

   motivation is azure and s3 having conflict over dependency versions
   -

   refactor so each module has its own assembly!


tour: https://github.com/geoserver/geoserver/pull/7710

updated build instructions:
https://github.com/geoserver/geoserver/blob/d012557bd1085ed46e2fc694a7ce7e18bf0a8ac0/src/community/README.md


action:

   -

   jody: to review (thanks for this work Andrea)


Roadmap/Sprint planning

So about roadmap stuff:

   -

   Jody has not had time to write an updated blog post (activities ready to
   work)
   -

   Do not see a common event/sprint to attend
   -

  Any opportunity to organize our own?


Problem with PRs landing large changes:

   -

   Wicket 9 update (brad) ← this is the next priority
   -

  GeoCat offers in-kind A/B testing when ready
  -

  Brad asked for help with an “modal dialog”
  -

 Option to suppress deprecation warnings, put off until Wicket 10?
 -

   PMD 7 update (mprins started), very large PR in need of assistance
   -

   mkdocs (jody will return in July for this one and ask for help then)


Actions:

   -

   jody: Ask brad about A/B testing, and if modal dialog is a blocker
   -

   jody (done): Andrea nominated for ImageN


Chit Chat

   -

   GeoTools build troubleshooting (fun and games)
   -

   David had a GeoPackage PR - it is good to merge
   -

   OGC API Feat Part 3 (Filter and CQL2) are approved in the OGC member
   voting - now we just need funding! And CITE tests…
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Set HTTP proxy for XML SchemaCache

[Jody Garnett]

That is … amazing you can get in there and make the change. Wow.

For normal XML parsing does it use the cache?



--
Jody Garnett


On Fri, May 31, 2024 at 2:22 AM Cécile Vuilleumier <
cecile.vuilleum...@camptocamp.com> wrote:

> Hi all
>
> This is a follow-up to: https://osgeo-org.atlassian.net/browse/GEOT-7576
> (Make SchemaCache use the HttpClient from the GeoTools hints)
>
> The goal would be to be able to configure an HTTP proxy for XML schema
> requests using the GeoTools hint HTTP_CLIENT_FACTORY (similarly to OWS
> requests). If not set the fallback would be the SimpleHttpClient.
>
> I have been looking at the code and it seems doable, although the
> SchemaCache does something special in order to follow HTTP redirections. An
> option could be to move this to the SimpleHttpClient GET method or to
> overload this method.
> (Note that after testing it seems HttpURLConnection does already follow
> redirects but only if they have the same protocol e.g. HTTP or HTTPS)
>
> Would you be in favor of this change? Any comments about the
> implementation?
>
> Thanks in advance, Cécile
>
> --
> *camptocamp*
>
>
> *Cécile Vuilleumier *
> Geospatial developer
> www.camptocamp.com
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Could I get more GitHub permissions?

[Jody Garnett]

I think you have been a committer previously David,  but we cleaned up
inactive accounts a couple years back.

I don’t think the project guidelines have changed much:
https://docs.geotools.org/latest/developer/roles/contributor.html

The key thing is don’t break the build.

+1 from me, but as your friend and coworker I will ask another PMC member
to speak up also.
--
Jody Garnett


On Tue, May 28, 2024 at 4:21 PM David Blasby  wrote:

> Hi,
>
> I've been working in the GT codebase and I'd like to have a bit more
> permission.  I cannot re-run failed builds and I cannot ask for PR reviews.
>
> Thanks a lot,
> Dave
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] GeoTools PMC meeting notes, May 21 2024

[Jody Garnett]

GeoTools / GeoServer PMC meeting - 2024-05-21Attending

   -

   David Blasby
   -

   Peter Smythe
   -

   Jody Garnett
   -

   Jukka Rahkonen


Actions from prior meeting:

   -

   [DONE] Jody: Make a ticket about GROUP_ADMIN not having permission to
   create a new user (GEOS-10938
   <https://osgeo-org.atlassian.net/browse/GEOS-10938>)
   -

   [DONE] Jody: Make a ticket on clean up of admin roles and constants (
   GEOS-11389 <https://osgeo-org.atlassian.net/browse/GEOS-11389>)
   -

   [DONE] Jody: Open a ticket to refine Demo Page Javascript rewrite (
   GEOS-11390 <https://osgeo-org.atlassian.net/browse/GEOS-11390>)


Agenda:

   -

   repo.osgeo.org maintenance
   -

   build status
   -

  Why do checks fail, what is the process to handle failures?
  -

  Dependabot https://github.com/geoserver/geoserver/pull/7637 process?
  -

   release status
   -

   discourse migration
   -

   Clean up old branches, keeping 2.2.x, ones with open PRs?
   -

   TestWFSPost servlet removal (replace w/ 100% JS).  Demo Request, WCS
   Request, WPS Request
   -

   mkdocs


repo.osgeo.org maintenance

Upgrade Nexus to v3.68.1 for CVE-2024-4956:

   -

   Asked to reset gsbuild user (done)
   -

  contacted torben, updated build.geoserver.org settings.xml
  -

   Asked to reset gsdocker user
   -

  contacted wesk...@terrestris.de ?


   -

   See: https://trac.osgeo.org/osgeo/ticket/3189

build status

Q: Why do checks fail, what is the process to handle failures?

   -

   Jody broke last week (did not run -DQA checks when backporting using
   cherry-pick)
   -

  Had to close and open backports to “rebase” effectively
  -

   Checks that are needed across projects (geotools api change; that needed
   a geoserver
   -

   For intermittent failures
   -

  Quick: rerun failed test …
  -

  Why: Each example needs investigation
  -

 windows locked file is a common failure with older file system?
 -

 Perhaps some state changed (environmental variable) that affects
 another test…
 -

 Perhaps opening a port → randomise the port used (minimise error)


Thanks Andrea for fixing build (twice) recently.

About backports:

   -

   Yes - if we can (example dependabot)
   -

   New functionality?
   -


  https://docs.geoserver.org/latest/en/developer/policies/pull_request.html
  If the new feature is suitable for backport, you may ask on the
  developer list after a 1 month.
  -

  Q: Add this to CONTRIBUTING.md also?


Dependabot https://github.com/geoserver/geoserver/pull/7637  process?
release status

Delayed: Waiting on PR reviews and build stability

PRs:

   -

   https://github.com/geotools/geotools/pull/4773 Geometry type mismatch in
   WFS 1.1.0
   -

   version updates of stuff? Some from GeoTools…

discourse migration

This is ready to move

   -

   Marketing committee made the change, can see their instructions
   -

   We need similar instructions in our docs, and then inform the user-list

Clean up old branches, keeping 2.y.x, ones with open PRs?

In general we keep in case people need an emergency patch

   -

   We can see examples where release are made for archived releases


Stale PRs get removed, with the idea that the branch is there if anyone
wishes to recover the work. So deleting the branch may not be kind?

Stale working branches?

   -

   Developers should remove when activity is complete
   -

   It would be nice to clean these up, I do not know of anything automatic
   -

   Ones with “stale” PRs may be worth keeping?
   -

   Some from big refactors are useful to keep (example refactor code sprint)
   Perhaps these could be placed in to a folder?



TestWFSPost servlet removal (replace w/ 100% JS).  Demo Request, WCS
Request, WPS Request

Positive response, nice work David.

Peter had feedback on workflow and button order consistency between Demo
Request page, WPS Builder, WCS Builder.


   -

   https://github.com/geoserver/geoserver/pull/7672
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Gradle Project problems including gt-main

[Jody Garnett]

 The binary download of geotools includes an example program with
instructions for running int he README (so it is possible to use without
maven).
Does gradle handle transitive dependencies?

Checking GeoServer in IDE the Unit class is defined in unit-api-2.1.2.jar


--
Jody Garnett


On May 14, 2024 at 1:33:05 AM, Sara Schade 
wrote:

> Hi all,
>
> is there a known solution to integrate GeoTools correctly in a Gradle
> project? At the moment we are going from one dependency error during run to
> the next. At the moment we are stuck here:
>
> Caused by: java.lang.ClassNotFoundException: javax.measure.Unit
>
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
>
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
>
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525)
>
> We have a composite build
> and our dependencies are:
>
> implementation 'org.geotools:gt-main:30.2'
>
> implementation 'org.geotools:gt-referencing:30.2'
>
> implementation 'org.geotools:gt-epsg-wkt:30.2'
>
> implementation 'org.geotools:gt-api:30.2'
>
> api 'org.locationtech.jts:jts-core:1.19.0'
>
> implementation 'org.geotools:gt-epsg-hsql:30.2'
>
> implementation 'org.geotools:gt-epsg-extension:30.2'
>
> implementation 'org.geotools:gt-metadata:30.2'
>
> implementation 'javax.media:jai_core:1.1.3'
>
> implementation 'org.geotools:gt-coverage:30.2'
>
> implementation 'org.geotools:gt-coverage-api:30.2'
>
> implementation 'org.geotools:gt-geotiff:30.2'
>
> implementation 'org.geotools:gt-shapefile:30.2'
> thank you.
> Best regards Sara
>
> --
> 
> Sara Schade
> Dipl.-Geol., Senior Scientist
> INSIGHT
> Geologische Softwaresysteme GmbH
> Tel.: 0176-21428186
> 
>
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] GeoTools PMC meeting 2024-05-07

[Jody Garnett]

GeoTools / GeoServer PMC meeting - 2024-05-07Attending

   -

   David Blasby
   -

   Peter Smythe
   -

   Jody Garnett
   -

   Andrea Aime


Actions from prior meeting:

   -

   [DONE] Jody: Make a PR for GSIP 224
   <https://github.com/geoserver/geoserver/wiki/GSIP-224>
   -

   [DONE] Peter: Make a similar proposal for GeoTools
   -

   [DONE] Jody: Make a Proposal for geoserver-users transition to discourse


Agenda:

   -

   GSIP-224 - Individual contributor clarification
   <https://github.com/geoserver/geoserver/wiki/GSIP-224>
   -

   GSIP-223 - Community module graduation, amending generality rule
   <https://github.com/geoserver/geoserver/wiki/GSIP-223>
   -

   GSIP-222 - Promote Raster Attribute Table module to extension
   <https://github.com/geoserver/geoserver/wiki/GSIP-222>
   -

   GSIP-225 - Migrate geoserver-users from SourceForge to discourse
   <https://github.com/geoserver/geoserver/wiki/GSIP-225>
   -


   
https://github.com/geotools/geotools/wiki/Individual-contributor-clarification
   -

   Security roles internals
   -

   Record of meeting minutes


Actions:

   -

   Jody: Make a ticket about GROUP_ADMIN not having permission to create a
   new user (GEOS-10938 <https://osgeo-org.atlassian.net/browse/GEOS-10938>)
   -

   Jody: Make a ticket on clean up of admin roles and constants (GEOS-11389
   <https://osgeo-org.atlassian.net/browse/GEOS-11389>)
   -

   Jody: Open a ticket to refine Demo Page Javascript rewrite (GEOS-11390
   <https://osgeo-org.atlassian.net/browse/GEOS-11390>)


GSIP-224 - Individual contributor clarification

https://github.com/geoserver/geoserver/wiki/GSIP-224

   -

   Is this done? yes

GSIP-223 - Community module graduation, amending generality rule

https://github.com/geoserver/geoserver/wiki/GSIP-223

No PR, Jody made a PR? Can we merge …

   -

   https://github.com/geoserver/geoserver/pull/7603 done
   -

   Does this need backport? Probably not since we only publish from main …


GSIP-222 - Promote Raster Attribute Table module to extension

https://github.com/geoserver/geoserver/wiki/GSIP-222

What is the status?

   -

   Proposal was not completed by the time the release window…
   -

   Not sure if this is merged can we check? Yes …
   -

   2.25 and main!
   -

   Updated Proposals <https://github.com/geoserver/geoserver/wiki/Proposals>
   page to indicate this is complete


GSIP-225 - Migrate geoserver-users from SourceForge to discourse

https://github.com/geoserver/geoserver/wiki/GSIP-225

   -

   Proposal was made, and approved


What happens next:

   -

   user list to discourse is a go, we will wait on SAC for the change
   -

   Expected some kind of PR for the website to provide instructions
   -

   Then notify users of the change
   -

   Proposal has shutting down the SF list after 1 month, and migrate any
   additional messages over


See proposal for details …

Encouragement from mastodon:
https://fosstodon.org/@geoserver/112367510772585467

GeoTools proposal for individual contributors

https://github.com/geotools/geotools/wiki/Individual-contributor-clarification

50% response rate …

   -

   Torben is away so assume +0
   -

   No objections
   -

   Likely to pass on May 9th :D


Could probably safely start the PR 
Security roles internals

Email questions

   -

   Hard to talk about due to naming “role_admin” “admin”
   “role_administrator”
   -

   Sometimes objects, sometimes strings


ROLE_ADMINISTRATOR

   -

   This is for the user interface, it unlocks the data admin console screens


ADMINISTRATOR

   -

   This is the “root” kind of access, often used for the REST API
   -

   Unlocks all the admin console for all the screens


GROUP_ADMIN

   -

   Unlocks the security admin console screens


The rest.properties is parsed:

   -

   The constants from GeoServerRole.java
   
<https://github.com/geoserver/geoserver/blob/main/src/main/src/main/java/org/geoserver/security/impl/GeoServerRole.java>
   define the role objects


GeoServerRole ADMIN_ROLE = new GeoServerRole("ROLE_ADMINISTRATOR");

GeoServerRole GROUP_ADMIN_ROLE = new GeoServerRole("ROLE_GROUP_ADMIN");

GeoServerRole AUTHENTICATED_ROLE = new GeoServerRole("ROLE_AUTHENTICATED");

GeoServerRole ANY_ROLE = new GeoServerRole("*");

GeoServerRole ANONYMOUS_ROLE = new GeoServerRole("ROLE_ANONYMOUS");


The
https://github.com/geoserver/geoserver/blob/main/data/release/security/rest.properties
file is parsed:

/**;GET=ADMIN

/**;POST,DELETE,PUT=ADMIN

Parsed by AbstractGeoServerSecurityService.java
<https://github.com/geoserver/geoserver/blob/main/src/main/src/main/java/org/geoserver/security/impl/AbstractGeoServerSecurityService.java>
:

   -

   Has its own contents …

String DEFAULT_NAME = "default";

String DEFAULT_LOCAL_ADMIN_ROLE = "ADMIN";

String DEFAULT_LOCAL_GROUP_ADMIN_ROLE = "GROUP_ADMIN"

Re: [Geotools-devel] Investigating new SQLDialect for Apache Pinot (gt-jdbc-pinot)

[Jody Garnett]

 Hello Robert,

It has been some time since you attended our meeting, how is your
development going?
--
Jody Garnett


On Apr 3, 2024 at 5:27:39 PM, Robert Zych via GeoTools-Devel <
geotools-devel@lists.sourceforge.net> wrote:

> Hello GeoTools!
>
>
>
> I’m investigating the feasibility and level of effort required to add
> support for Apache Pinot <https://pinot.apache.org/>. I have reviewed the
> Internals
> <https://docs.geotools.org/latest/userguide/library/jdbc/internal.html> page
> and I’m reviewing the reference implementation (gt-jdbc-h2) now.
>
>
>
> Thank you for any additional documentation, support, and interest.
>
>
>
>
>
> *Robert Zych*
>
> Raft <https://goraft.tech/> | Software Engineer
>
> E: rz...@teamraft.com
>
> [image: A picture containing font, graphics, logo, graphic design
> Description automatically generated]
>
> [image: A picture containing font, text, graphics, screenshot Description
> automatically generated]
>
> IL6 Edge2Enterprise Datamesh
> Enabled 12+ Software Factories
>
>
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Possible bug in KML Export

[Jody Garnett]

 Hi Bruno,

The lml format is not very active these days, I am trying to determine why
others have not run into this problem - does your PostGIS table have a
generic "Geometry" type (rather thank Point, or Polygon, or
MultiLineString?)

You would be implementing a new feature, so it would be good to confirm the
abilities of the KML standard, and be sure to include a test case :D
--
Jody Garnett


On Apr 26, 2024 at 6:47:09 AM, Bruno Lombardi 
wrote:

> Hi,
>
> I've found some difficulty exporting Feature to KML.
>
> Here's my piece of code:
>
> Encoder encoder = new Encoder(new FCKMLConfiguration());
> encoder.setIndenting(true);
> PipedInputStream in = new PipedInputStream();
> try {
> PipedOutputStream out = new PipedOutputStream(in);
> new Thread(new Runnable() {
> public void run() {
> try {
> encoder.encode(polyFeatures, KML.kml, out);
> } catch (IOException e) {
> log.error("", e);
> } finally {
> try {
> out.close();
> } catch (IOException e) {
> log.error("", e);
> }
> after.run();
> }
> }
> }).start();
> } catch (IOException e) {
> log.error("Problem generating export", e);
> }
> return in;
>
> All works correctly but, if feature contains a "multigeometry" retrieved
> from PostGIS data base, the KML entry is empy:
>
> 
>
> I've changed the MultiGeometryTypeBinding in this way:
>
> @Override
>
> public Object getProperty(Object object, QName name) throws Exception {
> GeometryCollection gc = (GeometryCollection) object;
> if ("AbstractGeometryGroup".equals(name.getLocalPart()) ||
> KML.Geometry.getLocalPart().equals(name.getLocalPart())) {
> Geometry[] g = new Geometry[gc.getNumGeometries()];
> for (int i = 0; i < g.length; i++) {
> g[i] = gc.getGeometryN(i);
> }
> return g;
> }
> return super.getProperty(object, name);
> }
>
> It works! I don't know if the change is correct since I do not know so
> deeply the code but, if it make sense I would do a pull_request for the
> change.
>
> Thanks for you fantastic works!
>
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Individual Contributor clarification

[Jody Garnett]

+1 thanks

--
Jody Garnett


On Thu, Apr 25, 2024 at 4:08 AM Peter Smythe  wrote:

> Following in the footsteps of GeoServer's GSIP-224, here is a similar
> proposal for GeoTools for the PMC to vote on please:
>
>
> https://github.com/geotools/geotools/wiki/Individual-contributor-clarification
>
> Proposed text, updating
> https://docs.geotools.org/latest/developer/procedures/contribution_license.html
> :
>
> All new contributors
>> <https://docs.geotools.org/latest/developer/roles/contributor.html> will
>> be required to grant copyright to the foundation using a Contributor
>> Licenses <https://www.osgeo.org/about/licenses/>:
>
>
>-
>
>individual_contributor
><https://www.osgeo.org/resources/individual-contributor-license/>
>
>-
>
>corporate_contributor
><https://www.osgeo.org/resources/corporate-contributor-license/>
>
>
> GeoTools is grateful that organizations of all shapes and sizes support
> our project with in-kind participation of their employees. Extending commit
> access is made to individuals directly based on their expertise
> demonstrated over time.
>
>
> Voting:
>
>- Andrea Aime:
>- Ian Turton:
>- Jody Garnett:
>- Nuno Oliveira:
>- Simone Giannecchini:
>- Torben Barsballe:
>
>
> Peter
>
> GeoServer PSC
> AWS Solutions Architect
> https://github.com/petersmythe
>
>
> On Wed, 10 Apr 2024 at 06:13, Jody Garnett  wrote:
>
>> Proposal for discussion
>> https://github.com/geoserver/geoserver/wiki/GSIP-224
>>
>> New text proposed for
>> https://docs.geoserver.org/latest/en/developer/policies/committing.html
>>  page:
>>
>> All contributors are asked to provide an assignment agreement for working
>> on the project:
>>
>>
>>- individual_contributor
>>   <https://www.osgeo.org/resources/individual-contributor-license/>
>>   - Individual contributor agreement.
>>
>>
>>
>>- corporate_contributor
>>   <https://www.osgeo.org/resources/individual-contributor-license/>
>>   - Corporate contributor agreement to authorize employees to work
>>   on project. May also be used as a software grant to donate software to 
>> the
>>   project.
>>
>>
>> GeoServer recognizes that organizations of all shapes and sizes support
>> our project with in-kind participation of their employees. Extending commit
>> access is made to individuals directly based on their expertise
>> demonstrated over time.
>>
>>
>> Thanks!
>> --
>> Jody Garnett
>> ___
>> Geoserver-devel mailing list
>> geoserver-de...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] GeoTools PMC Meeting notes April 23 2024

[Jody Garnett]

GeoTools / GeoServer PMC meeting - 2024-04-23Attending

   -

   Torben Barsballe
   -

   Andrea Aime
   -

   Jody Garnett
   -

   Jukka Rahkonnen
   -

   Peter Smythe


Actions from prior meetings:

   -

   [DONE] Andrea: send an email for the release manager
   -

   [DONE] (no response yet) Jody: Reach out to Jo Cook (Astun) regarding
   core contributor status
   -

   [DONE] Jody: Propose adjustments to contributor policy requiring
   interaction on an individual (not organization) level

Agenda

   -

   Crazy issue with Azure blobstore, and how to prevent it
   -

   GRIB backwards compatibility broken (with silver lining)
   -

   Mkdocs conversion getting it moving again
   -

   GSIP 224 discussion
   -

   Roadmap communication and chit-chat

Actions

   -

   Jody: Make a PR for GSIP 224
   <https://github.com/geoserver/geoserver/wiki/GSIP-224>
   -

   Peter: Make a similar proposal for GeoTools
   -

   Jody: Make a PR for geoserver-users transition to discourse


Crazy issue with Azure blobstore, and how to prevent it

GWC Report makes a massive amount of requests
<https://github.com/GeoWebCache/geowebcache/issues/1149> to Azure blob
store:

   -

   Deleting a layer / gridset resulted in an infinite loop due to a …
   jackson upgrade resulting in a regression
   -

   API uses JSON, we use jackson to parse the JSON including the token to
   page through results … and token was null when reaching the end
   -

   Jackson upgrade changed null to empty string, so infinite loop


Can we run tests?

   -

   There is a cost (paid account), but for an infinite loop this would be
   expensive …


   -

   emulator + client library are a matched set
   -

   so we need to migrate to newer client library to make use of the API
   -

   Azure / S3 / etc… all have this lack of infrastructure to test against
   problem


There is a public ticket here, but has not attracted interest / fix…

   -

   33000 requests per min is expensive!
   -

   Fix was to check for empty string


This is a good example of where the PSC can ask for funding?

   -

   Would have to set a hard limit of build server use (for each day a
   specific number of calls etc…)
   -

   This is also an example of shared risk, someone found the 33000 requests
   per min and reported it (so it was available for others to see and work on).
   -

   So we could estimate the cost to setup a “cloud infrastructure” testing …




GRIB backwards compatibility broken (with silver lining)

   -

   Follow on to this from a few meetings ago …
   -

   Manual upgrade process documented
   
<https://docs.geoserver.org/latest/en/user/installation/upgrade.html#grib-layers-geoserver-2-26-and-newer>
   (also for GeoTools
   <https://docs.geotools.org/latest/userguide/welcome/upgrade.html>)…
   -

  Can kind of guess and rewrite the variable names
  -

  But the time format changes so still some risk..
  -

  We do expect time format to change once again (hopefully before
  September release cycle)
  -

   With all this … success we are now on a supported version netCDF library
   -

  Quite a bit faster (example 20x), especially on a network …

mkdocs conversion getting it moving again

   -

   Jody is back from travel and available to work on this again
   -

   available on pypi: https://pypi.org/project/mkdocs-translate/0.4.0/
   -

   tested by Andrea, can make it run, however breaking on pandoc
   -

  jody is using pandoc 3.1.7 (installed via homebrew)
  -

 latest is 2 weeks ago: pandoc 3.1.13 (pip only has up to 2.3, Mint
 up to 2.9)
 -

   GeoCat will provide a tester to help with the remaining A/B testing


Examples of the kind of RST fixes to expect:

   -

   closed: https://github.com/geoserver/geoserver/pull/7429 applied fixes
   (yet to be backported)
   -

   open: https://github.com/geoserver/geoserver/pull/7462 pending rst fixes

GSIP 224 discussion

GSIP 224 clarification about be grateful to companies (while explaining
that commit access is extended to individuals):

GeoServer is grateful that organizations of all shapes and sizes support
our project with in-kind participation of their employees. Extending commit
access is made to individuals directly based on their expertise
demonstrated over time.

Proposal is approved

   -

   Jody will take an action to make a PR for GSIP224
   -

   Peter to make a similar proposal for GeoTools


Roadmap communication and chit-chat

2024 Q1: https://geoserver.org/behind%20the%20scenes/2024/01/03/roadmap.html

https://github.com/geoserver/geoserver/wiki/Maintenance-%26-Roadmap

2024 Q2: jody is considering making another news announcement.

   -

   goal would be to emphasis the in-kind contributions / commitment
   -

   any progress…
   -

   fundraising progress … not very much sadly



Q: What roadmap items can be worked on now?

   -

   As spring-framework upgrade is “stuck” pending fun

Re: [Geotools-devel] Deployment of Javadocs

[Jody Garnett]

It may just be adding stuff to the pom.xml? The release scripts just call
maven deploy at some point

--
Jody Garnett


On Tue, Mar 26, 2024 at 9:28 AM Roar Brænden 
wrote:

> Hi,
>
> Thanks for the answer. I have also been using the IDE in the past. Now I'm
> looking into something new, were a pre-generated javadoc jar could be
> beneficial. I would have a look at the release scripts to see if I can
> figure it out myself.
>
> Hilsen Roar
>
> 26. mar. 2024 kl. 09:03 skrev Jody Garnett :
>
> No special reason, I think IDEs are happy enough downloading source (and
> generating javadoc tooltios as required).
>
> I you would find it useful it would be fine to update the release scripts
> (which are in versions control).
>
> --
> Jody Garnett
>
>
> On Tue, Mar 26, 2024 at 8:55 AM Roar Brænden 
> wrote:
>
>> Hi,
>>
>> Recently I've been looking at Javadocs, and I see that there are no
>> -javadoc.jar at the Maven repository repo.osgeo.org for Geotools
>> artifacts. I see from the web site that they are downloadable from
>> sourceforge.net as a zip-file, but for me it seems more obvious to
>> download it with Maven from a repository.
>>
>> Is there a reason why these aren't published to the repository when
>> releasing a new project?
>>
>> Best regards,
>> Roar Brænden
>>
>> ___
>> GeoTools-Devel mailing list
>> GeoTools-Devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
>
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Deployment of Javadocs

[Jody Garnett]

No special reason, I think IDEs are happy enough downloading source (and
generating javadoc tooltios as required).

I you would find it useful it would be fine to update the release scripts
(which are in versions control).

--
Jody Garnett


On Tue, Mar 26, 2024 at 8:55 AM Roar Brænden 
wrote:

> Hi,
>
> Recently I've been looking at Javadocs, and I see that there are no
> -javadoc.jar at the Maven repository repo.osgeo.org for Geotools
> artifacts. I see from the web site that they are downloadable from
> sourceforge.net as a zip-file, but for me it seems more obvious to
> download it with Maven from a repository.
>
> Is there a reason why these aren't published to the repository when
> releasing a new project?
>
> Best regards,
> Roar Brænden
>
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] GeoServer/GeoTools PMC Meeting at 18:30 CET / 10:30 PDT tomorrow

[Jody Garnett]

I am at OGC meeting today but will attend for a bit if available.

Thanks to the team making the release and CVE processing.

--
Jody Garnett


On Tue, Mar 26, 2024 at 6:11 AM Torben Barsballe 
wrote:

> Reminder that the next PMC meeting is scheduled for tomorrow, March 26, at
> 18:30
> <https://www.timeanddate.com/worldclock/fixedtime.html?year=2024=3=26=18=30=0=GeoTools%20/%20GeoServer%20Meeting=1=1=215>
>  CET.
>
> We're still out of sync with Daylight Savings, so this will once again be
> at *10:30am* instead of 9:30am PDT for the North American folks.
>
> You can join the meeting by following this link:
> https://meet.osgeo.org/GeoServerMeeting
>
> Also, I'm not going to be able to make the meeting this week.
>
> Cheers,
> Torben
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Running geotools Quickstart without Maven

[Jody Garnett]

Those are for raster support, the rendering engine gt-render can draw
rasters as well, and assume the many of the it.GeoSolutions plugins to hand
geospatial rasters are available

--
Jody Garnett


On Fri, Mar 1, 2024 at 5:25 AM Amirhossein Nikfal 
wrote:

> I could run the Quickstart application
> <https://docs.geotools.org/latest/userguide/tutorial/quickstart/maven.html>
> without using Maven. My purpose was to get an understanding of what was
> going on.
>
> Maven's dependency tree shows 97 modules for this application. However,
> with only 22 ones out of these 97 modules, the application could be run
> perfectly without any issue. So 75 modules seemed to be not-required. Among
> them, there were 37 modules from *it.geosolutions*, 12 modules from
> *org.geotools*, 7 modules from *com.google*, and many other unnecessary
> modules.
>
> It would be appreciated if you clarify this for me.
>
> On Tue, Feb 27, 2024 at 5:50 PM Ian Turton  wrote:
>
>> If you use maven it walks the dependency tree and finds all the jars it
>> needs.
>>
>> Ian
>>
>> On Tue, 27 Feb 2024, 14:10 Amirhossein Nikfal, 
>> wrote:
>>
>>> Yes, the problem was due to the missing of apache.commons.lang3. Thank
>>> you very much.
>>>
>>> But how could I know about this dependency before the compilation?
>>> Neither in the pom file, nor in the contents of the jar file
>>> (gt-swing-31-SNAPSHOT.jar), there was no name regarding
>>> apache.commons.lang3. Also "*mvn dependency:tree
>>> -Dincludes=org.geotools:gt-swing:**" could not be helpful.
>>>
>>> Best,
>>> Amir
>>>
>>> On Fri, Feb 23, 2024 at 4:37 PM Ian Turton  wrote:
>>>
>>>> it looks like you haven't added (at least) the apache.commons.lang3
>>>> jar. This is what maven excels at so you should probably let it do it's
>>>> magic rather than trying to muddle along with out it.
>>>>
>>>> Ian
>>>>
>>>> On Fri, 23 Feb 2024 at 14:49, Amirhossein Nikfal 
>>>> wrote:
>>>>
>>>>> The short code below can be compiled and run successfully, but *after
>>>>> loading the shapefile*, shows error in line: FileDataStore store =
>>>>> FileDataStoreFinder.getDataStore(file);
>>>>>
>>>>> This is the way I compile and run it:
>>>>> java -d . Quickstart.java
>>>>> java org.geotools.tutorial.quickstart.Quickstart
>>>>>
>>>>> Code:
>>>>> package org.geotools.tutorial.quickstart;
>>>>>
>>>>> import java.io.File;
>>>>> import org.geotools.api.data.FileDataStore;
>>>>> import org.geotools.api.data.FileDataStoreFinder;
>>>>> import org.geotools.swing.data.JFileDataStoreChooser;
>>>>>
>>>>> public class Quickstart {
>>>>> public static void main(String[] args) throws Exception {
>>>>> File file = JFileDataStoreChooser.showOpenFile("shp", null);
>>>>> if (file == null) {
>>>>> return;
>>>>> }
>>>>> FileDataStore store = FileDataStoreFinder.getDataStore(file);
>>>>> }
>>>>> }
>>>>>
>>>>> The errors:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *Feb 23, 2024 3:31:29 PM org.geotools.api.data.FileDataStoreFinder
>>>>> getDataStoreWARNING: Could not aquire ESRI(tm) Shapefiles
>>>>> (*.shp):java.lang.NoClassDefFoundError:
>>>>> org/apache/commons/lang3/SystemUtilsjava.lang.NoClassDefFoundError:
>>>>> org/apache/commons/lang3/SystemUtilsat
>>>>> org.geotools.data.shapefile.files.ShpFiles.init(ShpFiles.java:189)
>>>>> at org.geotools.data.shapefile.files.ShpFiles.(ShpFiles.java:147)
>>>>> at
>>>>> org.geotools.data.shapefile.ShapefileDataStoreFactory.createDataStore(ShapefileDataStoreFactory.java:260)
>>>>>   at
>>>>> org.geotools.data.shapefile.ShapefileDataStoreFactory.createDataStore(ShapefileDataStoreFactory.java:417)
>>>>>   at
>>>>> org.geotools.api.data.FileDataStoreFinder.getDataStore(FileDataStoreFinder.java:78)
>>>>>   at
>>>>> 

Re: [Geotools-devel] Starting release train for GeoTools 31-RC

[Jody Garnett]

 Release artifacts for your testing enjoyment:
https://build.geoserver.org/view/release/job/geotools-release/118/artifact/build/release/distribution/31-RC/
--
Jody Garnett


On Mar 1, 2024 at 3:58:17 PM, Jody Garnett  wrote:

> Release train for GeoTools 31-RC! I collected a few of the PRs that have
> come in (example [GEOT-7538] Use gt-http logging for request/response
> <https://github.com/geotools/geotools/pull/4676> just in time).
>
> The new 31.x branch is created, although build jobs will take some time to
> settle.
>
> Have a great weekend everyone.
> --
> Jody Garnett
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] Starting release train for GeoTools 31-RC

[Jody Garnett]

Release train for GeoTools 31-RC! I collected a few of the PRs that have
come in (example [GEOT-7538] Use gt-http logging for request/response
<https://github.com/geotools/geotools/pull/4676> just in time).

The new 31.x branch is created, although build jobs will take some time to
settle.

Have a great weekend everyone.
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Pre-proposal discussion: adding alpha to ChannelSelection

[Jody Garnett]

 Sounds good Andrea, I look forward to reviewing.

Are you planning to get this in for the release candidate?
--
Jody Garnett


On Feb 22, 2024 at 2:07:59 AM, Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> On Wed, Feb 21, 2024 at 7:37 PM Jody Garnett 
> wrote:
>
>> That sounds good .. and surprising it is not there already? Is it just
>> not a feature of SLD?
>>
>
> Indeed, as crazy as it sounds, it's not an SLD feature. This is an excerpt
> from SE 1.1 schemas:
>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>
>> Default method very much appreciated to be kind to implementations. For a
>> default setter should it log a message, or throw a not implemented
>> exception?
>>
>
> Yes. There is only one implementation, that will be updated, so the
> exception should not be triggered in the practice.
>
>
>> If you are making an API change perhaps attack the channel traversal
>> problem directly with a default method to list all 4 channels...
>>
>
> The existing API is actually going to collaborate for this bit, here is
> what we have in the style visitor:
>
> /**
>  * Called when accept is called on a raster {@link ChannelSelection}
> element
>  *
>  * @param cs the {@link ChannelSelection} to visit.
>  */
> void visit(ChannelSelection cs);
>
> /**
>  * Called when accept is called on a raster {@link
> SelectedChannelType} element
>  *
>  * @param sct the {@link SelectedChannelType} to visit.
>  */
> void visit(SelectedChannelType sct);
>
> So it's up to the implementation to unpack the channel selection and call
> the visit on the single channel selection type.
> All existing implementations will be updated to call also on the new alpha
> channel. No need for a new visit method here.
>
> All in all, existing implementations not using the alpha channel should be
> unaffected, which should help backporting this change.
> Thoughts?
>
> Cheers
> Andrea
>
> ==
>
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Pre-proposal discussion: adding alpha to ChannelSelection

[Jody Garnett]

 That sounds good .. and surprising it is not there already? Is it just not
a feature of SLD?

Default method very much appreciated to be kind to implementations. For a
default setter should it log a message, or throw a not implemented
exception?

If you are making an API change perhaps attack the channel traversal
problem directly with a default method to list all 4 channels...
--
Jody Garnett


On Feb 21, 2024 at 10:26:41 AM, Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> Hi all,
> I'm looking into channel selection, and in particular, to add the ability
> to specify an alpha
> channel along with either RGB or Gray.
>
> XML wise that would look as follows:
>
> 
>   
> 3
>   
>   
> 2
>   
>   
> 1
>   
>   
> 4
>   
> 
>
> or:
>
> 
>   
> 3
>   
>   
> 4
>   
> 
>
> Now... API wise this a bit annoying as ChannelSelection does not have a
> list of channels, but separate methods for the gray and RGB cases:
>
>
> https://github.com/geotools/geotools/blob/main/modules/library/api/src/main/java/org/geotools/api/style/ChannelSelection.java#L23
>
> I would consider adding an alphaChannel getter/setter in that interface,
> with default implementation. Would that be ok?
> While it would not break compiling, it would still break semantics of
> visitors that care about channels (probably a minority) as they need to be
> updated to consider the new channel source. Would you consider this a
> blocker for backports?
>
> Code wise, I would expect to have to change the following:
>
>- Core interface and implementation
>- SLD 1.0 and 1.1 parser and encoder
>- CSS and eventually YSLD
>- The style builder in gt-browser
>- All visitors in GT/GS that care about channels (e..g, the
>duplicating one)
>- The grid coverage renderer to actually perform the selection
>
> What do you think?
>
> Cheers
> Andrea
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] GeoTools PMC Meeting 2024-02-13

[Jody Garnett]

GeoTools / GeoServer PMC meeting - 2024-02-13Attending

   -

   Peter Smythe
   -

   Gabriel Roldan
   -

   Jody Garnett
   -

   Torben Barsballe
   -

   Andrea Aime
   -

   Jukka Rahkonen
   -

   Kevin Smith


Actions from prior meetings:

   -

   [DONE] Peter: Make a PR to update the PSC list (in the developers guide)
   gabe: Please help with review of #7156
   -

   [DONE] Peter: Check-in with Brad to see how we can help/plan 
   -

   Peter: Share new wiki pages with the community
   -

   [WIP] gabe: Will make a PR for parallel loader
   -

   andrea: add peter to the security vulnerabilities issues

Agenda

   -

   Release schedule
   -

   mkdocs update
   -

   Discourse update
   -

   github security advisory graph question
   -

   Worldwide installations of GeoServers
   -

   Firefox redirection
   -

   GEOS-11284 Promote community module "datadir catalog loader" to core
   -

   GEOT-7411 App-schema performance improvement in setting attribute values
   -

   SLD Arrow Regression
   -

   JNDI documentation critical fix
   -

   “www” no longer serving JS apps

Actions

   -

   Peter: create a sed script to fix email addresses in sourceforge lists
   export
   -

   Jody: setup a github workflow to use dependency submission API
   
<https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api>
   -


Release schedule

GeoTools 29.5 / GeoServer 2.23.5 this month

Need a volunteer - Andrea will ask around GeoSolutions but no promises.
Fallback: Peter

Next RC cycle (2.25) is also approaching.

Adjusting release schedule to avoid extra 2.24 stable release…

https://github.com/geoserver/geoserver/wiki/Release-Schedule

Several potentially large changes outstanding:

   -

   Wicket 9 <https://github.com/geoserver/geoserver/pull/7154> (postpone to
   2.26)
   -

   Resources and Paths API
   <https://github.com/geoserver/geoserver/pull/7156>
   -

  one legit bug on windows
  -

  Firefox redirectionand stuck on difference of opinion on API meaning
  (need to clarify javadoc)
  -

  action: gabe: volunteer to check in on this later in the month
  (breakout meeting)
  -

   startup enhancements (should be good)
   -

   mkdocs (branch <https://github.com/geoserver/geoserver/tree/mkdocs>)
   (timing would be good)


sidebar: Handling of WPS results with respect of ResourceStore and multiple
containers

   -

   there is some other way to handle that, can check system property
   -

   ideally a blob storage would be good for shared WPS output
   -

   Configure in WPS administration panel, where to share output

mkdocs update

Download directives now work:
https://jodygarnett.github.io/geoserver/introduction/license/

   -

   docs/introduciton/download/download.txt - lists “external” files
   -

   docs/introduction/download/.gitignore - to avoid storing duplicate files
   -

   mkdocs.yml has a hook to code to read download.txt above


Example of using {{ version }} and {{ release }}:

   -

   https://jodygarnett.github.io/geoserver/installation/docker/
   -

   Short term {{ release }}
   -

   Jody would like to grab these from pom.xml (this would be a change to
   release procedure)
   -

   Or can we determine from git history
   -

   I cannot determine with git because our tags are not on our branch, ours
   are not :)


Can we convert the chinese docs:

   -

   yes we could, there is a language chooser
   -

   can convert chinese docs later, run the script, need a native speaker to
   review
   -

   jody has a script to convert language, but need a native speaker to
   review results

Discourse update

https://trac.osgeo.org/osgeo/ticket/3104#comment:7

Migration broken by SF anonymization…

Action: Peter to create a sed script to fix email addresses
github security advisory graph question

A change to a published vulnerability came in from Mark:

   -

   https://github.com/github/advisory-database/pull/3483
   -

   Q: why is this not being made to our geoserver one?


Fundamental questions:

   -

   For a vulnerability in gs-web-core …
   -

   Do we also record gs-web-app? For the war overlay use?
   -

   Do we also record against the war for download use
   -

   Do we also record against the windows installer …
   -

   Would this change for wps extension?


Jody’s expectation is to write down the most specific thing … and trust the
tools

The answer provided by dependabot is a github action, that would run for
each tag, that would publish the “graph” based on the pom.xml file
relationships.

   -

   https://github.com/dependabot/dependabot-core/issues/2640
   -

  No it does not handle maven pom.xml directly, there is an action that
  processes the dependency:tree into the “graph” used by the tools
  -

   would it be smart enough for profiles?


action: setup a github workflow to use dependency submission AP

Re: [Geotools-devel] Carsten has a JDBC DataStore proposal for review

[Jody Garnett]

er("num_features",
Integer.class));

public KNearestNeighbourFunction() {
super(NAME);
}

@Override
public Object evaluate(Object feature) {
throw new UnsupportedOperationException("Unsupported usage of
Nearest operator");
}
}



--
Jody Garnett


On Jan 16, 2024 at 7:09:57 AM, Jody Garnett  wrote:

> Thanks for the reminder, you could also reply to the post with a topic for
> the agenda :)
>
> --
> Jody Garnett
>
>
> On Mon, Jan 15, 2024 at 11:04 PM Carsten Klein 
> wrote:
>
>> Hello Jody,
>>
>> are you going to attend the GeoServer/GeoTools PMC Meeting at 18:30 CET
>> / 9:30 PST on January 16th (today)?
>>
>> If so, maybe you could bring my latest proposal at
>>
>>
>> https://github.com/geotools/geotools/wiki/SQL-Encoding-of-Vendor%E2%80%90Provided-Custom-Functions
>>
>> to the attention of the GeoTools devs?
>>
>> I've sent an email to the geotools-devel list on January 9th, 2024 and
>> did dot yet receive any response. Do you think there is something wrong
>> with the proposal or is it not clear enough?
>>
>> Actually, the requested/proposed new capabilities are quite important
>> for one of our upcoming projects and it would be great to get at least
>> some feedback about what the core developers think about it.
>>
>> To be honest, additionally, i'd love to leave the implementation up to
>> the GeoTools core developers, since those are already familiar with the
>> contributing and changing procedures of GeoTools. As shown by the
>> proposal, it's only about introducing one or two new interfaces plus
>> adding a line to each of the database backed data stores. Likely, the
>> pure implementation takes about 20 minutes or less.
>>
>> Cheers,
>>
>> Carsten Klein
>>
>> --
>>
>> Carsten Klein
>> Lead Software Engineer
>>
>> DataGis GmbH
>>
>> Johann-Strauß-Str. 26
>> 70794 Filderstadt
>> GERMANY
>>
>> Phone: +49 7158 9490 106
>> Fax: +49 7158 9490 111
>>
>> E-Mail: c.kl...@datagis.com
>> Internet: www.datagis.com
>>
>> Commercial Register: Stuttgart, HRB 225945
>> Management: Dr. Gunter Hahn, Markus Ruess, Carsten Klein
>>
>>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Development of a plugin

[Jody Garnett]

I would start by making a ticket outlining what is required, and then
contact the module maintainer for netCDF for suggestions on how to proceed.

If there is significant API change that would affect others, the module
maintainer may recommend writing a proposal (
https://docs.geotools.org/latest/developer/procedures/proposal.html).

For new functionality that needs an API change we make major releases twice
a year (making roadmap planning easier). We do this so frequently to
support consultants that only get paid when the needed functionality is
available for download. When we did releases once a year releases got
delayed for "one more thing". Worst case roadmap change available in six
months.

If the new functionality is additive and does not need an API change, it
can be backported to the stable branch after a month. This gives people a
chance to try try out the functionality and ensure it does not compromise
stability.  Best case roadmap change available in 2 months.

GeoTools matches release schedule with GeoServer, but our proposal process
is a little more relaxed.
--
Jody Garnett


On Fri, Feb 2, 2024 at 4:44 AM Amirhossein Nikfal 
wrote:

> The NetCDF plugin supports those NetCDF files which conform to a special
> convention (COARDS).
> How can Geoserver or Geotools be developed to support other NetCDF
> conventions? What are the possible roadmaps for such a task?
>
> Best regards,
> Amir
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Regarding naming of rules derived from css

[Jody Garnett]

I have not looked t these changes as I do not personally follow
stackexchange.

We are very much open to contributions and changes:

a) for day to day changes and fixes the CONTRIBUTING.md document describes
the nuts and bolts of submitting a pull request with QA coverage, and
documentation as required

b) For API changes (where compatibility is affected) there is a formal
change control process - where you write up a proposal for public review.
We have setup our procedure to be responsive in order to support
consultants working on behalf of a customer. Proposals are not rejected
without an alternate way forward provided. The goal is to reduce risk, and
to prevent more than one party making competing implementations (and then
both finish their budget and cannot work out a compromise leading to hurt
feelings).

- Proposal first: In your quote to a customer include a design milestone
which includes delivering of a proposal to the community; this way you get
a public review and assurance that your approach will be accepted; reducing
risk.

- Proposal second: Do the work and make sure your customer is happy
(sometimes the only way to establish scope); and then write it up as a
proposal to the community. The risk is if your approach missed out on
required tasks then you may be out of budget; with an unhappy customer.

We are very understanding if scope changes during implementation, or when a
customer firsts looks at it. The idea is to keep communication going.

The details of what I describe are in the developers guide:
-
https://docs.geotools.org/latest/developer/procedures/proposal.html
--
Jody Garnett


On Fri, Feb 2, 2024 at 5:23 AM Segerstedt, Peter via GeoTools-Devel <
geotools-devel@lists.sourceforge.net> wrote:

> Dear developers,
>
> I've made, on the behalf of a customer, small additions to geotools and
> geoserver in order to solve what's been previously discussed here:
>
>
> https://gis.stackexchange.com/questions/452624/name-property-for-rules-in-css-styles-alternatives-or-how-to-contribute
> https://sourceforge.net/p/geoserver/mailman/message/36050785/
>
> The code should be publicly available here:
> https://github.com/sweco-sepesd/geoserver/tree/geoserver_css_name_rule
> (
> https://github.com/sweco-sepesd/geoserver/commit/7ed3780e377dcb0318bf9f44be2420d2f53d2639
> )
>
> https://github.com/sweco-sepesd/geotools/tree/css_named_rule
> (
> https://github.com/sweco-sepesd/geotools/commit/2a4d1afcbb6fac7ac9c7798946db50a627aff119
> )
>
> Under what circumstances would it be possible for geotools/geoserver to
> adopt these changes?
>
> Best Regards,
>
> Peter Segerstedt
>
>
>
>
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] GeoTools PMC Meeting Notes 2024-01-30

[Jody Garnett]

GeoTools / GeoServer PMC meeting - 2024-01-30Attending

   -

   Torben Barsballe
   -

   Peter Smythe


   -

   Kevin Smith
   -

   Gabriel Roldan
   -

   Andrea Aime
   -

   Amir Nikfal
   -

   Jody Garnett


Actions from prior meetings:

   -

   [DONE] action: Reopen ContentDataStore API ticket GEOT-7509
   <https://osgeo-org.atlassian.net/browse/GEOT-7509>  to update affected
   docs
   -

   Action: Wait for Carsten to read the above SQL Function discussion, and
   we can discuss further in email
   -

   action: Make a https://trac.osgeo.org/ right away to ask osgeo to
   purchase domain name (https://trac.osgeo.org/osgeo/ticket/3121#ticket)
   -

   [DONE] Action: Peter: create roadmap placeholder pages so we can list
   in-kind interested parties and sponsors
   -

   [DONE] action: Andrea creating a ticket
   <https://sourceforge.net/p/forge/site-support/25396/> for SF mailman
   download
   -

   [DONE] action: Jody to reply to email topic on getfeature freemarker
   encoding

Agenda

   -

   [GEOT-7411] App-schema performance improvement in setting attribute
   values <https://github.com/geotools/geotools/pull/4410>ready to merge,
   no bandwidth to fix failing integration tests?
   -

   Welcome to Peter in the PSC
   -

   Extending Query to support sorting on expression
   -

   Security vulnerability update/review ahead of 2.25.0 release cycle
   -

   Release/Roadmap planning

Actions

   -

   peter: Make a PR to update the PSC list (in the developers guide)
   gabe: Please help with review of #7156
   -

   [done] peter: Check-in with Brad to see how we can help/plan 
   -

   Peter: Share new wiki pages with the community
   -

   gabe: Will make a PR for parallel loader
   -

   andrea: add peter to the security vulnerabilities issues





[GEOT-7411] App-schema performance improvement in setting attribute values
ready to merge, no bandwidth to fix failing integration tests?

PR has been re-aligned.

Issue, there are failing tests in the postgis online app-schema tests:

[ERROR]
FeatureChainingWfsTest.testEncodeFeatureMember:1868->AbstractAppSchemaTestSupport.assertXpathCount:340
expected:<1> but was:<0>

[ERROR]   PagingTest.testGetFeatureWithCSVFormat:900 expected:
but was:

[ERROR]
SRSWfsTest.testGetFeatureContent:148->AbstractAppSchemaTestSupport.assertXpathEvaluatesTo:329
expected:<[-1.2 52.5 -1.2 52.6 -1.1 52.6 -1.1 52.5 -1.2 52.5]> but
was:<[52.5 -1.2 52.6 -1.2 52.6 -1.1 52.5 -1.1 52.5 -1.2]>

[ERROR]
SRSWfsTest.testReproject:378->AbstractAppSchemaTestSupport.assertXpathEvaluatesTo:329
expected:<[-1.2 52.5 -1.2 52.6 -1.1 52.6 -1.1 52.5 -1.2 52.5]> but
was:<[52.5004 -1.2 52.6004 -1.2 52.6004 -1.1 52.5004 -1.1 5

Welcome to Peter in the PSC

We appreciate all the help Peter has been giving to the project as of late!

Welcome Peter to the PSC.

action:

   -

   peter: Make a PR to update the PSC list
   
<https://github.com/geoserver/geoserver/blob/main/doc/en/developer/source/policies/psc.rst>
   (in the developers guide)

Extending Query to support sorting on expression

Query SortBy allows sort on propertyName

   -

   We should be able to sort by an expression
   -

   Yes we should … make a GeoTools more general
   -

   May be a challenge for some DataStores?
   -

  Yeah but ContentDataStore handles this in memory or disk if your
  store cannot do the thing …
  -

  JDBCDataStore can learn how to do this, maybe Dialect?
  -

   PropertyName getPropertyName() // deprecated
   Expression getPropertyName()
   -

   Go through normal API change cycle, deprecate and remove
   -

   Make a proposal so we get all the tasks (example updating parsers)

Great idea!
Release/Roadmap planning

We identified a bunch work:

   -

   Peter made wiki pages for helpers, in-kind assistance
   -

   https://github.com/geoserver/geoserver/wiki/Maintenance-%26-Roadmap


Can we do anything for the 2.25 release cycle?

   -

   roadmap: If the wicket 9 upgrade is ready it can be included? Not sure …
   -

  volunteers are asking how to help (for manual testing)…
  -

  but we first need developers to finish
  -

   roadmap: nothing else is close to being ready
   -

   Niels resource store api PR
   <https://github.com/geoserver/geoserver/pull/7156> still needs jody to
   review (sigh)
   -

  https://github.com/geoserver/geoserver/pull/7156
  -

  there is a solid test failure to fix here
  -

  Jody requests help as we seem to be at an impasse (Niels is correct
  in identifying the problem; just do not have a clear solution I am happy
  with)
  -

  Jody wants the paths to be consistent clear javadocs
  -

   roadmap: can we include the parallel loader please?
   -

  Gabe is using it as the default loader in geoserver-cloud. It has a
  bunch of production testing now (3-4 instances for some time now)
  -

  

Re: [Geotools-devel] Time to remove GDAL support from the OSX Github action?

[Jody Garnett]

 Thanks,

I remember asking at a code sprint and the GDAL folks needed a volunteer to
publish out java bindings themselves. I did the build once a couple years
back; not sure what shape it is in now.

I do not see Mac instructions in their manual at present:
https://gdal.org/api/java/index.html
--
Jody Garnett


On Jan 24, 2024 at 11:23:57 PM, Roar Brænden 
wrote:

> Hi,
>
> I have some experience in using Mac and GDAL. It will not work by just
> using "brew install gdal", because that will not install the Java bindings.
> There was this other brew tap called "osgeo/osgeo4mac" that had a solution
> for the Java bindings, but I don't that works either. The solution for me
> was to build the GDAL libraries from sources, an even then there are some
> settings and tweaks to make it run with GeoTools.
>
> So my recommendation is to drop it.
>
> Regards,
> Roar Brænden
>
>
>
>
> 22. jan. 2024 kl. 20:05 skrev Jody Garnett :
>
> I can look at it after this release
> --
> Jody Garnett
>
>
> On Mon, Jan 22, 2024 at 3:42 AM Andrea Aime <
> andrea.a...@geosolutionsgroup.com> wrote:
>
>> Hi al,
>> the OSX github action keeps on failing while installing GDAL.
>> Mark has made a valiant effort to try and get it going, which I truly
>> appreciate, but... it just keeps on failing.
>>
>> At this point, I vote for just pulling the GDAL installation from the OSX
>> action.
>> Objections? Ideas? Actions?
>>
>> Cheers
>> Andrea
>>
>> ==
>> GeoServer Professional Services from the experts!
>> Visit http://bit.ly/gs-services-us for more information.
>> ==
>>
>> Ing. Andrea Aime
>> @geowolf
>> Technical Lead
>>
>> GeoSolutions Group
>> phone: +39 0584 962313
>> fax: +39 0584 1660272
>> mob:   +39  339 8844549
>>
>> https://www.geosolutionsgroup.com/
>> http://twitter.com/geosolutions_it
>> ---
>>
>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>> precisa che ogni circostanza inerente alla presente email (il suo
>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>
>> This email is intended only for the person or entity to which it is
>> addressed and may contain information that is privileged, confidential or
>> otherwise protected from disclosure. We remind that - as provided by
>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>> e-mail or the information herein by anyone other than the intended
>> recipient is prohibited. If you have received this email by mistake, please
>> notify us immediately by telephone or e-mail
>> ___
>> GeoTools-Devel mailing list
>> GeoTools-Devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
>
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] Thanks for the donation Andrea

[Jody Garnett]

I have updated the 2024 Donations list to thank Andrea Aime for continued
securing donation to GeoServer:

   - https://geoserver.org/sponsor/


Thanks Andrea (and thanks for your hard work also).
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] Release 30.2 available for preflight testing

[Jody Garnett]

Hello everyone:

Downloads are available here:
https://build.geoserver.org/view/release/job/geotools-release/lastSuccessfulBuild/artifact/build/release/distribution/30.2/
for
preflight testing.

Other things to review:

   - Jira Release notes:
   
https://osgeo-org.atlassian.net/projects/GEOT/versions/16907/tab/release-report-all-issues

   - Tag has the jira release notes:
   https://github.com/geotools/geotools/releases/tag/30.2
   - draft blog post

--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Time to remove GDAL support from the OSX Github action?

[Jody Garnett]

I can look at it after this release
--
Jody Garnett


On Mon, Jan 22, 2024 at 3:42 AM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> Hi al,
> the OSX github action keeps on failing while installing GDAL.
> Mark has made a valiant effort to try and get it going, which I truly
> appreciate, but... it just keeps on failing.
>
> At this point, I vote for just pulling the GDAL installation from the OSX
> action.
> Objections? Ideas? Actions?
>
> Cheers
> Andrea
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] GeoTools PMC Meeting 2024-01-16 Notes

[Jody Garnett]

GeoTools / GeoServer PMC meeting - 2024-01-16Attending

   -

   Torben Barsballe
   -

   Jody Garnett
   -

   Peter Smythe
   -

   Gabriel Roldan


   -

   Jukka Rahkonnen
   -

   Andrea Aime


Actions from prior meetings:

   -

   Andrea: Look into JIRA license limit
   -

   Brad: Give the OK on the Wicket 9 Upgrade

Agenda

   -

   Proposal: SQL Encoding of Vendor Provided Custom Functions
   -

   Release Planning
   -

   Roadmap coordination
   -

   Sponsorship updates
   -

   User-list / Discourse discussion
   -

   Security Vulnerabilities update/review
   -

   HTML GetFeature encoding with Freemarker templates
   -

   Jitsi Issues
   -

   geowebcache domain name was not renewed

Actions

   -

   action: Reopen ContentDataStore API ticket GEOT-7509
   <https://osgeo-org.atlassian.net/browse/GEOT-7509>  to update affected
   docs
   -

   Action: Wait for Carsten to read the above SQL Function discussion, and
   we can discuss further in email
   -

   action: Make a https://trac.osgeo.org/ right away to ask osgeo to
   purchase domain name (https://trac.osgeo.org/osgeo/ticket/3121#ticket)
   -

   Action: Peter: create roadmap placeholder pages so we can list in-kind
   interested parties and sponsors
   -

   action: Andrea creating a ticket
   <https://sourceforge.net/p/forge/site-support/25396/> for SF mailman
   download
   -

   action: Jody to reply to email topic on getfeature freemarker encoding


Proposal: SQL Encoding of Vendor Provided Custom Functions

Proposal from email:
https://github.com/geotools/geotools/wiki/SQL-Encoding-of-Vendor%E2%80%90Provided-Custom-Functions


Q: Is this the change to the ContentDataStore canProcess(filter) kind of
thing?

A: No, it was only an API change to main (no need to backport) so that got
merged.

   -

   Um, did this update the content datastore tutorial? Um no …
   -

   action: Reopen ContentDataStore API ticket to update affected docs
   please …


Discussion:

   -

   Jody would like to avoid functionality that only works in PostGIS (for
   example?) to avoid breaking WFS.
   -

   Apparently this is already the case with some placeholder functions (KNN
   for example)
   -

   Why? Because then the WFS GetCapabilities advertises functionality that
   “does not work” (this is somewhat a limitation of the WFS standard)
   -

   Still the  approach could be okay for GeoTools Java programmers, but
   does it really affect GeoServer?


What to do?

   -

   SLD already has a mechanism for this? Providing a “fallback value” if
   the function is not available in that context …
   -

   We could use the marker interface to avoid listing these functions in
   WFS GetCapabilities


Goal is to make the SQL generation / encoding extensible:

   -

   seems okay; but is “per datastore”
   -

   even that should be fine as long as their is a java fallback so it can
   be listed in WFS GetCapabilities
   -

   If there is no fallback java implementation? Do not list in WFS
   GetCapabilities, but could be used in SLD (if there is a fallback value for
   safety)


The limitations about exact function name match?

   -

   that is not so good as different databases may have different function
   names, or small SQL snippets …


Jody: WIth the changes above I think this could be a good addition…

Action: Wait for Carsten to read the above SQL Function discussion, and we
can discuss further in email

Release Planning

Jody volunteering to do the release this week, see
https://github.com/geoserver/geoserver/wiki/Release-Schedule

aside: new graphic for https://geoserver.org/roadmap/ is cute

mkdocs

No I do not have mkdocs ready but you can look:
http://jodygarnett.github.io/geoserver/

download is a challenge:

   -

   within in a docs folder a relative link,


   -

   linking to stuff outside of docs?
   -

  We have like 400 examples of this
  -

  link to raw github on the branch or something.
  -

  Or use ant to prefetch everything into the docs folder? snippets
  allows an “include” folder which would be appropriate?
  -

   See https://jodygarnett.github.io/geoserver/introduction/license/

Roadmap coordination

What is going on:

   1.

   Wicket 9 upgrade if ready (2.25.x be ideal if we can coordinate it)
   2.

   ImageN: Andrea joined email list, needs to be nominated for commit access
   3.

   spring-framework-6: gabe started looking at it


Can we coordinate with Brad to get Wicket upgrade in time for 2.25.x
release cycle?

   -

   PR here: https://github.com/geoserver/geoserver/pull/7154
   -

   Brad outlined something technical about wicket upgrade and said not to
   test yet?
   -

  New security feature of the browser, which disables inline styles, …
  -

  result is need to removing inline styles
  -

   What is needed:


   -

   Brad to enjoy summer vacation in Australia :)
   -

   Setup a planning document, or wiki page, to outline plan for the year -
   so peo

Re: [Geotools-devel] Time to upgrade Spotless... and maybe take advantage of the break?

[Jody Garnett]

I really like the more terse alternative and longer line width.

Since I like two things +2 :)

--
Jody Garnett


On Tue, Jan 2, 2024 at 9:06 AM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> Hi all,
> you probably know that we are formatting the source code with the Spotless
> Maven plugin,
> in combination with the Google Java Format library.
>
> Currently, we are using an older version of both, because they upgraded
> time ago to require Java 11 as the minimum version, and we were still using
> Java 8. But we have been on Java 11 for a while now, and we can update up
> the dependencies.
>
> I've prepared a pure upgrade of GeoTools, as an example, here:
> https://github.com/aaime/geotools/tree/spotless_upgrade
>
> The update touches 2k files, mostly changing the javadoc style for single
> line javadocs, to use three lines instead. Lots of noise, no significant
> gain in my opinion.
>
> One formatting library that I've been keeping an eye on for a while is
> Palantir's fork of Google Java format. They made some significant changes:
>
>- 4 spaces indent by default (we get this by adopting the AOSP style
>of Google's one)
>- 120 columns rather than 100
>- Formatter optimized for streams and functional style to use less
>space.
>
> They have some significant examples in their landing page
> <https://github.com/palantir/palantir-java-format?tab=readme-ov-file#motivation--examples>.
> I've tried this out with GeoTools, and linking what I've found, also with
> GeoServer (both are best viewed offline, in a checkout):
>
>- https://github.com/aaime/geotools/tree/spotless_palantir
>- https://github.com/aaime/geoserver/tree/spotless_palantir
>
> In this case, the GeoTools diff is significantly bigger than the pure
> Spotless upgrade, touches 2k files, but in the end, manages to cut down 60k
> lines of code.
>
> What is your opinion? Would you like to go with Palantir?
>
> If we went down that road, I'd recommend to:
>
>- Wait until the Wicket 9 upgrade is done
>- Wholesale reformat all three projects (GeoTools, GeoWebCache,
>GeoServer)
>- Reformat all active branches for ease of backport (if this ends up
>landing after the 2.25.x release, maybe also reformat the 2.23.x series as
>it will likely get some extra fixes in the next few months).
>
> Cheers
> Andrea
>
> ==
>
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] GeoServer/GeoTools PMC Meeting at 18:30 CET / 9:30 PST tomorrow

[Jody Garnett]

I may be in transit and unavailable for tomorrow's meeting.

Topics:
- blog post is ready:
https://github.com/geoserver/geoserver.github.io/pull/175 describing 2024
roadmap
- GSIP is ready:
https://github.com/geoserver/geoserver/wiki/GSIP-221

Community stuffs:
- New osgeo board is being assembled, voting starts this week
- The existing board is assembling the budget from everything provided thus
far
- The text of the european Cyber Resilience Act is out; and has a lot of
language softening open-source exposure. There will still be work to do to
support our core contributors but that is fine.
--
Jody Garnett


On Mon, Jan 1, 2024 at 6:32 PM Torben Barsballe 
wrote:

> Reminder that the next PMC meeting is scheduled for tomorrow, January 2,
> at 18:30
> <https://www.timeanddate.com/worldclock/fixedtime.html?year=2024=1=2=18=30=0=GeoTools%20/%20GeoServer%20Meeting=1=1=215>
>  CET.
>
> You can join the meeting by following this link:
> https://meet.osgeo.org/GeoServerMeeting
>
> Cheers,
> Torben
>
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Java 21 Github build check active

[Jody Garnett]

Thanks for the improvement!

When do we decide we officially support Java 21 and update the docs:
-
https://docs.geotools.org/latest/userguide/build/install/jdk.html

There is actually an update needed, a lot of the quickstart instructions
still indicate Java 8.

--
Jody Garnett


On Thu, Dec 28, 2023 at 6:00 AM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> Hi all,
> as discussed in the last PSC meeting, we now have a Java 21 build
> in addition to the Java 11 and Java 17 one, checking that the code
> builds properly under the new Java LTS.
>
> You're probably wondering, what does one need to pay attention to?
> Mostly likely, nothing, the entire code base was made to build with Java 21
> with a handful of changes here:
>
> https://github.com/geotools/geotools/pull/4591
>
> Long story short, it should be largely transparent, but we want to make
> sure
> the code is working fine on Java 21 as users get that version by default
> now,
> when just going to install "Java".
>
> Cheers
> Andrea
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] Carsten has a JDBC DataStore proposal for review

[Jody Garnett]

There is a GeoTools proposal taking shape here:
https://github.com/geotools/geotools/wiki/SQL-Encoding-of-Vendor%E2%80%90Provided-Custom-Functions

I neglected to bring this up in today's meeting; if there is any feedback
for Carsten please share 
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] GeoTools PMC Meeting December 19 2023

[Jody Garnett]

GeoTools / GeoServer PMC meeting - 2023-12-19Attending

   -

   Torben Barsballe
   -

   Kevin Smith
   -

   Andrea Aime
   -

   Gabriel Roldan
   -

   Jody Garnett


Actions from prior meetings:

   -

   Jody: Submit budget + sponsor activities
   
<https://github.com/geoserver/geoserver/wiki/GeoServer-2024-Sponsorship-Opportunities>
   to board (copy geotools example)
   -

   [DONE] Jody: Make a motion to sponsor Marlin and GISSA 2024

Agenda

   -

   Release 2.23.4 Planning
   -

   OSGeo Budget Request / Sponsorship Opportunities
   -

   GSIP 221 mkdocs
   -

   Java 21 work ongoing
   -

   Use maven CI friendly versions (
   https://maven.apache.org/maven-ci-friendly.html)
   -

   Security Vulnerability Roundup


Actions

   -

   Jody: Call for vote on GSIP 221, plan to update early Jan
   -

   Andrea: warn people about Java 21 build requirements and start merging
   PRs. Also make a GWC 21 PR.

Release 2.23.4 Planning

Looks like we have a volunteer - Peter! Thank you Peter!

He will need backup on GWC (if there are any changes)

   -

   checking: yes an update is needed


OSGeo Budget Request / Sponsorship Opportunities

The OSGeo elections are stalled on communication - so the current board has
not been replaced

   -

   that results in delay for budget communication stuff (sigh)
   -

   We are ready with a request:
   -


  
https://github.com/geoserver/geoserver/wiki/GeoServer-2024-Sponsorship-Opportunities
  -

   OSGeo request is updated to:
   -

  $1000 Operational
  -

  $1000 Security CRA reporting requirements
  -

  $0 AGM Attendance


Jody would like to plan a blog post for January 1st (new calendar year).

   -

   please provide feedback to the list; or contact jody directly with your
   input
   -

   there will be a pull-request for review/feedback

GSIP 221 mkdocs

https://github.com/geoserver/geoserver/wiki/GSIP-221


   -

   There is an example for A/B comparison
   -

   pending: Trying handle |version| or |release| substitutions
   -

   https://github.com/geoserver/geoserver/tree/mkdocs/doc/en/user


Q: Doc freeze?


Yes - a good idea when proposal is accepted

   -

   it is quick to convert as I have script? So can we freeze for 1-2 days
   after successful doc conversion

Q: Do we just want to update main? Or the active branches?

   -

   A: Update the active branches


Q: version selector version VS stable URLs

   -

   A: This is attractive; but we may be able to do it later …


   -

   If we update the active branches we can get a versions/language selector
   
   -

  https://docs.geonetwork-opensource.org/4.2/
  -

  https://docs.geonetwork-opensource.org/4.2/fr/
  -

  https://docs.geonetwork-opensource.org/latest/
  -

   It likes to have a directory structure like this:
   -

  version.json
  
<https://github.com/geonetwork/core-geonetwork/blob/gh-pages/versions.json>
  -

  2.24/
  -

  latest/
  -

  2.23/
  -

  stable/
  -

  2.22/
  -

  maintenance/
  -

   It is optimized for gh-pages deployment, but we have our manual deploy
   process…


Action: Jody will call for a vote on the proposal, plan to doc freeze the
1st week of January
Java 21 work ongoing

https://github.com/geotools/geotools/pull/4591

Q: Allow to Java 21 build to fail?

   -

   A: No, go for broke 


This handles people who just install java … and end up with Java 21.

Q: Why is this working? I thought JAI would break things …

   -

   A: We are not running QA - indeed if we build with Java 17 or Java 21
   the QA will fail
   -

   We compile with Java 11, and then Java 17 and Java 21 will load the
   older classes with less strict requirements


How to go with it? Just go with a warning that code will build with java 21
in the actions.
Use maven CI friendly versions

See https://maven.apache.org/maven-ci-friendly.html

Andrea +1

Requires Maven > 3.5.0

Jenkins is showing two different maven versions:

   -

   3.6.3 in the logs and when ssh’d to the server
   -

   3.9.5 in the web console
   https://build.geoserver.org/manage/configureTools/

We should probably be more consistent here, but in any case Jenkins
supports this tool as-is
Security Vulnerability Roundup

The Coordinated Vulnerability disclosure policy is going fine.

Notes:

   -

   sikeoka has been working on several fixes
   -

   gabe has one to look at
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Bug when graphic-margin is greater than marker size

[Jody Garnett]

That looks good; and the change to the reference image covers your need for
a test case.

Question: you assume the margin is an array of 4 numbers.

Does it work like with CSS where an array of a single number, or an array
of two numbers could be provided?

--
Jody Garnett


On Tue, Dec 19, 2023 at 7:33 AM Cécile Vuilleumier <
cecile.vuilleum...@camptocamp.com> wrote:

> Hi all
>
> I am back again on the topic of polygon fill with repeated markers (see
> https://osgeo-org.atlassian.net/browse/GEOT-7357)
> Unfortunately my fix did introduce an unwanted side effect: if the given
> margin is greater than the marker size, an error is thrown and the layer is
> not drawn:
> org.geotools.renderer.lite: x lies outside raster  -> it happens on this
> line
> <https://github.com/geotools/geotools/blob/9df403d52baf8f099d8d9569b7399a1b1906568a/modules/library/render/src/main/java/org/geotools/renderer/style/SLDStyleFactory.java#L1263>
>
> Here is a proposed fix:
> https://github.com/vuilleumierc/geotools/commit/b94415a586fdb86a923b072a9ad26af92c83b278
>
> Is it OK for me to open an issue and a PR?
>
> Cheers, Cécile
>
> --
> *camptocamp*
>
> *Cécile Vuilleumier *
> Geospatial developer
> www.camptocamp.com
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] [Geowebcache-devel] Release train starting tomorrow

[Jody Garnett]

Thanks Peter, that is much appreciated.

One thing to keep an eye out for testing is change to the binary
distribution.

We should be able to run startup.sh from:

cd $GEOSERVER_HOME
bin/startup.sh

or:

cd GEOSERVER_HOME/bin
./startup.sh


--
Jody Garnett


On Mon, Dec 18, 2023 at 11:33 PM Peter Smythe  wrote:

> Good day developers
>
> I will be starting with a maintenance release of GeoServer 2.23.4 in
> conjunction with GeoTools 29.4 (and GeoWebCache if necessary) tomorrow, so
> if anyone wants to get code into these releases, please do it in the next
> 24 hours.
>
> Thank you
>
> Peter
> ___
> Geowebcache-devel mailing list
> geowebcache-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geowebcache-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Introduce query as context to ContentFeatureSource capabilities

[Jody Garnett]

I was not considering back porting as this is an API change? Admittedly
only a protected API between superclass and implementation.

If we really need to backport then option 2 is the only one.
--
Jody Garnett


On Mon, Dec 18, 2023 at 6:04 AM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> Hi,
> I agree with contextualizing on Query the various "canXYZ" methods in
> ContentFeatureSource, and agree on the implementation
> that deprecates the method without any parameter, having the new one
> delegate back. It fits just fine with the main branch.
>
> However, I'm worried about the backports. We don't have precedent for
> deprecating bits of an important API like
> ContentFeatureSource on stable/maintenance too.
>
> What to do? Options:
>
>- Don't backport. It's what we normally do, don't think it's what
>Bjorn needs though.
>- Backport without deprecation? Would a warning in the javadoc that
>the method will be deprecated help any? Not sure anyone would read it.
>- Backport as is. That would be new, don't think it's fair to just
>deprecate stuff like that in stable (and more importantly, in maintenance)
>but I'm open to discussion.
>
> Cheers
> Andrea
>
> On Fri, Dec 15, 2023 at 1:10 PM Björn Harrtell 
> wrote:
>
>> Hi,
>>
>> TL;DR - I propose to add query as parameter for capability methods like
>> canOffset in ContentFeatureSource to allow native optimization to be
>> implemented for specific categories of queries. See JIRA issue at (1).
>>
>> Longer story,
>>
>> I recently discovered that fetching larger datasets from static files
>> like FlatGeobuf (and presumably Shapefile?) using paged access (startIndex
>> offset) is not optimal and will result in "full scans" on each request.
>>
>> Currently a datastore must either provide native implementation for all
>> cases or none based on the boolean answer for a capability. This works fine
>> for flexible storages like databases and the like which can support these
>> things generally. However, fx. FlatGeobuf can only support offset in
>> certain circumstances based on the actual query. For example, it can
>> support offset on queries for the full dataset without any filtering or
>> custom ordering but it cannot support offset in combination with an
>> attribute filter.
>>
>> To be able to optimize the queries it can handle it would therefore in
>> this case be useful to be able implement capabilities so that the answer
>> can depend on the actual query.
>>
>> There has been some informal discussion on the naming sensibility of this
>> and I suppose there could be an issue that this removes the ability for a
>> data store to generally advertise that it can do something generally
>> without supplying an actual query.
>>
>> See proposed implementation at (2).
>>
>> 1) https://osgeo-org.atlassian.net/browse/GEOT-7509
>> 2) https://github.com/geotools/geotools/pull/4593
>>
>> Regards,
>> Björn Harrtell
>> ___
>> GeoTools-Devel mailing list
>> GeoTools-Devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
>
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Can anyone figure out the GDAL setup failure in the MAC OS build?

[Jody Garnett]

 I have a Mac is there something I can test?

Running brew update just lists for me things that are outdated - which
included gdal.

Running brew upgrade gdal worked

But it is wise to be careful with python and home-brew because it is not
automatically on the path.
--
Jody Garnett


On Dec 7, 2023 at 4:24:47 AM, Mark Prins  wrote:

> So I've opened a `brew update` PR
>
> https://github.com/geotools/geotools/pull/4586
>
> but that seems to just make the failure reproducible...
>
> -M
>
>
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] GeoTools 2024 Sponsorship Opportunities / OSGeo Budget 2024 page

[Jody Garnett]

GeoTools PMC:

I have submitted request for $2000 to
https://wiki.osgeo.org/wiki/OSGeo_Budget_2024#OSGeo_Projects

Please see
https://github.com/geotools/geotools/wiki/GeoTools-2024-Sponsorship-Opportunities
for
details
--
Jody Garnett


On Oct 31, 2023 at 2:01:39 PM, Jody Garnett  wrote:

> Hey folks,
>
> I attended the OSGeo board meeting to day to check in on CRA communication
> (interesting to think about what regulation would mean to a library like
> GeoTools). One topic that came up was the OSGeo Annual Budget Request,
> which has traditionally used GeoTools as a "good example" 
>
> With that in mind please review draft budget request:
>
>- GeoTools 2024 Sponsorship Opportunities
>
> <https://github.com/geotools/geotools/wiki/GeoTools-2024-Sponsorship-Opportunities>
>
>
> Notes:
>
>- For the roadmap challenges outlined above, please see slides 52-55
>in recent presentation
>
> <https://docs.google.com/presentation/d/1clOEsaUBzVVXZqCUHWvbyxPRAgRjSbmsOtCk06Zi068/edit?usp=sharing>
>.
>- I am taking our lessons learned from foss4g and actually asking
>sponsors for money
>- Added a placeholder sponsorship page
><https://github.com/geotools/geotools/wiki/Sponsorship>to the wiki
>also.
>
>
> Please review the above pages.
> --
> Jody Garnett
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Fun with wind arrows in polar projections

[Jody Garnett]

What a fun problem, I think the suggestion is a good one.

On Fri, Dec 1, 2023 at 2:31 AM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> Hi,
> I'm working with wind maps, where typically the data contains
> (some way to compute) magnitude and directions of the wind vectors.
>
> Now, the "direction" is an angle that is used to rotate a symbol.
> The angle has an assumption... that north is up. However, take a non
> trivial projection, like polar ones, and the assumption goes belly up, the
> direction of north can change point by point.
>
> So my plan is to introduce a function, "northFix", that would provide a
> correction angle
> taking as parameters a CRS and the current point. Something like this:
>
> 
>   
> EPSG:3976
> theGeom
> windDirection
> 
>  
>
> Parameters in order:
>
>- The current CRS  (in actual app, coming from an env variable, e.g
>"wms_crs" in GeoServer)
>- The current point
>- The angle to be fixed
>
> So far, so good, I'd say... but in a general SLD, that might still eat
> quite some time, in cases where it's not needed, e.g., web mercator, WGS84.
> It would be better to recognize the situation right away, and eliminate the
> function, replacing it with the wind direction property name directly.
>
> I have a StyleSimplifier that could do that, but it would also be quite
> ad-hoc. Could we have maybe an interface that functions could implement to
> test if they are simplifyable at all, and offer a replacement? E.g.
>
> SimplifyableFunction {
>  Expression simplify(Function function);
> }
>
> Thoughts?
>
> Cheers
> Andrea
> ==
>
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] GeoTools Release train starting

[Jody Garnett]

 I have tested, and the release is now published - the blog post is
scheduled to be visible on Monday.

Had to double back and get a fix for
https://osgeo-org.atlassian.net/browse/GEOT-7495 in; a glitch leftover from
package changes for 30.x series.

Thanks everyone
--
Jody Garnett


On Nov 23, 2023 at 4:09:22 PM, Jody Garnett  wrote:

> Release artifacts available for testing here:
> https://build.geoserver.org/view/release/job/geotools-release/113/artifact/build/release/distribution/30.1/
> --
> Jody Garnett
>
>
> On Nov 23, 2023 at 9:55:56 AM, Jody Garnett 
> wrote:
>
>> I will be releasing geotools today, for announcement Monday.
>> Thanks to everyone who has been doing bug fixes :)
>> --
>> Jody Garnett
>>
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] GeoTools Release train starting

[Jody Garnett]

 Release artifacts available for testing here:
https://build.geoserver.org/view/release/job/geotools-release/113/artifact/build/release/distribution/30.1/
--
Jody Garnett


On Nov 23, 2023 at 9:55:56 AM, Jody Garnett  wrote:

> I will be releasing geotools today, for announcement Monday.
> Thanks to everyone who has been doing bug fixes :)
> --
> Jody Garnett
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] GeoTools Release train starting

[Jody Garnett]

I will be releasing geotools today, for announcement Monday.
Thanks to everyone who has been doing bug fixes :)
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] Change to bi-weekly jitsi PMC meeting room

[Jody Garnett]

We take part in a bi-weekly meeting using jitsi. The next meeting, on Nov
21, will use osgeo meeting room:  https://meet.osgeo.org/GeoServerMeeting

(Anonymous access is still fine, only one person needs needs to use OSGeo
User ID to start meeting)

For background see: https://jitsi.org/blog/authentication-on-meet-jit-si/

--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] GeoServer/GeoTools PMC Meeting at 18:30 CET / 9:30 PST tomorrow

[Jody Garnett]

We may also wish to switch to osgeo Jitsi at some point:
https://wiki.osgeo.org/wiki/SAC:Jitsi

No real difference. Jitsi changed to requiring a login for the person
hosting the meeting.. from google or Facebook or something. Everyone else
can be anonymous.

The OSGeonserver requires osgeo login to host meeting rather than google.

Jody

On Mon, Nov 6, 2023 at 12:41 PM Torben Barsballe 
wrote:

> Reminder that the next PMC meeting is scheduled for tomorrow, November 7,
> at 18:30
> 
> CET.
> With the NA switch to Daylight Savings this week, and Europe last week, it
> should be the same time as usual for everyone.
>
> Cheers,
> Torben
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] [Geoserver-devel] Artefacts for GeoServer release 2.23.3 ready for testing

[Jody Garnett]

 Peter:

I updated today to "Java version: 11.0.21, vendor: Eclipse Adoptium" and
the demo is working as expected.

I could not figure out the java release notes to determine what had changed.


--
Jody Garnett


On Oct 31, 2023 at 12:44:41 AM, Peter Smythe  wrote:

> Hi Jody (and *looking for other GeoTool developers/users assistance too*)
>
> Thanks for the macOS feedback.  Strange.  I can confirm that the testing
> procedure (
> https://docs.geotools.org/latest/developer/procedures/release.html
> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/B-HcvO1gcgX0TvExSk1DDw4Iq4M7PxQhSpZ7bu813CEB0Xo0pKlq-fhZvOnnHpK7O2Ofm1y_RhBMJ7EwG_5lp7kvKOFcMEe-FNOqcEIUnkUVjzU5uJnyusHfL9fEofpyA8KTwzGrlp5hIuzgk-zerls6fK0pQw__JLlDCr3z-goqbNYrOAepjYqyfteL9t4LEKsMwdkF5DvzVPORPLzRGI60LT31jJYeR8RQLtXo4Y1KtP8crpy1qh2fOdZNtfgUMRKY5RRg-guhpdQwWa7xbfQguhxBQWLXwWLS>
> > Test the Artifacts > Run quickstart) works on Windows 11 and both Java 11
> and Java 17.
>
> It would be really great if other GeoTool developers or users could
> perform the same test on the release artefacts from
> https://build.geoserver.org/view/geotools/job/geotools-release/112/
> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/MmmXnNh70101LByXEHoKlTeG0vOqvuVHQaCAto1qeinLFalfooMFRqx0RBVDo490ol7SRh9c8M-GQHZoJ0Tq8rj7ZiDGoIK7Ln8EUYjqfciNF3f25c1i0qmvuiJZz3DfLjQE60d5A1SDSvrS6cZ_Qq5phlMQZ-gwQFJW_om8yojm90iEmAALGW163_tiQJhbUS0x7FTparHBngcq4fbRle1Uc6kJbaPirabLuKJH0PkPacJZIqH-ttz-rU5ZJRtJiVGT7lnzZfQst-M8WKiiFb6At_TcSpC9kDCLuTD0RFY>
> and report their findings on various platforms, especially repeating your
> test on *macOS*
>
> Thank you
>
> Peter
>
> [image: image.png]
> [image: image.png]
>
>
>
>
> On Mon, 30 Oct 2023 at 18:54, Jody Garnett  wrote:
>
>> Thanks,
>>
>> Testing locally:
>>
>> java -cp "lib/*" org.geotools.util.factory.GeoTools
>>>
>>
>> Works as expected.
>>
>> However:
>>
>> mkdir bin
>>>
>> javac -cp "lib/*" -d bin
>>> src/org/geotools/tutorial/quickstart/Quickstart.java
>>
>> java -cp "lib/*;bin" org.geotools.tutorial.quickstart.Quickstart
>>>
>>
>> This compiles and runs, but I am not being shown the file chooser to
>> display a file... perhaps someone can test in another environment also.
>> --
>> Jody Garnett
>>
>>
>> On Oct 30, 2023 at 9:21:12 AM, Peter Smythe  wrote:
>>
>>> Hi GeoServer developers
>>>
>>> As part of the release process, we would appreciate you taking a few
>>> minutes to test the latest build artefacts prior to the formal release in
>>> approximately 12 hour's time, if that is at all possible.
>>>
>>>
>>> https://build.geoserver.org/view/release/job/geoserver-release/lastBuild/artifact/distribution/2.23.3/
>>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/WoO8gCZff4Eby_7cX2sXIZHOqtcuRjRdMdpTMJJQopZIAd8r3rpYACI4-MRNuZGX1efiq1-wv_TOqSEXAZfGk9nVhQni_gbsEY-r9pFLIeyCSB17ErahicymM_rRYBnaoXO0MSicH6W8JVZbT03yGfCS4Iie_-2driPmamqOFtvrWNsa499AWNv3HSuMTXjlQAVD1KaH6iWYEPtGUMBHsOr1zMtxK3BD1VsC3dSMWap0S6MjRSxmPxw7BvVL5P7xwM4RgGephRu5Ow-WCirp9iyEfUQ50puxchQKcHo30Q3gHEYeHu21J0q62Y4FFactosJfRmLrg-jvPBBZcheyT0VXiDW0p9bz6w>
>>>
>>> Thank you
>>>
>>> Peter
>>> ___
>>> Geoserver-devel mailing list
>>> geoserver-de...@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/x1DhI5y-y_uWpfYBtnlF4G5iV-fdDydLrV5lzvpg_DV53ceIrWbWRoq7mZwpgZhMx0_d_VvzaYZNYOVeA1pTpttLyuQKsRMwy6mwPkwBqiVaqYI__ubpx2NoulGTCh92ajGXftyz5Afi4SL83DZ7Y7oQi6l5E9ay-YEkY3y3I767nKYH7DdA3e0uzZm5PSv1IZrWz2UptAS4bHWYzQNXEhSwsa1PjaZrGJEvCO9h7g1XSEDfBcMupuw7iD6mjuI3ptZpnYy7s7qKPAZwcRHaxBJtDg>
>>>
>>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] GeoTools 2024 Sponsorship Opportunities / OSGeo Budget 2024 page

[Jody Garnett]

Hey folks,

I attended the OSGeo board meeting to day to check in on CRA communication
(interesting to think about what regulation would mean to a library like
GeoTools). One topic that came up was the OSGeo Annual Budget Request,
which has traditionally used GeoTools as a "good example" 

With that in mind please review draft budget request:

   - GeoTools 2024 Sponsorship Opportunities
   
<https://github.com/geotools/geotools/wiki/GeoTools-2024-Sponsorship-Opportunities>


Notes:

   - For the roadmap challenges outlined above, please see slides
52-55 in recent
   presentation
   
<https://docs.google.com/presentation/d/1clOEsaUBzVVXZqCUHWvbyxPRAgRjSbmsOtCk06Zi068/edit?usp=sharing>
   .
   - I am taking our lessons learned from foss4g and actually asking
   sponsors for money
   - Added a placeholder sponsorship page
   <https://github.com/geotools/geotools/wiki/Sponsorship>to the wiki also.


Please review the above pages.
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] GeoServer/GeoTools PMC Meeting at 18:30 CET / 9:30 PST tomorrow

[Jody Garnett]

 Great!

Jukka: the state of geoserver slides have a nice diagram about the
java/library updgrades and migration challenge. It looks like our deadline
to stay supported is December 2024.

I published the two outstanding CVEs and updated the release announcements:
https://github.com/geoserver/geoserver.github.io/pull/165

(I like the workflow, using CVEs to document mitigation and patch
information is less duplication - and less noise in the release
anouncements). I Also noticed that the CVE-2023-41339
<https://www.google.com/search?client=safari=en=CVE-2023-41339=UTF-8=UTF-8>
record
is still terrible; but links back to the good information we provided via
GitHub advisory database.

--
Jody Garnett


On Oct 24, 2023 at 12:37:28 PM, Torben Barsballe 
wrote:

> As expected, we're cancelling the meeting today due to lack of attendance.
>
> I did take a little bit of time while waiting to go through our action
> items from last meeting - looks like most of them are now done, but there's
> a couple still to-do (let me know if you think I've missed something):
>
>
>-
>
>*[TODO] Jukka: blog post about Java/library upgrades/migrations*
>-
>
>[DONE] Jody: blog post or something for FOSS4GNA, the conference
>provided some “social assets”
>-
>
>[DONE] Jody: GEOS-11134 - work on license file fix
>-
>
>[DONE] Joseph Miller: GEOT-7434 - working on fix, trying to get in
>before 2.24.0
>-
>
>*[TODO] Janne Korhonen: Send an email to the list about new OGCFeat
>datastore and getting that added as a community module*
>
>
> Cheers,
> Torben
>
> On Tue, Oct 24, 2023 at 7:56 AM Torben Barsballe <
> torbenbarsba...@gmail.com> wrote:
>
>> Thanks for the heads up. We'll see what attendance is looking like in the
>> first five minutes or so, and make a decision to cancel (or not) after that.
>>
>> Cheers,
>> Torben
>>
>> On Mon, Oct 23, 2023 at 7:48 PM Jody Garnett 
>> wrote:
>>
>>> Given foss4gna is ongoing I expect we may need to cancel? Andrea and
>>> myself are at foss4gna - and it technically the lunch break (12:30 local
>>> time) so we may drop-in and say hi!
>>>
>>>
>>> --
>>> Jody Garnett
>>>
>>>
>>> On Oct 23, 2023 at 10:23:40 PM, Torben Barsballe <
>>> torbenbarsba...@gmail.com> wrote:
>>>
>>>> Reminder that the next PMC meeting is scheduled for tomorrow, October
>>>> 24, at 18:30
>>>> <https://www.timeanddate.com/worldclock/fixedtime.html?year=2023=10=24=18=30=0=GeoTools%20/%20GeoServer%20Meeting=1=1=215>
>>>>  CET.
>>>>
>>>> Cheers,
>>>> Torben
>>>> ___
>>>> GeoTools-Devel mailing list
>>>> GeoTools-Devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>>
>>>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] GeoServer/GeoTools PMC Meeting at 18:30 CET / 9:30 PST tomorrow

[Jody Garnett]

 Given foss4gna is ongoing I expect we may need to cancel? Andrea and
myself are at foss4gna - and it technically the lunch break (12:30 local
time) so we may drop-in and say hi!


--
Jody Garnett


On Oct 23, 2023 at 10:23:40 PM, Torben Barsballe 
wrote:

> Reminder that the next PMC meeting is scheduled for tomorrow, October 24,
> at 18:30
> <https://www.timeanddate.com/worldclock/fixedtime.html?year=2023=10=24=18=30=0=GeoTools%20/%20GeoServer%20Meeting=1=1=215>
>  CET.
>
> Cheers,
> Torben
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] GeoTools 30.0 released

[Jody Garnett]

GeoTools 30.0 has been released as the new stable release of the library -
more details (and a fun diagram) in the release announcement
<http://geotoolsnews.blogspot.com/2023/10/geotools-300-released.html>.  The
release is available for download and directly from maven.

This update features an api-break due to the refactor of the org.opengis
package to org.geotools.api package (along with associated cleanup).
The upgrade
instructions
<https://docs.geotools.org/stable/userguide/welcome/upgrade.html> include a
well-tested script you may use on your codebase.  We would like to thank
Ian Turton, Andrea Aime and Jody Garnett for completing this activity, and
everyone who helped test the release candidate.

Thanks to Peter Smith and Jody Garnett for making this release.
--
Project Management Committee
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Where did the historical downloads go

[Jody Garnett]

 I was missing something - all the content is here
https://sourceforge.net/projects/geotools/files/

No idea what geotools.mirror is (huh)
--
Jody Garnett


On Oct 15, 2023 at 10:11:31 AM, Jody Garnett  wrote:

> I was prepping a diagram for our upcoming 30.0 announcement .. and notice
> that source forge only has very recent downloads?
>
> Am I missing something?
> https://sourceforge.net/projects/geotools.mirror/files/
>
> Github has a longer history https://github.com/geotools/geotools/releases,
> but I thought we were using sorceforge for long term storage / archive .
> --
> Jody Garnett
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] Where did the historical downloads go

[Jody Garnett]

I was prepping a diagram for our upcoming 30.0 announcement .. and notice
that source forge only has very recent downloads?

Am I missing something?
https://sourceforge.net/projects/geotools.mirror/files/

Github has a longer history https://github.com/geotools/geotools/releases,
but I thought we were using sorceforge for long term storage / archive .
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] Release trains progress

[Jody Garnett]

Peter:

I have released:

   - GeoTools 30.0 to maven / source forge (so artifacts were available for
   downstream projects)
   -
   https://github.com/mapfish/mapfish-print-v2/releases/tag/release%2F2.3.0
   - https://github.com/GeoWebCache/geowebcache/releases/tag/1.24.0


There is one PR to review, merge and backport here:
https://github.com/geoserver/geoserver/pull/7183

Over to you 

I did see one alarming bug report from Andrea but it is unclear to me if
this is regression for downstream code:
https://osgeo-org.atlassian.net/browse/GEOT-7475
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] pull-request to update docs for 30.x refactor

[Jody Garnett]

I have been looking at anything else holding us back from releasing 30.0.

   - Although I had remembered seeing a Point2D based implementation on
   Position I could not find it today
   - The docs still referenced gt-opengis, here is a pull-request to update
   diagrams and page headings:
   https://github.com/geotools/geotools/pull/4514

--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Github Workflow integration.yml throwing error

[Jody Garnett]

 There was a pull-request to fix
https://github.com/geotools/geotools/pull/4500 (I had made similar changes
before noticing it.)

I am not sure how to ask existing pull-request to re-run, for some reason
it does not appear to be an option.
--
Jody Garnett


On Oct 7, 2023 at 8:42:43 AM, Joseph Miller  wrote:

> Not sure who is maintaining the GeoTools Github Workflow scripts, but
> heads up that the integration.yml is causing an issue at the following line:
> run: mvn -B
> -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn
> clean install -T2 -Dall --file pom.xml -DskipTests
>
> Example is from:
> https://github.com/geotools/geotools/actions/runs/6442027923/workflow
>
> Thanks,
> Joe Miller
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] mkdocs proposal

[Jody Garnett]

 Andrea:


   1. To migrate GeoTools I need to make one major improvement to the
   script -> processing the include-source directives into an equivalent
   mkdocs extension.


Material for MkDocs recommends
<https://squidfunk.github.io/mkdocs-material/setup/extensions/python-markdown-extensions/#snippets>
the pymdownx.snippets extension, but it seems odd.

   - We include using comments in the example code, and start / before
   pattern matching
   - The --8<-- marker that looks like a pair of scissors is cute!
   - Snippets has a cool feature where you can *name* the snippet in the
   example code:
   // --8<-- [start:dataStore]
   DataStore store = DataStoreFinder
   // --8<-- [end:dataStore]

   And then include it using:
   --8<-- "include.md:name"


Stack exchange recommended mkdocs-include-markdown-plugin and I got it to
work:

   - It matches our existing workflow, but is not as cute
   - It provides two things include-markdown, and include (for example code)


Mkdocs-macros <https://mkdocs-macros-plugin.readthedocs.io> seems to turn
mkdocs into a mini templating framework and is too complicated to live

   - The only thing that would be good here is the ability to re-create
   |project| and |version| equivalents



   1. I plan to socialize in GeoServer when I have a chance to define what
   is needed:



   - In addition to code examples we have some very complicated "download"
   external-link directive in GeoServer (with may need to be replaced with
   simple markdown, or worthwhile maintaining using mkdocs-macros
   - I can share the geotools proposal with the geotools-devel list



   1. I did include the geonetwork result in the proposal and initial
   email. But you are correct that it was a generic sphinx-build theme ant not
   he best comparison.



   - Sphinx-build generic theme:

   
https://geonetwork-opensource.org/manuals/4.0.x/en/user-guide/describing-information/creating-metadata.html
   - Sphinx-build read-the-docs with custom colours:

   
https://www.geocat.net/docs/geonetwork-enterprise/2022/geonetwork/community/user-guide/describing-information/creating-metadata.html
   https://metadata101.github.io/iso19139.ca.HNAP/search/records.html
   - Material for MkDocs:

   
https://docs.geonetwork-opensource.org/4.2/user-guide/describing-information/creating-metadata/
   https://docs.geonetwork-opensource.org/4.2/help/search/


The selected "Material for MkDocs
<https://squidfunk.github.io/mkdocs-material/>" (be sure to scroll down the
home page). This is by far the most established and best supported theme.
Indeed it is so well done it is almost a separate environment to mkdocs;
and has excellent documentation.

Making it "fun" is a little up to styling and getting some time from Michel
 Indeed his evaluation of the different documentation options, and
enthusiasm for Material for MkDocs, is a key enabler for this proposal.

I fund many of the reference examples
<https://squidfunk.github.io/mkdocs-material/reference/> fun:

   - The little icons, and the ability to define your own
   <https://squidfunk.github.io/mkdocs-material/reference/icons-emojis/>
   - Linked tabbed code example things
   <https://squidfunk.github.io/mkdocs-material/reference/content-tabs/>
   - A big thing for geoserver could be the language chooser, and the
   version chooser which was a decider for geonetwork


--
Jody Garnett


On Oct 2, 2023 at 6:30:32 AM, Andrea Aime 
wrote:

> Hì Jody,
> I'm all for the simplest possible approach to writing documentation, and
> one less syntax to master is a benefit.
>
> Some questions:
>
>- The automation is impressive, how much work do you reckon it would
>be migrate GeoTools?
>- Could you also socialize the idea in GeoServer, so that we get more
>points of view? It would not be good to do a GT migration but not a GS one
>- I'm trying to figure out how much we'll have to compromise in terms
>of output, and wanted to find out how good the output would be. I know you
>recently did a GeoNetwork migration but I don't see the results.
>
> In particular, the current Geonetwork guide seems to be built with sphinx
> using the "read the docs" theme (which I find depressing and sickening,
> looks like a backwater python library):
> https://geonetwork-opensource.org/manuals/4.0.x/en/index.html
>
> The example that was linked from the Geonetwork proposal is a bit more
> lively, though still pretty bland:
> https://jodygarnett.github.io/iso19139.ca.HNAP/search/records/
>
> Can we get something a bit more upbeat/colorful like we have today
> (thinking more of the Geoserver docs here)?
> Or are the themes hard to update?
>
> Cheers
> Andrea
>
>
> On Mon, Oct 2, 2023 at 1:00 AM Jody Garnett 
> wrote:
>
>> Going to run an experiment tomorrow and 

[Geotools-devel] mkdocs proposal

[Jody Garnett]

Going to run an experiment tomorrow and have written it up as a proposal to
protect the innocent:

   - https://github.com/geotools/geotools/wiki/MkDocs
   - https://osgeo-org.atlassian.net/browse/GEOT-7466


If successful it would be a good time to change the format of the docs. Due
to API change I do not anticipate a lot of changes being back ported to the
maintenance branch this release cycle (so the overhead of changing from
reStructuedText to Markdown).

If you already like Markdown you can skip the proposal and just look:

   - Compare example sphinx-build
   <https://geonetwork-opensource.org/manuals/4.0.x/en/overview/index.html>
vs mkdocs <https://jodygarnett.github.io/core-geonetwork/4.2.5/>
   - Structure is unchanged so existing links to the docs do not break
   - Search actually works

>From the proposal:

The Journey is tough but the destination appears worth it.


   - Previously I learned convert content and not rewrite at the same time
  - This time I learned not to edit at all and made a script
  http://github.com/jodygarnett/translate
  - The script uses pandoc and then cleans up the mess for any
  sphinx-build directives that pandoc cannot support
  - A lot of the work went into reverse engineering doc and ref directives,
  and processing toctree directives that we would not wish to do by
  hand. These are all sphinx-build directives that require knowledge of
  documentation structure beyond a single file.
  - With such a powerful script it was often faster to fix problems in
  RST and re-convert (example for unexpected block quotes due to indenting)


The destination:


   - mkdocs build is faster, and responsive when editing
  - the material theme is very good and well supported
  - mkdocs.yml requires a navigation tree of all pages (but there may
  be a plugin to glob *.md files)
  - Amazing: the search actually works
  - Disappointing: We give up some explicit features (guilabel,
  menuselection, file, download) and can make do with a clear writing
  guideline. It seems I may of been the only person appreciating these
  capabilities of sphinx-build
  - Great: Some of the advanced features we enjoy like literal-include
  are covered by markdown extensions
  - Bonus: version management for docs is much nicer


Markdown is less expressive than sphinx-build, so we have to rely on a
strong writing guideline to capture conventions that are no longer enforced
by inline directives

--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] release candidate starting

[Jody Garnett]

 And here is mapfish-print-v2: 2.3-RC Release Candidate
<https://github.com/mapfish/mapfish-print-v2/releases/tag/release%2F2.3-RC>

Both GeoTools 30-RC and mapfish-print-v2 2.3-RC are now available in maven.

Over to you Andrea!
--
Jody Garnett


On Sep 22, 2023 at 12:17:37 AM, Jody Garnett  wrote:

> As the release process is being split over several days there the build
> jobs for "main" will be disabled for a bit.
>
> If you are merging any PRs be sure to backport to the new geotools 30.x
> branch.
>
> Nightly build had the following revisions:
>
> version = 2.24-SNAPSHOT
>>
> git revision = 73b838957c2d729b022ab71067efb2c9f5383970
>>
> git branch = origin/main
>>
> build date = 19-Sep-2023 08:33
>>
> geotools version = 30-SNAPSHOT
>>
> geotools revision = 978072bbd191de05422e0429d3726a97f8768cf6
>>
> geowebcache version = 1.24-SNAPSHOT
>>
> geowebcache revision = 9258fe614a0e90f9fbab1c453534d965bcd71aa6/9258fe6
>>
>
> Adding to that:
>
> geofence revision: 07471ad789725d570d7d4131174e465a2951
>>
> Mapfish-print-v2 revision: 0b6631f87388b7ee88e9e2948814388e0255bacb
>
>
>
> GeoTools 30-RC1
>
>- rev: c531ba6b8b81aba859d5bbd3fab14265ded33ef3
>(revision updates on new branch because of transition of pom.xml
>series from "latest" to "stable", and some problems with assembly)
>- branch: 30.x build and docs are green
>- main: 31.x build and docs are green
>- branch: 29.x: should build docs to maintenance
>- branch: 28.x: should stop building docs
>
>
> Artifacts are available for testing here:
>
>
> https://build.geoserver.org/view/release/job/geotools-release/lastSuccessfulBuild/artifact/build/release/distribution/30-RC/
>
> Next up mapfish-print-v2 2.3-RC1
>
>- rev: 07471ad789725d570d7d4131174e465a2951
>- branch: main
>
>
> --
> Jody Garnett
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] release candidate starting

[Jody Garnett]

As the release process is being split over several days there the build
jobs for "main" will be disabled for a bit.

If you are merging any PRs be sure to backport to the new geotools 30.x
branch.

Nightly build had the following revisions:

version = 2.24-SNAPSHOT
>
git revision = 73b838957c2d729b022ab71067efb2c9f5383970
>
git branch = origin/main
>
build date = 19-Sep-2023 08:33
>
geotools version = 30-SNAPSHOT
>
geotools revision = 978072bbd191de05422e0429d3726a97f8768cf6
>
geowebcache version = 1.24-SNAPSHOT
>
geowebcache revision = 9258fe614a0e90f9fbab1c453534d965bcd71aa6/9258fe6
>

Adding to that:

geofence revision: 07471ad789725d570d7d4131174e465a2951
>
Mapfish-print-v2 revision: 0b6631f87388b7ee88e9e2948814388e0255bacb



GeoTools 30-RC1

   - rev: c531ba6b8b81aba859d5bbd3fab14265ded33ef3
   (revision updates on new branch because of transition of pom.xml series
   from "latest" to "stable", and some problems with assembly)
   - branch: 30.x build and docs are green
   - main: 31.x build and docs are green
   - branch: 29.x: should build docs to maintenance
   - branch: 28.x: should stop building docs


Artifacts are available for testing here:

https://build.geoserver.org/view/release/job/geotools-release/lastSuccessfulBuild/artifact/build/release/distribution/30-RC/

Next up mapfish-print-v2 2.3-RC1

   - rev: 07471ad789725d570d7d4131174e465a2951
   - branch: main


--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Seeking assistance with release-candidate to update build server and branches

[Jody Garnett]

The downstream GeoNode / MapStore test seems to have been completed … 2
hours ago.  Many of the other projects have reported back successfully - it
was the right call to contact projects via their issue trackers.

With positive response (and great engagement from affected projects) the RC
can go ahead next week.

Thanks to everyone for making such a big change happen smoothly.

Personal thanks to Ian and Andrea for their dedication and discernment on
all the judgement calls just of the sprint.

Jody

On Tue, Sep 12, 2023 at 2:59 PM Jody Garnett  wrote:

> Follow up to today's meeting, I am seeking assistance making the release
> candidate for GeoTools 30-RC. This is a big jump for the GeoTools project
> and I would like it to go smoothly.
>
> It generally takes 1/2 day to make a release, however making a release
> candidate involves more moving pieces and can take a full day to sort out.
>
>
>1. We need some branch and build server help:
>   1. Make new branches for 30.x (and downstream projects...)
>   2. Setup new jobs for geotools-30.x on the build server
>   2. The actual release steps are bit more involved this time:
>   1. Release geotools 30-RC1
>   2. Jody: Release https://github.com/geoserver/geofence 3.6-RC
>   3. Jody: Release https://github.com/mapfish/mapfish-print-v2 2.3-RC
>   4. Release https://github.com/GeoWebCache/geowebcache 1.3-RC
>   5. Release https://github.com/geoserver/geoserver 2.24-RC
>
>
> We are presently waiting on feedback from GeoNode testing here:
> https://github.com/geosolutions-it/mapfish-print/issues/65
>
>- It would be good to wait until Tobia Di Pisa has completed
>testing before making the release-candidate
>
>
> How to help:
>
>- We need a volunteer for (1) above
>- Please test the update instructions on your GeoTools based project
>- Docs can really use some attention, new svg diagrams of the module
>structure, search for org.opengis in the code examples, etc...
>
>
> --
> Jody Garnett
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] ESRI Shapefile driver read charset from *.cpg file

[Jody Garnett]

That would be a welcome improvement :)

Have you read our contribution policy, did you have any questions?

On Thu, Sep 14, 2023 at 12:45 PM Burkhard Strauss 
wrote:

> Some providers of ESRI Shapefile data provide an additional *.cpg-file
> containing the character set name for string-fields in the *.dbf-file.
> One such provider is HERE/NavStreets street map data.
>
> Currently the API-user has to specify a Charset to the
> ShapefileDataStoreFactory to ensure properly read string values. The
> application has to ask the application-user to look up the Charset in
> the *.cpg-file and copy or type the name. That's rather awkward.
>
> I prepared a solution which adds 15 lines to ShapefileDataStoreFactory
> plus a unit-test and test-data. If a file named .cpg is
> present beside .dbf and the other files, and the Charset
> can be determined from the file without error, a possibly present
> factory parameter is ignored and overridden by the Charset found in the
> file.
>
> What do you think?
>
> Regards
> Burkhard
>
>
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Seeking assistance with release-candidate to update build server and branches

[Jody Garnett]

 Thanks Andrea,

The main overhead is setting up new jobs/branches. I am not available that
weekend, but maybe we can split things up so I am out of the way for you to
make the release?

*Thursday 21 September:*

   - Jody: GeoTools 30.x branch and geotools-30.x and geotools-30.x-docs
   jobs
   - Jody: GeoTools 30-RC1 release
   - Jody: mapfish-print-v2 2.3-RC

*Friday 22 September*

   - Andrea: geofence 3.6-RC (jobs and branch)
   - Andrea: gwc 1.3-RC (jobs and branch)
   - Andrea: geoserver 2.24-RC (jobs and branch


Plan?
--
Jody Garnett


On Sep 13, 2023 at 8:16:29 AM, Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> Hi Jody,
> I'll have time to work on the release next Friday, September 22nd,
> hopefully
> with Alessandro's assistance. Unless anyone beats me to the punch and does
> it sooner? 
>
> Cheers
> Andrea
>
> On Wed, Sep 13, 2023 at 12:00 AM Jody Garnett 
> wrote:
>
>> Follow up to today's meeting, I am seeking assistance making the release
>> candidate for GeoTools 30-RC. This is a big jump for the GeoTools project
>> and I would like it to go smoothly.
>>
>> It generally takes 1/2 day to make a release, however making a release
>> candidate involves more moving pieces and can take a full day to sort out.
>>
>>
>>1. We need some branch and build server help:
>>   1. Make new branches for 30.x (and downstream projects...)
>>   2. Setup new jobs for geotools-30.x on the build server
>>   2. The actual release steps are bit more involved this time:
>>   1. Release geotools 30-RC1
>>   2. Jody: Release https://github.com/geoserver/geofence 3.6-RC
>>   3. Jody: Release https://github.com/mapfish/mapfish-print-v2 2.3-RC
>>   4. Release https://github.com/GeoWebCache/geowebcache 1.3-RC
>>   5. Release https://github.com/geoserver/geoserver 2.24-RC
>>
>>
>> We are presently waiting on feedback from GeoNode testing here:
>> https://github.com/geosolutions-it/mapfish-print/issues/65
>>
>>- It would be good to wait until Tobia Di Pisa has completed
>>testing before making the release-candidate
>>
>>
>> How to help:
>>
>>- We need a volunteer for (1) above
>>- Please test the update instructions on your GeoTools based project
>>- Docs can really use some attention, new svg diagrams of the module
>>structure, search for org.opengis in the code examples, etc...
>>
>>
>> --
>> Jody Garnett
>> ___
>> GeoTools-Devel mailing list
>> GeoTools-Devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
>
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] Seeking assistance with release-candidate to update build server and branches

[Jody Garnett]

Follow up to today's meeting, I am seeking assistance making the release
candidate for GeoTools 30-RC. This is a big jump for the GeoTools project
and I would like it to go smoothly.

It generally takes 1/2 day to make a release, however making a release
candidate involves more moving pieces and can take a full day to sort out.


   1. We need some branch and build server help:
  1. Make new branches for 30.x (and downstream projects...)
  2. Setup new jobs for geotools-30.x on the build server
  2. The actual release steps are bit more involved this time:
  1. Release geotools 30-RC1
  2. Jody: Release https://github.com/geoserver/geofence 3.6-RC
  3. Jody: Release https://github.com/mapfish/mapfish-print-v2 2.3-RC
  4. Release https://github.com/GeoWebCache/geowebcache 1.3-RC
  5. Release https://github.com/geoserver/geoserver 2.24-RC


We are presently waiting on feedback from GeoNode testing here:
https://github.com/geosolutions-it/mapfish-print/issues/65

   - It would be good to wait until Tobia Di Pisa has completed
   testing before making the release-candidate


How to help:

   - We need a volunteer for (1) above
   - Please test the update instructions on your GeoTools based project
   - Docs can really use some attention, new svg diagrams of the module
   structure, search for org.opengis in the code examples, etc...


--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] GeoServer/GeoTools PMC Meeting Notes 2023-09-12

[Jody Garnett]

GeoTools / GeoServer PMC meeting - 2023-09-12Attending

   -

   Torben Barsballe
   -

   Jody Garnett
   -

   Andrea Aime
   -

   Kevin Smith

Actions from prior meetings:

   -

   [DONE] Code Sprint: Merge styling changes, prepare for RC

Agenda

   -

   Build-server care and feeding
   -

   Translation Question
   -

   Security vulnerability proposal
   -

   Release candidate
   -

   Oddments and questions

Actions

   -

   action: Discuss with Alexandre Gacon on the geoserver-devel list about
   translation
   -

   action: Ask on the geoserver-devel list for assistance setting up new
   branches and jobs

Build-server care and feeding

   -

   Gabe for Java 17?
   -

  This is easy enough to add through the Jenkins interface
  -

   Jody fixed a few jobs that now require Java 11
   -

   I think it is happy?

Translation Question

Q: Regina asks if we need help on weblate.osgeo.org ?

A: Alex had an experiment going, they are now in communication

action: Let’s discuss with Alexandre Gacon on the geoserver-devel list
about translation :)
Security vulnerability proposal

We have been successful with the “private vulnerability report”, and this
allows us to make our own CVE numbers which we control.

But there are lots we do not control:
https://github.com/advisories?query=geoserver

Here is a policy change with this in mind:
https://github.com/geoserver/geoserver/wiki/GSIP-220

How to handle GHSA-cqpc-x2c6-2gmfGHSA-cqpc-x2c6-2gmf:

   -

   The number https://cve.report/CVE-2023-41339 shows up as
   not-yet-published
   -

   This is patched in GeoServer 2.23.2 and 2.22.4 already
   -

   Update old announcements with the CVE number when announced?

Release candidate

We need capacity :) Any takers …

   -

   Jody is going to have to be on hand to release mapfish-print-v2:
   -

  Also confirmed he has permission to release geofence to osgeo releases
  (tested with SNAPSHOT jars)
  -

   release candidate requires a bit more than a normal release:
   -

  new branches, new build.geoserver.org jobs, etc …
  -

  anyone else we can ask?


Feedback:

   -

   Nice feedback on the geotools-devel list from Roar
   -

   Andrea fixed some SERVICE-INF/ interfaces - nice 
   -

   Jody noticed Point2D can be removed
   -

   The docs need some love (and diagrams)


action: ask on the geoserver-devel list for assistance setting up new
branches and jobs
Oddments and questions

Jody was looking at displacementMode tests, they have:

  

label



  Bitstream Vera
Sans

  14









0.5

0.5







50

E

conflictResolution

  

Huh? I guess the parser is ignoring … lol :)

That is a vendorOption, but why is it free text :)

false
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Remove opengis: merge underway

[Jody Garnett]

Whew!

I spotted a few things that were missed, or are worth discussion.

There is a Point2D class to remove - we removed Envelop2D already.

FactoryFinders? Are they api or implementation ...

And the docs need help, review, and new pictures.

Jody

On Wed, Sep 6, 2023 at 10:31 PM Roar Brænden 
wrote:

> Hi,
>
> I've gone through my portfolio of GeoTools examples, and this was a
> remarkable effort.
> I haven't found a single issue.
>
> Well done!
>
> Best regards,
> Roar Brænden
>
>
> 6. sep. 2023 kl. 03:37 skrev Jody Garnett :
>
> Merge is complete, build server is chewing over the builds jobs.
>
> The build server build chain for main now looks like: GeoTools > GWC >
> GeoFence > GeoServer to account for snapshot dependencies.
>
> There is a build job for mapfish-print-v2 (
> https://build.geoserver.org/view/geofence/job/mapfish-print-main/)
> however gtbuildergh may require access (
> https://github.com/mapfish/mapfish-print-v2/issues/15) if we wish to
> automate tagging/release.
>
> Code freeze over :)
> --
> Jody Garnett
>
>
> On Sep 5, 2023 at 4:49:20 PM, Jody Garnett  wrote:
>
>> The big bad merge <https://github.com/geotools/geotools/pull/4466> is
>> underway!
>>
>>- draft PRs created in affected downstream projects.
>>- Build jobs are presently disabled
>>
>>
>> if all goes well we can release the code-freeze later today.
>> --
>> Jody Garnett
>>
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
>
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Remove opengis: merge underway

[Jody Garnett]

 Merge is complete, build server is chewing over the builds jobs.

The build server build chain for main now looks like: GeoTools > GWC >
GeoFence > GeoServer to account for snapshot dependencies.

There is a build job for mapfish-print-v2 (
https://build.geoserver.org/view/geofence/job/mapfish-print-main/)
however gtbuildergh may require access (
https://github.com/mapfish/mapfish-print-v2/issues/15) if we wish to
automate tagging/release.

Code freeze over :)
--
Jody Garnett


On Sep 5, 2023 at 4:49:20 PM, Jody Garnett  wrote:

> The big bad merge <https://github.com/geotools/geotools/pull/4466> is
> underway!
>
>- draft PRs created in affected downstream projects.
>- Build jobs are presently disabled
>
>
> if all goes well we can release the code-freeze later today.
> --
> Jody Garnett
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] Remove opengis: merge underway

[Jody Garnett]

The big bad merge <https://github.com/geotools/geotools/pull/4466> is
underway!

   - draft PRs created in affected downstream projects.
   - Build jobs are presently disabled


if all goes well we can release the code-freeze later today.
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] remove opengis: code-complete!

[Jody Garnett]

Hello team,

Now that GitHub is working against I am happy to report we are
"code-complete" 
Watching the test workflow, which can now test gs-printing extension now
mapfish-print-v2 has a maven build.

Then we are into the end-game: creating remove-opengis branches on
downstream projects so everything can be merged.

How does this sound:


   1. Stop all the main Jenkins jobs on build.geoserver.org as it would
   just waste resources
   2. Publish a 30-SNAPSHOT to maven repo.osgeo.org
   3. Confirm downstream PRs now build against 30-SNAPSHOT
   4. Merge GeoTools remove-opengis PR, and downstream PRs
   5. Re-enable GeoTools main jobs and ensure that much builds and
   published SNAPSHOTS to repo.osgeo.org


--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Remove opengis update: code-freeze now, release candidate Monday

[Jody Garnett]

Things started coming together today, with a lot of regex care and feeding.

Unfortunately GitHub is having trouble provisioning workflows:

Warning: Failed to download action
>
'
> https://api.github.com/repos/actions/checkout/tarball/ee0669bd1cc54295c223e0bb666b733df41de1c5
> '.
>
Error: Response status code does not indicate success: 503 (Service
> Unavailable).
>

I am signing off for the day, if GitHub comes back please run jobs for
https://github.com/geotools/geotools/pull/4466 and merge.

--
Jody Garnett


On Sep 3, 2023 at 7:37:08 AM, Jody Garnett  wrote:

> Reminder: GeoTools PMC members please vote on the financial support
> authorization.
>
> Now that the code sprint is done, where did we get to:
>
>- The August 29th meeting notes had a good summary of progress and
>priorities
>- Ian got the styling api duplication resolved which is great (our
>minimum is met)
>- We decided not to make a milestone at the end of the code sprint, as
>we were both out of time and some work had not yet landed
>
>
> To help I volunteered to make the release-candidate "next weekend" as I
> had an upcoming long weekend available. What I did not notice until I
> returned from the code-sprint is ... that long weekend means this Monday!
>
> I am going to recommend we hold off setting up new branches until the
> final release is made; this would result in in a "code freeze" for
> bug/fixes and feedback which I believe is warrented.
>
> With that in mind:
>
>
>- CODE FREEZE (at least until release-candidate, although I recommend
>longer)
>- Check progress with pull-requests with GEOT-7287:
>https://github.com/geotools/geotools/pulls?q=is%3Apr+GEOT-7287
>- Tasks/planning in google docs here
>
> <https://docs.google.com/document/d/12Jcmg49zjMaBz97FXwQ8qKSwUwih3kCWH8wy7dWsA3E/edit?usp=sharing>
>
>
> We REALLY wish to see this release-candidate play tested given the sheer
> amount of changes; our community has not responded well to calls for
> participation/testing and I wish to see this improve.
>
> --
> Jody Garnett
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] [Geoserver-devel] Remove opengis update: code-freeze now, release candidate Monday

[Jody Garnett]

 Simone:

The voting is in the geotools mailing list and is financial only, I was
only trying to remind folks to vote no that email thread.

This email is about logistics as I am trying to communicate what needs to
be done across several projects to make a release candidate.
--
Jody Garnett


On Sep 4, 2023 at 6:33:13 AM, Simone Giannecchini <
simone.giannecch...@geosolutionsgroup.com> wrote:

> Hi Jody,
> It is not super clear to me what we are voting for as there is a mix of
> financial and technical update in this email.
>
> Just to be clear, we are voting solely on the split of the budget you
> proposed in the document?
>
> Looking forward to hearing from you.
>
> Regards,
> Simone Giannecchini
> ==
> Online training classes for GeoNode, GeoServer and MapStore from the
> experts!
> Visit https://www.geosolutionsgroup.com/professional-training/ for more
> information.
> ==
> Ing. Simone Giannecchini
> @simogeo
> Founder/Director GeoSolutions Italy
> President GeoSolutions USA
>
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob:   +39  333 8128928
> US: +1 (845) 547-7905
>
> http://www.geosolutionsgroup.com
> http://twitter.com/geosolutions_it
>
> ---
> 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 Sun, Sep 3, 2023 at 4:37 PM Jody Garnett 
> wrote:
>
>> Reminder: GeoTools PMC members please vote on the financial support
>> authorization.
>>
>> Now that the code sprint is done, where did we get to:
>>
>>- The August 29th meeting notes had a good summary of progress and
>>priorities
>>- Ian got the styling api duplication resolved which is great (our
>>minimum is met)
>>- We decided not to make a milestone at the end of the code sprint,
>>as we were both out of time and some work had not yet landed
>>
>>
>> To help I volunteered to make the release-candidate "next weekend" as I
>> had an upcoming long weekend available. What I did not notice until I
>> returned from the code-sprint is ... that long weekend means this Monday!
>>
>> I am going to recommend we hold off setting up new branches until the
>> final release is made; this would result in in a "code freeze" for
>> bug/fixes and feedback which I believe is warrented.
>>
>> With that in mind:
>>
>>
>>- CODE FREEZE (at least until release-candidate, although I recommend
>>longer)
>>- Check progress with pull-requests with GEOT-7287:
>>https://github.com/geotools/geotools/pulls?q=is%3Apr+GEOT-7287
>>- Tasks/planning in google docs here
>>
>> <https://docs.google.com/document/d/12Jcmg49zjMaBz97FXwQ8qKSwUwih3kCWH8wy7dWsA3E/edit?usp=sharing>
>>
>>
>> We REALLY wish to see this release-candidate play tested given the sheer
>> amount of changes; our community has not responded well to calls for
>> participation/testing and I wish to see this improve.
>>
>> --
>> Jody Garnett
>> ___
>> Geoserver-devel mailing list
>> geoserver-de...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-develSimon
>>
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] Remove opengis update: code-freeze now, release candidate Monday

[Jody Garnett]

Reminder: GeoTools PMC members please vote on the financial support
authorization.

Now that the code sprint is done, where did we get to:

   - The August 29th meeting notes had a good summary of progress and
   priorities
   - Ian got the styling api duplication resolved which is great (our
   minimum is met)
   - We decided not to make a milestone at the end of the code sprint, as
   we were both out of time and some work had not yet landed


To help I volunteered to make the release-candidate "next weekend" as I had
an upcoming long weekend available. What I did not notice until I returned
from the code-sprint is ... that long weekend means this Monday!

I am going to recommend we hold off setting up new branches until the final
release is made; this would result in in a "code freeze" for bug/fixes and
feedback which I believe is warrented.

With that in mind:


   - CODE FREEZE (at least until release-candidate, although I recommend
   longer)
   - Check progress with pull-requests with GEOT-7287:
   https://github.com/geotools/geotools/pulls?q=is%3Apr+GEOT-7287
   - Tasks/planning in google docs here
   
<https://docs.google.com/document/d/12Jcmg49zjMaBz97FXwQ8qKSwUwih3kCWH8wy7dWsA3E/edit?usp=sharing>


We REALLY wish to see this release-candidate play tested given the sheer
amount of changes; our community has not responded well to calls for
participation/testing and I wish to see this improve.

--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] motion: remove-opengis financial support authorization

[Jody Garnett]

+1

And a big thank you to Ian for his work (and re-work) on styling.
--
Jody Garnett


On Aug 29, 2023 at 7:22:03 PM, Jody Garnett  wrote:

> I have contacted the treasurer with respect to costs associated with
> "remove-opengis" proposal - started great success / and great effort last
> week.
>
> Motion: Propose GeoTools PMC authorize up-to $2000 USD to put towards
> travel expenses associated with this activity.
>
> This motion allows the osgeo board to retain some budget for affected
> downstream projects which have not paid attention thus far.
>
>
>    - Andrea Aime
>- Ian Turton
>- Jody Garnett
>- Nuno Oliveira
>    - Simone Giannecchini
>- Torben Barsballe
>
>
> --
> Jody Garnett
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] motion: remove-opengis financial support authorization

[Jody Garnett]

I have contacted the treasurer with respect to costs associated with
"remove-opengis" proposal - started great success / and great effort last
week.

Motion: Propose GeoTools PMC authorize up-to $2000 USD to put towards
travel expenses associated with this activity.

This motion allows the osgeo board to retain some budget for affected
downstream projects which have not paid attention thus far.


   - Andrea Aime
   - Ian Turton
   - Jody Garnett
   - Nuno Oliveira
   - Simone Giannecchini
   - Torben Barsballe


--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] [Geowebcache-devel] GeoTools 28.5 & GeoServer 2.22.5 & GeoWebCache 1.22.3 release

[Jody Garnett]

Thanks!

This should be the final scheduled maintenance release of 22.x series, and
the end of Java 8 support.

Jody

On Mon, Aug 28, 2023 at 1:04 PM Peter Smythe  wrote:

> Good day developers
>
> If you have any fixes that you want included in the upcoming 2.22.5
> GeoServer, 1.22.3 GeoWebCache or 28.5 GeoTools releases, please make sure
> you have backported them and updated the fix version in the Jira ticket
> before Wednesday morning (GMT+2) which is when I plan to start the next
> release cycle.
>
> Thank you
>
> Peter
>
> On Mon, 28 Aug 2023 at 12:52, Andrea Aime 
> wrote:
>
>> Hi Peter,
>> yes please, a volunteer is just what we need!
>> Thanks!
>>
>> Cheers
>> Andrea
>>
>> On Mon, Aug 28, 2023 at 12:17 PM Jody Garnett 
>> wrote:
>>
>>> That would be lovely Peter, please dit the page appropriately.
>>>
>>> We are quite busy with code-sprint (which is going "well" but running
>>> over time allocated).
>>> --
>>> Jody Garnett
>>>
>>>
>>> On Aug 28, 2023 at 10:13:19 AM, Peter Smythe  wrote:
>>>
>>>> Hi all,
>>>>
>>>> I see on https://github.com/geoserver/geoserver/wiki/Release-Schedule
>>>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/0bmVDi9f76HjB2DtNpPd_nlKrlEEzw_pkumf486N2VkxFduceApYvjEQgAqDQcjNmptalf7Y-XrnMHtU8RRTDishqS4_u34IrbJKjceeW39ZgDM4xhEgBsba6GYSxbM8HM_Yr8u26YvWEOJsgossVGBn037-xCzn1pY3Mca4PsmU5lXex-Xcj5X2qNzsuiioYwLj_EmNgpbDo_yeDQAD1k5h-KocgOegIXPY_deNHDUM6a_wUhAc8vavZ7vsZ9vnDD5_sL-YIGs0cRX2ZfT6GfdMnqZX>
>>>> that the above versions were supposed to be released 10 days ago, but there
>>>> is no name against it.
>>>>
>>>> Can I offer to perform this maintenance release some time this week?
>>>>
>>>> Peter
>>>>
>>>
> ___
> Geowebcache-devel mailing list
> geowebcache-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geowebcache-devel
>
-- 
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] GeoTools 28.5 & GeoServer 2.22.5 release manager

[Jody Garnett]

 That would be lovely Peter, please dit the page appropriately.

We are quite busy with code-sprint (which is going "well" but running over
time allocated).
--
Jody Garnett


On Aug 28, 2023 at 10:13:19 AM, Peter Smythe  wrote:

> Hi all,
>
> I see on https://github.com/geoserver/geoserver/wiki/Release-Schedule
> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/0bmVDi9f76HjB2DtNpPd_nlKrlEEzw_pkumf486N2VkxFduceApYvjEQgAqDQcjNmptalf7Y-XrnMHtU8RRTDishqS4_u34IrbJKjceeW39ZgDM4xhEgBsba6GYSxbM8HM_Yr8u26YvWEOJsgossVGBn037-xCzn1pY3Mca4PsmU5lXex-Xcj5X2qNzsuiioYwLj_EmNgpbDo_yeDQAD1k5h-KocgOegIXPY_deNHDUM6a_wUhAc8vavZ7vsZ9vnDD5_sL-YIGs0cRX2ZfT6GfdMnqZX>
> that the above versions were supposed to be released 10 days ago, but there
> is no name against it.
>
> Can I offer to perform this maintenance release some time this week?
>
> Peter
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] bolsena day 1 remove opengis

[Jody Garnett]

Quick update after day one.

Andrea has resolved conflicts with the work done from the foss4g sprint.

Sebastian from camptocamp was on hand to help untangle some
mapfish-print-v2 context. I am looking at resolving some of the differences
that have developed over time between the official release and the copy
used by geonode installations of geoserver.

We are setting up the build chain from GeoTools to GeoWebCache / GeoFence /
mapfish-print-v2 to GeoServer before starting the work in earnest. No sense
in jumping without a parachute.

Thanks for your support and encouragement everyone.

Jody
-- 
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] osgeo board still voting

[Jody Garnett]

With the Bolsena Code Sprint and major refactoring planned for next week
... the OSGeo board motion for 10k funding is not yet completed.

I think we should be prepared to make a motion here on the GeoTools PMC to
cover any shortfall? I will update when I hear back from the OSGeo board.
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] Reminder codebase change next week, get your PRs in this week

[Jody Garnett]

Reminder that some change is expected for the codebase next week.

After this point pull-requests will require some effort to backport. With
that in mind you may wish to focus on getting geotools pull requests in
this week.

It may be wise to consider the codebase "cold" if not "frozen" until
release candidate in September.
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] ResourceStore API workparty

[Jody Garnett]

 Sorry wrong list
--
Jody Garnett


On Aug 1, 2023 at 10:31:05 AM, Jody Garnett  wrote:

> Niel, Gabe:
>
> Our email thread on this topic has explored the topic by now, I think
> action rather than more communication is needed next.
>
> Can we setup a 1/2 day breakout work-party to get this activity underway
> (prior to the Bolsena code sprint and the next release cycle). Even a
> couple hours to get the topic started on a branch would be great.
>
> I am proposing two times below, and am willing to wake up early to see
> this topic move along:
>
>
>1. August 8th
>
> <https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023=8=8=13=0=0=256=45=48>
>  15
>CEST / 11 BRT / 6 PDT
>2. August 15th
>
> <https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023=8=15=13=0=0=256=45=48>:
>15 CEST / 11 BRT / 6 PDT
>
>
> Is this a good idea :)
> --
> Jody Garnett
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] ResourceStore API workparty

[Jody Garnett]

Niel, Gabe:

Our email thread on this topic has explored the topic by now, I think
action rather than more communication is needed next.

Can we setup a 1/2 day breakout work-party to get this activity underway
(prior to the Bolsena code sprint and the next release cycle). Even a
couple hours to get the topic started on a branch would be great.

I am proposing two times below, and am willing to wake up early to see this
topic move along:


   1. August 8th
   
<https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023=8=8=13=0=0=256=45=48>
15
   CEST / 11 BRT / 6 PDT
   2. August 15th
   
<https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023=8=15=13=0=0=256=45=48>:
   15 CEST / 11 BRT / 6 PDT


Is this a good idea :)
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] release failiure - source forge directory structure change

[Jody Garnett]

 I experimented with this today as a background activity; sorry for all the
noise from the build box.

It looks to be differences in how to encode spaces in "GeoTools 29
Releases" folder, various combinations of quotes and spaces are
recommended, command line options (s / --protect-args) to prevent external
shell from processing path etc...

Eventually --protect-args worked so we are back in the game.

As for what changed, I expect a change of the rsync command versions on our
build server or on source forge.


--
Jody Garnett


On Jul 19, 2023 at 9:11:34 AM, Jody Garnett  wrote:

> Oh sorry this is the source forge upload, perhaps source forge directory
> structure changed - do we have a new location in mind?
>
> Jody
>
> On Wed, Jul 19, 2023 at 3:23 AM Ian Turton  wrote:
>
>> I'm fairly sure we ran into this last time too, it seems that the project
>> directory has moved, looking at the docs (
>> https://sourceforge.net/p/forge/documentation/rsync/) it seems that
>> aiming for
>>
>> /home/frs/project/geotools/29.2/
>>
>> Is this a fix that needs to go into main and be backported? Or is it 
>> changing everytime?
>>
>> For this release I can just hand up load but we should really try to fix this
>>
>>
>>
>> Ian
>>
>> --
>> Ian Turton
>> ___
>> GeoTools-Devel mailing list
>> GeoTools-Devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
> --
> --
> Jody Garnett
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] release failiure - source forge directory structure change

[Jody Garnett]

Oh sorry this is the source forge upload, perhaps source forge directory
structure changed - do we have a new location in mind?

Jody

On Wed, Jul 19, 2023 at 3:23 AM Ian Turton  wrote:

> I'm fairly sure we ran into this last time too, it seems that the project
> directory has moved, looking at the docs (
> https://sourceforge.net/p/forge/documentation/rsync/) it seems that
> aiming for
>
> /home/frs/project/geotools/29.2/
>
> Is this a fix that needs to go into main and be backported? Or is it changing 
> everytime?
>
> For this release I can just hand up load but we should really try to fix this
>
>
>
> Ian
>
> --
> Ian Turton
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
-- 
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] release failiure - source forge directory structure change

[Jody Garnett]

Something indeed moved recently, Torben was working on it with the system
admin committee.

Perhaps check the other documentation builds? I am sure we just did not
think about the release documentation being uploaded int the same fashion.

Jody

On Wed, Jul 19, 2023 at 3:23 AM Ian Turton  wrote:

> I'm fairly sure we ran into this last time too, it seems that the project
> directory has moved, looking at the docs (
> https://sourceforge.net/p/forge/documentation/rsync/) it seems that
> aiming for
>
> /home/frs/project/geotools/29.2/
>
> Is this a fix that needs to go into main and be backported? Or is it changing 
> everytime?
>
> For this release I can just hand up load but we should really try to fix this
>
>
>
> Ian
>
> --
> Ian Turton
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
-- 
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Release artefacts for 29.2 for testing

[Jody Garnett]

 Ian, the same test works for me locally. I expect you are mixing up java
compilers on your local machine when testing.

The rest of the bin download looks fine, although the footer says ©
Copyright 2021, Open Source Geospatial Foundation
--
Jody Garnett


On Jul 18, 2023 at 9:44:34 AM, Jody Garnett  wrote:

> Is there chance you compiled Quickstart.java with Java 17 on line one?
> --
> Jody Garnett
>
>
> On Jul 18, 2023 at 9:25:48 AM, Ian Turton  wrote:
>
>> I've run into the following issue:
>>
>> javac -cp "lib/*" -d bin
>> src/org/geotools/tutorial/quickstart/Quickstart.java
>> java -cp "lib/*:bin" org.geotools.tutorial.quickstart.Quickstart
>> Error: LinkageError occurred while loading main class
>> org.geotools.tutorial.quickstart.Quickstart
>> java.lang.UnsupportedClassVersionError:
>> org/geotools/tutorial/quickstart/Quickstart has been compiled by a more
>> recent version of the Java Runtime (class file version 61.0), this version
>> of the Java Runtime only recognizes class file versions up to 55.0
>>
>> Not sure if I need to update my Java?
>> java --version
>> openjdk 11.0.19 2023-04-18
>> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu122.04.1)
>> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu122.04.1,
>> mixed mode, sharing)
>>
>> Or the build server is using Java17? the release job config claims to be
>> using 11.04
>>
>> Can anyone throw any light on this?
>>
>> Ian
>>
>> On Tue, 18 Jul 2023 at 16:44, Jody Garnett 
>> wrote:
>>
>>> Oh hey Ian cool :)
>>>
>>> I was not aware we had a volunteer for the release this month. I would
>>> like to join you to test the geoserver release announcement script , and
>>> can make the GWC release if needed.
>>>
>>> Jody
>>>
>>> On Tue, Jul 18, 2023 at 5:57 AM Ian Turton  wrote:
>>>
>>>> Goto
>>>> https://build.geoserver.org/view/release/job/geotools-release/99/artifact/build/release/distribution/29.2/
>>>>
>>>> Ian
>>>>
>>>> --
>>>> Ian Turton
>>>> ___
>>>> GeoTools-Devel mailing list
>>>> GeoTools-Devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>>
>>> --
>>> --
>>> Jody Garnett
>>>
>>
>>
>> --
>> Ian Turton
>>
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Release artefacts for 29.2 for testing

[Jody Garnett]

 Is there chance you compiled Quickstart.java with Java 17 on line one?
--
Jody Garnett


On Jul 18, 2023 at 9:25:48 AM, Ian Turton  wrote:

> I've run into the following issue:
>
> javac -cp "lib/*" -d bin
> src/org/geotools/tutorial/quickstart/Quickstart.java
> java -cp "lib/*:bin" org.geotools.tutorial.quickstart.Quickstart
> Error: LinkageError occurred while loading main class
> org.geotools.tutorial.quickstart.Quickstart
> java.lang.UnsupportedClassVersionError:
> org/geotools/tutorial/quickstart/Quickstart has been compiled by a more
> recent version of the Java Runtime (class file version 61.0), this version
> of the Java Runtime only recognizes class file versions up to 55.0
>
> Not sure if I need to update my Java?
> java --version
> openjdk 11.0.19 2023-04-18
> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu122.04.1)
> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu122.04.1,
> mixed mode, sharing)
>
> Or the build server is using Java17? the release job config claims to be
> using 11.04
>
> Can anyone throw any light on this?
>
> Ian
>
> On Tue, 18 Jul 2023 at 16:44, Jody Garnett  wrote:
>
>> Oh hey Ian cool :)
>>
>> I was not aware we had a volunteer for the release this month. I would
>> like to join you to test the geoserver release announcement script , and
>> can make the GWC release if needed.
>>
>> Jody
>>
>> On Tue, Jul 18, 2023 at 5:57 AM Ian Turton  wrote:
>>
>>> Goto
>>> https://build.geoserver.org/view/release/job/geotools-release/99/artifact/build/release/distribution/29.2/
>>>
>>> Ian
>>>
>>> --
>>> Ian Turton
>>> ___
>>> GeoTools-Devel mailing list
>>> GeoTools-Devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>
>> --
>> --
>> Jody Garnett
>>
>
>
> --
> Ian Turton
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Release artefacts for 29.2 for testing

[Jody Garnett]

Oh hey Ian cool :)

I was not aware we had a volunteer for the release this month. I would like
to join you to test the geoserver release announcement script , and can
make the GWC release if needed.

Jody

On Tue, Jul 18, 2023 at 5:57 AM Ian Turton  wrote:

> Goto
> https://build.geoserver.org/view/release/job/geotools-release/99/artifact/build/release/distribution/29.2/
>
> Ian
>
> --
> Ian Turton
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
-- 
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] GeoTools Docs Website Maintenance

[Jody Garnett]

 Thanks for working on this Torben :)
--
Jody Garnett


On Jul 5, 2023 at 6:13:41 PM, Torben Barsballe 
wrote:

> The GeoTools Documentation site at docs.geotools.org will briefly be down
> tomorrow (July 6th), while we perform some systems maintenance.
>
> If you can't access the website, this is likely why.
>
>
> Cheers,
> Torben
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Reminder foss4g code sprint this weekend

[Jody Garnett]

 Jody here:

The sprint was a "success", in that we started a branch and were able to
confirm both the approach, and that we believe we can complete the activity
during the Bolsena code sprint
<https://wiki.osgeo.org/wiki/Bolsena_Code_Sprint_2023>.

The branch is here: https://github.com/geotools/geotools/tree/remove-opengis

A PR is being used to perform integration testing:
https://github.com/geotools/geotools/pull/4367

The integration tests are presently failing on mapfish-print-v2 (which is
required for gs-printing module). That project uses an old version of
gradle which is not compatible with Java 11 (See
https://github.com/mapfish/mapfish-print-v2/issues/11).
--
Jody Garnett


On Jun 30, 2023 at 10:14:50 AM, Jody Garnett  wrote:

> Reminder that this weekend is the foss4g code sprint and the first
> activity of this proposal:
> https://github.com/geotools/geotools/wiki/Remove-OpenGIS
>
> This initial sprint is about experimenting and planning.
>
> Thanks!
> Jody
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] Reminder foss4g code sprint this weekend

[Jody Garnett]

Reminder that this weekend is the foss4g code sprint and the first activity
of this proposal:
https://github.com/geotools/geotools/wiki/Remove-OpenGIS

This initial sprint is about experimenting and planning.

Thanks!
Jody
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] [Geoserver-devel] GeoServer/GeoTools PMC Meeting at 18:30 CET / 9:30 PST tomorrow

[Jody Garnett]

 Thanks for the reminder Torben, I have a commitment this evening and do
not believe I can attend.


   - Thanks to Peter for helping with this weeks maintenance release. The
   create a release announcement script will improve with time.
   - I look forward to seeing a few folks in person next week, and working
   on the "Remove OpenGIS" activity during the code sprint.


--
Jody Garnett


On Jun 19, 2023 at 10:14:39 PM, Torben Barsballe 
wrote:

> Reminder that the next PMC meeting is scheduled for tomorrow, June 20, at
> 18:30
> <https://www.timeanddate.com/worldclock/fixedtime.html?year=2023=6=20=18=30=0=GeoTools%20/%20GeoServer%20Meeting=1=1=215>
>  CET.
>
>
> Cheers,
>
> Torben
> ___
> Geoserver-devel mailing list
> geoserver-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Geotools 28.4 preflight testing

[Jody Garnett]

 We are having trouble publishing to source forge as gtbuilder user (well
build.geoserver.org is having trouble).

It looks like the last time this worked wes February; and I expect people
have been manually uploading to SF since then...

Who is responsible for the gtbuilder :)
--
Jody Garnett


On Jun 18, 2023 at 12:17:42 PM, Jody Garnett  wrote:

> Okay the build is fixed up and tested.
>
> Found one issue with the integration tests (with plugin configuration of
> integration test jobs drifting away from geotools baseline over time):
> https://osgeo-org.atlassian.net/browse/GEOT-7382
>
> This is a problem with the build environment rather than the geotools
> release so marking it as a low priority task.
>
> This does not affect stability so I am reporting to jira and moving on to
> *geotools-release-publish-java8* :)
> --
> Jody Garnett
>
>
> On Jun 18, 2023 at 12:11:29 PM, Jody Garnett 
> wrote:
>
>> Lol - yes the job was using Java 11 - and thus the resulting GeoTools
>> could not be used in Java 8 environment (sigh).
>>
>> Creating geotools-release-java8 job to address this  (I do not wish to
>> remember to edit the build configuration each time)
>>
>> Reference:
>> https://www.morling.dev/blog/bytebuffer-and-the-dreaded-nosuchmethoderror/
>> --
>> Jody Garnett
>>
>>
>> On Jun 18, 2023 at 11:42:00 AM, Peter Smythe  wrote:
>>
>>> In testing with Java 8, there is an exception:
>>>
>>> Jun 18, 2023 11:31:23 AM org.geotools.tutorial.quickstart.Quickstart main
>>> INFO: java.util.logging.config.file=null
>>> Exception in thread "main" java.lang.NoSuchMethodError:
>>> java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer;
>>> at
>>> org.geotools.data.shapefile.dbf.DbaseFileHeader.readHeader(DbaseFileHeader.java:577)
>>> at
>>> org.geotools.data.shapefile.dbf.DbaseFileReader.doInit(DbaseFileReader.java:226)
>>> at
>>> org.geotools.data.shapefile.dbf.DbaseFileReader.init(DbaseFileReader.java:186)
>>> at
>>> org.geotools.data.shapefile.dbf.DbaseFileReader.(DbaseFileReader.java:148)
>>> at
>>> org.geotools.data.shapefile.ShapefileSetManager.openDbfReader(ShapefileSetManager.java:132)
>>> at
>>> org.geotools.data.shapefile.ShapefileFeatureSource.readAttributes(ShapefileFeatureSource.java:497)
>>> at
>>> org.geotools.data.shapefile.ShapefileFeatureSource.buildFeatureType(ShapefileFeatureSource.java:454)
>>> at
>>> org.geotools.data.shapefile.ShapefileFeatureStore.buildFeatureType(ShapefileFeatureStore.java:142)
>>> at
>>> org.geotools.data.store.ContentFeatureSource.getAbsoluteSchema(ContentFeatureSource.java:339)
>>> at
>>> org.geotools.data.store.ContentFeatureSource.getSchema(ContentFeatureSource.java:308)
>>> at
>>> org.geotools.data.store.ContentFeatureSource.getSchema(ContentFeatureSource.java:106)
>>> at
>>> org.geotools.tutorial.quickstart.Quickstart.main(Quickstart.java:58)
>>>
>>>
>>> https://www.morling.dev/blog/bytebuffer-and-the-dreaded-nosuchmethoderror/
>>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/pavIjKGP2v1NoavyFkb08GBnGSBbT4z2ldytdkAjmkL5nSBAU6kwavK9v1c-kuZeL8IZq7XtMwNsjJh-K2MIHo93XXOx7_K0Mgqahry4eV2_OCBQN7Zy3rkUI0TJ47V4YQiJt6z_MgyvlYzQcLiQDgx_u6ZvJ2pcSxKs62z43X1BpBnh5nab0bcfDzUyhKCtGeze_ai4EI8KtPDDwh96qYMc0ey-jUJeBIe4O2bjJvAdU2jBmKvZtAYBNmmZ8wnTshKYcc-0WNr2NWiJ-ObAj1bDbE0816MfWHfUrhj6-g4K>
>>>
>>> Jody says we should build using Java 8 not 11, so we're doing the
>>> release again.
>>>
>>>
>>>
>>> On Sun, 18 Jun 2023 at 11:26, Jody Garnett 
>>> wrote:
>>>
>>>> Artifacts are available for preflight testing:
>>>> https://build.geoserver.org/view/release/job/geotools-release/lastSuccessfulBuild/artifact/build/release/distribution/28.4/
>>>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/Npu9wPrT_NFfT1V4FHVjWdmqDNuruxyFF-N4EhVYc8ejUOBKmJGeGT9TljKmhNJKaeohNW_tTLXqo_xp-Hv1Xiv9f71yDqp2k9t5RYnb4T7y-QvlTCvNrgqEW89XYnMl8uz0fnJQrccYZJp4IQClHkxoIerexUTQO-wzVAi1X8xv00San5-CN-S45Hq4eEfFKwUqvjg7eUxwAFZ7sYHBJLDYraOhEJfUOEwLH6Ueo_SkEigkKvEHMai4xBevS6F90X1TSMs7sNvZ3-1wbr1eqiHl96vVQOYaYg2aHjK1qo1mNIxKKnhoMXjvur4uMq-z82rliTUESJzwZ9277QaymtYP-MzljnGSxoc2iP05vrFXGhZfuy0vbKohd0_4NYzazDo>
>>>>
>>>> Thanks Peter for volunteer for today's release :)
>>>> --
>>>> Jody Garnett
>>>> ___
>>>> GeoTools-Devel mailing list
>>>> GeoTools-Devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/hjB9ehvb875uz57iecgLO5qy66TBekrZ0tPqig97GL_bFET-NBQXpjbiluJ775VivddhIxhFq_gVUq8MIgS12qZIIJ1WI4WnAMXgWK27bx3WTpK1JDc-XM3es_d5P62nr9_n9UquXE6X3dIVOweClKw6wjEqtH6g_3HLsjBaPvHsMM3YSyNCb0HSLOLqg3agba63GFNN4lUCaocnZu68-HRorWFCj2oKHk6O1-i5PbrdgnGdxkt2sDCh5ry3gnahxzdMNmH3dk-hOAIHBQamfOUI>
>>>>
>>>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Geotools 28.4 preflight testing

[Jody Garnett]

 Okay the build is fixed up and tested.

Found one issue with the integration tests (with plugin configuration of
integration test jobs drifting away from geotools baseline over time):
https://osgeo-org.atlassian.net/browse/GEOT-7382

This is a problem with the build environment rather than the geotools
release so marking it as a low priority task.

This does not affect stability so I am reporting to jira and moving on to
*geotools-release-publish-java8* :)
--
Jody Garnett


On Jun 18, 2023 at 12:11:29 PM, Jody Garnett  wrote:

> Lol - yes the job was using Java 11 - and thus the resulting GeoTools
> could not be used in Java 8 environment (sigh).
>
> Creating geotools-release-java8 job to address this  (I do not wish to
> remember to edit the build configuration each time)
>
> Reference:
> https://www.morling.dev/blog/bytebuffer-and-the-dreaded-nosuchmethoderror/
> --
> Jody Garnett
>
>
> On Jun 18, 2023 at 11:42:00 AM, Peter Smythe  wrote:
>
>> In testing with Java 8, there is an exception:
>>
>> Jun 18, 2023 11:31:23 AM org.geotools.tutorial.quickstart.Quickstart main
>> INFO: java.util.logging.config.file=null
>> Exception in thread "main" java.lang.NoSuchMethodError:
>> java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer;
>> at
>> org.geotools.data.shapefile.dbf.DbaseFileHeader.readHeader(DbaseFileHeader.java:577)
>> at
>> org.geotools.data.shapefile.dbf.DbaseFileReader.doInit(DbaseFileReader.java:226)
>> at
>> org.geotools.data.shapefile.dbf.DbaseFileReader.init(DbaseFileReader.java:186)
>> at
>> org.geotools.data.shapefile.dbf.DbaseFileReader.(DbaseFileReader.java:148)
>> at
>> org.geotools.data.shapefile.ShapefileSetManager.openDbfReader(ShapefileSetManager.java:132)
>> at
>> org.geotools.data.shapefile.ShapefileFeatureSource.readAttributes(ShapefileFeatureSource.java:497)
>> at
>> org.geotools.data.shapefile.ShapefileFeatureSource.buildFeatureType(ShapefileFeatureSource.java:454)
>> at
>> org.geotools.data.shapefile.ShapefileFeatureStore.buildFeatureType(ShapefileFeatureStore.java:142)
>> at
>> org.geotools.data.store.ContentFeatureSource.getAbsoluteSchema(ContentFeatureSource.java:339)
>> at
>> org.geotools.data.store.ContentFeatureSource.getSchema(ContentFeatureSource.java:308)
>> at
>> org.geotools.data.store.ContentFeatureSource.getSchema(ContentFeatureSource.java:106)
>> at
>> org.geotools.tutorial.quickstart.Quickstart.main(Quickstart.java:58)
>>
>> https://www.morling.dev/blog/bytebuffer-and-the-dreaded-nosuchmethoderror/
>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/pavIjKGP2v1NoavyFkb08GBnGSBbT4z2ldytdkAjmkL5nSBAU6kwavK9v1c-kuZeL8IZq7XtMwNsjJh-K2MIHo93XXOx7_K0Mgqahry4eV2_OCBQN7Zy3rkUI0TJ47V4YQiJt6z_MgyvlYzQcLiQDgx_u6ZvJ2pcSxKs62z43X1BpBnh5nab0bcfDzUyhKCtGeze_ai4EI8KtPDDwh96qYMc0ey-jUJeBIe4O2bjJvAdU2jBmKvZtAYBNmmZ8wnTshKYcc-0WNr2NWiJ-ObAj1bDbE0816MfWHfUrhj6-g4K>
>>
>> Jody says we should build using Java 8 not 11, so we're doing the release
>> again.
>>
>>
>>
>> On Sun, 18 Jun 2023 at 11:26, Jody Garnett 
>> wrote:
>>
>>> Artifacts are available for preflight testing:
>>> https://build.geoserver.org/view/release/job/geotools-release/lastSuccessfulBuild/artifact/build/release/distribution/28.4/
>>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/Npu9wPrT_NFfT1V4FHVjWdmqDNuruxyFF-N4EhVYc8ejUOBKmJGeGT9TljKmhNJKaeohNW_tTLXqo_xp-Hv1Xiv9f71yDqp2k9t5RYnb4T7y-QvlTCvNrgqEW89XYnMl8uz0fnJQrccYZJp4IQClHkxoIerexUTQO-wzVAi1X8xv00San5-CN-S45Hq4eEfFKwUqvjg7eUxwAFZ7sYHBJLDYraOhEJfUOEwLH6Ueo_SkEigkKvEHMai4xBevS6F90X1TSMs7sNvZ3-1wbr1eqiHl96vVQOYaYg2aHjK1qo1mNIxKKnhoMXjvur4uMq-z82rliTUESJzwZ9277QaymtYP-MzljnGSxoc2iP05vrFXGhZfuy0vbKohd0_4NYzazDo>
>>>
>>> Thanks Peter for volunteer for today's release :)
>>> --
>>> Jody Garnett
>>> ___
>>> GeoTools-Devel mailing list
>>> GeoTools-Devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/hjB9ehvb875uz57iecgLO5qy66TBekrZ0tPqig97GL_bFET-NBQXpjbiluJ775VivddhIxhFq_gVUq8MIgS12qZIIJ1WI4WnAMXgWK27bx3WTpK1JDc-XM3es_d5P62nr9_n9UquXE6X3dIVOweClKw6wjEqtH6g_3HLsjBaPvHsMM3YSyNCb0HSLOLqg3agba63GFNN4lUCaocnZu68-HRorWFCj2oKHk6O1-i5PbrdgnGdxkt2sDCh5ry3gnahxzdMNmH3dk-hOAIHBQamfOUI>
>>>
>>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Geotools 28.4 preflight testing

[Jody Garnett]

 Lol - yes the job was using Java 11 - and thus the resulting GeoTools
could not be used in Java 8 environment (sigh).

Creating geotools-release-java8 job to address this  (I do not wish to
remember to edit the build configuration each time)

Reference:
https://www.morling.dev/blog/bytebuffer-and-the-dreaded-nosuchmethoderror/
--
Jody Garnett


On Jun 18, 2023 at 11:42:00 AM, Peter Smythe  wrote:

> In testing with Java 8, there is an exception:
>
> Jun 18, 2023 11:31:23 AM org.geotools.tutorial.quickstart.Quickstart main
> INFO: java.util.logging.config.file=null
> Exception in thread "main" java.lang.NoSuchMethodError:
> java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer;
> at
> org.geotools.data.shapefile.dbf.DbaseFileHeader.readHeader(DbaseFileHeader.java:577)
> at
> org.geotools.data.shapefile.dbf.DbaseFileReader.doInit(DbaseFileReader.java:226)
> at
> org.geotools.data.shapefile.dbf.DbaseFileReader.init(DbaseFileReader.java:186)
> at
> org.geotools.data.shapefile.dbf.DbaseFileReader.(DbaseFileReader.java:148)
> at
> org.geotools.data.shapefile.ShapefileSetManager.openDbfReader(ShapefileSetManager.java:132)
> at
> org.geotools.data.shapefile.ShapefileFeatureSource.readAttributes(ShapefileFeatureSource.java:497)
> at
> org.geotools.data.shapefile.ShapefileFeatureSource.buildFeatureType(ShapefileFeatureSource.java:454)
> at
> org.geotools.data.shapefile.ShapefileFeatureStore.buildFeatureType(ShapefileFeatureStore.java:142)
> at
> org.geotools.data.store.ContentFeatureSource.getAbsoluteSchema(ContentFeatureSource.java:339)
> at
> org.geotools.data.store.ContentFeatureSource.getSchema(ContentFeatureSource.java:308)
> at
> org.geotools.data.store.ContentFeatureSource.getSchema(ContentFeatureSource.java:106)
> at
> org.geotools.tutorial.quickstart.Quickstart.main(Quickstart.java:58)
>
> https://www.morling.dev/blog/bytebuffer-and-the-dreaded-nosuchmethoderror/
> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/pavIjKGP2v1NoavyFkb08GBnGSBbT4z2ldytdkAjmkL5nSBAU6kwavK9v1c-kuZeL8IZq7XtMwNsjJh-K2MIHo93XXOx7_K0Mgqahry4eV2_OCBQN7Zy3rkUI0TJ47V4YQiJt6z_MgyvlYzQcLiQDgx_u6ZvJ2pcSxKs62z43X1BpBnh5nab0bcfDzUyhKCtGeze_ai4EI8KtPDDwh96qYMc0ey-jUJeBIe4O2bjJvAdU2jBmKvZtAYBNmmZ8wnTshKYcc-0WNr2NWiJ-ObAj1bDbE0816MfWHfUrhj6-g4K>
>
> Jody says we should build using Java 8 not 11, so we're doing the release
> again.
>
>
>
> On Sun, 18 Jun 2023 at 11:26, Jody Garnett  wrote:
>
>> Artifacts are available for preflight testing:
>> https://build.geoserver.org/view/release/job/geotools-release/lastSuccessfulBuild/artifact/build/release/distribution/28.4/
>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/Npu9wPrT_NFfT1V4FHVjWdmqDNuruxyFF-N4EhVYc8ejUOBKmJGeGT9TljKmhNJKaeohNW_tTLXqo_xp-Hv1Xiv9f71yDqp2k9t5RYnb4T7y-QvlTCvNrgqEW89XYnMl8uz0fnJQrccYZJp4IQClHkxoIerexUTQO-wzVAi1X8xv00San5-CN-S45Hq4eEfFKwUqvjg7eUxwAFZ7sYHBJLDYraOhEJfUOEwLH6Ueo_SkEigkKvEHMai4xBevS6F90X1TSMs7sNvZ3-1wbr1eqiHl96vVQOYaYg2aHjK1qo1mNIxKKnhoMXjvur4uMq-z82rliTUESJzwZ9277QaymtYP-MzljnGSxoc2iP05vrFXGhZfuy0vbKohd0_4NYzazDo>
>>
>> Thanks Peter for volunteer for today's release :)
>> --
>> Jody Garnett
>> ___
>> GeoTools-Devel mailing list
>> GeoTools-Devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/hjB9ehvb875uz57iecgLO5qy66TBekrZ0tPqig97GL_bFET-NBQXpjbiluJ775VivddhIxhFq_gVUq8MIgS12qZIIJ1WI4WnAMXgWK27bx3WTpK1JDc-XM3es_d5P62nr9_n9UquXE6X3dIVOweClKw6wjEqtH6g_3HLsjBaPvHsMM3YSyNCb0HSLOLqg3agba63GFNN4lUCaocnZu68-HRorWFCj2oKHk6O1-i5PbrdgnGdxkt2sDCh5ry3gnahxzdMNmH3dk-hOAIHBQamfOUI>
>>
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] Geotools 28.4 preflight testing

[Jody Garnett]

Artifacts are available for preflight testing:
https://build.geoserver.org/view/release/job/geotools-release/lastSuccessfulBuild/artifact/build/release/distribution/28.4/

Thanks Peter for volunteer for today's release :)
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] [Geowebcache-devel] GS 2.22.4, GT 28.4 and GWC 1.22.3 release cycle will start this Friday

[Jody Garnett]

 The release is intended to start this weekend; but we have a number of
outstanding PRs wanting to review. While I am reviewing most of them I
would appreciate reviews on the following:

   - [GEOS-11026] Only WARN on h2 unload failure if H2 driver available
   <https://github.com/geoserver/geoserver/pull/6939>
   - Oauth2 fix spring sec 5.7.8
   <https://github.com/geoserver/geoserver/pull/6938>
   - [GEOS-10949] URLChecksPage formatting
   <https://github.com/geoserver/geoserver/pull/6937>


There is also a security component to the planned maintenance release and I
wonder if we should release 2.23.x also?
--
Jody Garnett


On Jun 12, 2023 at 12:40:34 PM, Peter Smythe  wrote:

> Good day developers
>
> If you have any fixes that you want included in the upcoming 2.22.4
> GeoServer, 1.22.3 GeoWebCache or 28.4 GeoTools releases, please make sure
> you have backported them and updated the fix version in the ticket before
> Friday afternoon (UTC) which is when Jody and I plan to start the next
> release cycle.
>
> Thank you
>
> Peter
>
>
>
> ___
> Geowebcache-devel mailing list
> geowebcache-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geowebcache-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] [Geoserver-devel] GeoServer/GeoTools PMC Meeting at 18:30 CET / 9:30 PST tomorrow

[Jody Garnett]

 My calendar says today 
--
Jody Garnett


On Jun 6, 2023 at 2:12:03 AM, Rahkonen Jukka <
jukka.rahko...@maanmittauslaitos.fi> wrote:

> Hi,
>
>
>
> To be sure, so on Wednesday tomorrow and not on Tuesday as usually?
>
>
>
> -Jukka-
>
>
>
> *Lähettäjä:* Torben Barsballe 
> *Lähetetty:* tiistai 6. kesäkuuta 2023 4.55
> *Vastaanottaja:* Geoserver-devel ;
> GeoTools Developers 
> *Aihe:* [Geoserver-devel] GeoServer/GeoTools PMC Meeting at 18:30 CET /
> 9:30 PST tomorrow
>
>
>
> Reminder that the next PMC meeting is scheduled for tomorrow, June 7, at
> 18:30
> <https://www.timeanddate.com/worldclock/fixedtime.html?year=2023=6=7=18=30=0=GeoTools%20/%20GeoServer%20Meeting=1=1=215>
>  CET.
>
>
>
> Cheers,
>
> Torben
> ___
> Geoserver-devel mailing list
> geoserver-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] [Geoserver-devel] GeoServer/GeoTools PMC Meeting at 18:30 CET / 9:30 PST tomorrow

[Jody Garnett]

I will not be attending this week

Thanks to Siam for getting the release out, and for those responding to
some of my Jira tickets.

See you next month.

Jody

On Mon, May 22, 2023 at 11:51 AM Torben Barsballe 
wrote:

> Reminder that the next PMC meeting is scheduled for tomorrow, May 23, at
> 18:30
> <https://www.timeanddate.com/worldclock/fixedtime.html?year=2023=5=23=18=30=0=GeoTools%20/%20GeoServer%20Meeting=1=1=215>
>  CET.
>
>
> Cheers,
>
> Torben
> ___
> Geoserver-devel mailing list
> geoserver-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
-- 
--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] osgeo dns troubled, and 29-SNAPSHOT building

[Jody Garnett]

Working with Regina on osgeo general channel we have build.geoserver.org in
communication with repo.osgeo.org again!

The build jobs described above are now working as intended (needed to use
-U for the deploy step although I am not clear why).
--
Jody Garnett


On Thu, May 18, 2023 at 3:18 PM Jody Garnett  wrote:

> A couple notes from build server maintenance stuff:
>
> 1) osgeo.org is having some kind of DNS trouble (DoS? The provider is
> working on it...)
>
> If anyone hears of osgeo.org being fixed please respond to this thread :)
>
> 2) The GeoTools 29-SNAPSHOT builds were not being deployed to
> repo.osgeo.org so a couple of jobs have been updated:
>
> - geotools-29.x-java11 - disabled
> - geotools-29.x
> <https://build.geoserver.org/view/geotools/job/geotools-29.x/> - new,
> copied from geotools-28.x
>
> Updated the downstream geowebcache-1.23.x
> <https://build.geoserver.org/view/geotools/job/geowebcache-1.23.x/> and
> geoserver-2.23.x
> <https://build.geoserver.org/view/geotools/job/geoserver-2.23.x/> jobs:
> - no longer include an independent maven repository (previously
> inconsistent, with some jobs having -Dmaven.repo.local=m2)
> - no longer have a shared workspace, some of the java11 jobs had a shared
> workspace and m2 repository to avoid mixing java8 and java11 jars)
> - no longer in a the multi-module throttle group "geoserver", rely on
> being restricted from upstream / downstream jobs to avoid overloading server
> - the build jobs all include -U to force download of SNAPSHOTs (which is
> what we are testing)
> - build steps include -T1C threading (previously -T2)
> - the deploy steps do not include -U, and -T2C threading (previously
> inconsistent -T2 and T4)
>
>
> --
> Jody Garnett
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] osgeo dns troubled, and 29-SNAPSHOT building

[Jody Garnett]

Scaled back to 0.75C build and 1C deploy :)
--
Jody Garnett


On Fri, May 19, 2023 at 12:36 AM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> On Fri, May 19, 2023 at 12:20 AM Jody Garnett 
> wrote:
>
>> - build steps include -T1C threading (previously -T2)
>> - the deploy steps do not include -U, and -T2C threading (previously
>> inconsistent -T2 and T4)
>>
>
> That is very aggressive... for personal experience, the shortest build
> time is achieved at 3/4 of the physical cores (so with 8 physical cores, I
> run -T6).
>
> Cheers
> Andrea
>
> ==
>
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Add mapping for new type

[Jody Garnett]

Wassim:

You may also consider ContentDataStore tutorial
<https://docs.geotools.org/stable/userguide/tutorial/datastore/index.html>
which introduces the DataStore API - and importantly the helper classes
available to implementers.

The JDBCDataStore builds on this work (isolating most database specific
decisions into a dialect class as you have seen).
--
Jody Garnett


On Thu, May 18, 2023 at 4:32 AM WaZy  wrote:

> If I follow the "tutorial" written in the text file jdbc-notes.txt will it
> help me to achieve what I want ?
>
> I have also already started to take a look at the code of the PostGIS JDBC
> plugin, but I find it a bit hard to understand because there are some
> functions where there are details that are not explained. Is somewhere a
> full documentation about the dialect and what the functions are supposed to
> do? Or even a video ?
>
> Wassim
>
> Le mar. 16 mai 2023 à 14:06, Ian Turton  a écrit :
>
>> You'll need to take a look at the PostGIS JDBC plugin to get you started,
>> you should be able to extend most of it and just need to work on the
>> dialect to add in the changes you need.
>>
>> Ian
>>
>> On Tue, 16 May 2023 at 12:05, WaZy  wrote:
>>
>>> I forgot that there exists a MobilityDB-JDBC driver, can  I use it to
>>> implement those mapping in a simpler way ?
>>>
>>> Le mar. 16 mai 2023 à 11:23, WaZy  a écrit :
>>>
>>>> I actually have a type implemented in MobilityDB known as tgeompoint,
>>>> it is a type used to represent points moving in time( trips). For example
>>>> this is what  a  tgeompoint looks like :
>>>>
>>>> tgeompoint '[Point(0 0)@2000-01-01, Point(100 100)@2000-01-02
>>>>
>>>> For your 2 first  questions I didn't understand what you were asking so 
>>>> maybe know that you see what it looks like we have a better idea than me.
>>>>
>>>> For your last question I have already taken a look at PostGISDialect but I 
>>>> don't know what I should do to have the same thing for mobilityDB and how 
>>>> would I test it?
>>>>
>>>> Do I have to extend this class since mobility+DB is built on top of 
>>>> PostGIS? Or is there a better way  to  do  that?
>>>>
>>>> Wassim
>>>>
>>>>
>>>>
>>>> Le lun. 15 mai 2023 à 22:41, Jody Garnett  a
>>>> écrit :
>>>>
>>>>> There are a number of ways to model locations changing in time. Do you
>>>>> have a series of time stamped records each Ruth’s location? If so the
>>>>> existing temporal support should be fine?
>>>>>
>>>>> Or do you have a spatial temporal reference burst as some kind of XYZM
>>>>> geometry with M being some kind of timestamp? If so you probably have
>>>>> functions to work with your type?
>>>>>
>>>>> Have a look at PostGISDialect for type mapping; you can make something
>>>>> similar for MobilityDB?
>>>>>
>>>>> Jody
>>>>>
>>>>> On Mon, May 15, 2023 at 6:59 AM WaZy  wrote:
>>>>>
>>>>>> Hello I'm new here and I would like to know how I could add the
>>>>>> mapping for a new type in  GeoTool. I'm actually using MobilityDB  which 
>>>>>> is
>>>>>> an extension to the PostgreSQL database system and its spatial extension
>>>>>> PostGIS. It allows temporal and spatio-temporal objects to be stored in 
>>>>>> the
>>>>>> database, that is, objects whose attribute values and/or location evolves
>>>>>> in time.I want to  visualize data with Geoserver but it do not allow me 
>>>>>> to
>>>>>> read the data because those types are unknown to Geotool if I understood
>>>>>> correctly.
>>>>>>
>>>>>> The message I get in  the logs is : No mapping found for
>>>>>> "myAttribute" set to  read only.
>>>>>>
>>>>>>
>>>>>>  This is why I want to know how I could do  that and if it is a hard
>>>>>> task.
>>>>>>
>>>>>> Best regards.
>>>>>> ___
>>>>>> GeoTools-Devel mailing list
>>>>>> GeoTools-Devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>>>>
>>>>> --
>>>>> --
>>>>> Jody Garnett
>>>>>
>>>> ___
>>> GeoTools-Devel mailing list
>>> GeoTools-Devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>
>>
>>
>> --
>> Ian Turton
>>
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] osgeo dns troubled, and 29-SNAPSHOT building

[Jody Garnett]

A couple notes from build server maintenance stuff:

1) osgeo.org is having some kind of DNS trouble (DoS? The provider is
working on it...)

If anyone hears of osgeo.org being fixed please respond to this thread :)

2) The GeoTools 29-SNAPSHOT builds were not being deployed to repo.osgeo.org
so a couple of jobs have been updated:

- geotools-29.x-java11 - disabled
- geotools-29.x
<https://build.geoserver.org/view/geotools/job/geotools-29.x/> - new,
copied from geotools-28.x

Updated the downstream geowebcache-1.23.x
<https://build.geoserver.org/view/geotools/job/geowebcache-1.23.x/> and
geoserver-2.23.x
<https://build.geoserver.org/view/geotools/job/geoserver-2.23.x/> jobs:
- no longer include an independent maven repository (previously
inconsistent, with some jobs having -Dmaven.repo.local=m2)
- no longer have a shared workspace, some of the java11 jobs had a shared
workspace and m2 repository to avoid mixing java8 and java11 jars)
- no longer in a the multi-module throttle group "geoserver", rely on being
restricted from upstream / downstream jobs to avoid overloading server
- the build jobs all include -U to force download of SNAPSHOTs (which is
what we are testing)
- build steps include -T1C threading (previously -T2)
- the deploy steps do not include -U, and -T2C threading (previously
inconsistent -T2 and T4)


--
Jody Garnett
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel