geotools-devel — A list for GeoTools development issues

[Geotools-devel] Call for Architecture: Open-Source Redistricting, The NGA Standard, and Ending Spatial Dicing Games

[Christopher H. <han...@gm...>]

*To the OSGeo Consortium, ASPRS Reps, and University Geospatial/Human-Socio
Professors:*

My name is Chris, Project Architect at NexaVision. I am reaching out to the
geospatial community with a specific architectural challenge regarding the
ongoing spatial "dicing games" being played with U.S. congressional
redistricting (specifically the current watering down of votes in Florida).

*The Question:* How would you mathematically and spatially solve this
problem using an unbiased, open-source algorithm?

*The Objective:* We need to build a standardized, un-gerrymanderable
redistricting model. We want to outline a project that can be funded by a
congressional bill and hosted permanently by the public-sector side of the
NGA (National Geospatial-Intelligence Agency).

*The Technical & Socio-Economic Parameters:*

   1.

   *County Boundary Integrity:* The algorithm must respect county lines as
   hard boundaries/masking layers as much as possible, recognizing that local
   datums and localized governance are highly efficient.
   2.

   *Protecting Vulnerable Clusters:* The model must explicitly account for
   socio-economic variables. It must identify and protect poor/working-class
   citizen clusters to ensure they are *not* split on the outskirts just to
   dilute their representation.
   3.

   *Historical Vector Titration:* We need layers that weight historical
   vectors, starting with strong historical representation and
   titrating/smoothing the transition over a yearly schedule to prevent
   sudden, chaotic representative shifts.
   4.

   *The Tech Stack:* The final output must utilize GeoServer, hosting web
   tiles, polys, vectors, and rasters.
   5.

   *Governance:* NGA hosts the static shapefiles and web layers, but
   administrative QA/QC protocols and worker accounts are managed by a
   consortium of OSGeo, ASPRS, and university reps.

*The End Goal:* We need to produce clean, undeniable web layers and static
shapefiles that can be presented directly to Congress as bill materials and
appendices. We want the whole nation singing in spatial harmony, utilizing
a single, undeniable dataset.

If you are a maker or a doer in the GIS, remote sensing, or spatial
analytics space, I would like to hear your thoughts on structuring the
weights, metrics, and data pipelines for this initiative.

Best regards,

*Chris* Project Architect | The NexaVision https://www.nexavision.tech

*Geo people should be thinking about these maps
--> https://youtu.be/G18uqNY8NWM?si=b9-ChO6z1wvOiHiu
<https://youtu.be/G18uqNY8NWM?si=b9-ChO6z1wvOiHiu>*

[Geotools-devel] Request for Architecture: Lightweight Vector Tile Server for Open-Source Parcel OSINT ("The Richest Maps")

[Christopher H. <han...@gm...>]

*To the OSGeo / Geo-Dev Community:*

My name is Chris. I am a project architect operating out of NexaVision
(nexavision.tech), and I am currently seeking developers and geospatial
engineers interested in collaborating on a lightweight, high-impact OSINT
mapping project.

*The Objective: "The Richest Maps"* We are conceptualizing an open-source,
web-hosted mapping space designed to visualize massive wealth disparity on
a localized level. The goal is to ingest open-source county parcel data,
cross-reference it with trusted public databases (e.g., Forbes lists, SEC
filings, public property records), and map the residential footprints,
assets, and holding companies of the 0.1% (billionaire class) on a
county-by-county basis.

We are not building a bloated Google Maps competitor. We need a fast,
surgical, vector-based tile environment.

*The Technical Requirements:*

   -

   *Architecture:* A lightweight vector tile server (e.g., GeoServer,
   PostGIS, Mapbox GL JS / MapLibre) capable of handling spatial queries on
   the fly.
   -

   *Data Ingestion:* Automated or semi-automated pipelines to harvest and
   normalize disparate U.S. county parcel data into a unified schema (WGS84 /
   EGM 2020 projection preferred).
   -

   *Visualization:* Clean heatmaps and 3D building footprints (where
   LiDAR/vector data is available) representing the highest-valued residential
   parcels in any given query zone.
   -

   *User Interaction:* A user-queryable interface ("Who is the richest
   resident in my county?") with trusted-source update capabilities (similar
   to Waze's community-driven layering).
   -

   *Layering:* Specific attention to proximity queries—mapping the nearest
   public spaces and navigable waterways to these heavily fortified assets.

*The Ethos:* Transparency is a two-way street. If the billionaire class
continues to leverage data brokers against the public, the public has a
right to utilize open civic data to map the true distribution of assets in
their own backyards.

If you are skilled in Python, R, DB management, or WebGIS, and you believe
that open data is a tool for civic accountability, I would like to connect.
This is a FOSS (Free and Open-Source Software) initiative aimed at building
a better, more transparent world architecture.

Please reply to this thread or reach out directly via
https://www.nexavision.tech/skills.html if you are interested in
structuring the seed points for this repository.

Best regards,

*Chris* Project Architect | The NexaVision https://www.nexavision.tech

[Geotools-devel] Next GeoTools 34.x (34.4) release is missing in Jira

[Mark P. <mc....@gm...>]

Hi all,
Could someone add the 34.4 version/release in Jira please, it appears to 
be missing, so I cannot set it as "fix version".

TIA, Mark

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

[Torben B. <tor...@gm...>]

Reminder that the next PMC meeting is scheduled for tomorrow, April 21, at
18:30
<https://www.timeanddate.com/worldclock/fixedtime.html?year=2026&month=4&day=21&hour=18&min=30&sec=0&msg=GeoTools%20/%20GeoServer%20Meeting&ah=1&sort=1&p1=215>
 CET.

Cheers,
Torben

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

[Torben B. <tor...@gm...>]

 Reminder that the next PMC meeting is scheduled for tomorrow, April 7, at
18:30
<https://www.timeanddate.com/worldclock/fixedtime.html?year=2026&month=4&day=7&hour=18&min=30&sec=0&msg=GeoTools%20/%20GeoServer%20Meeting&ah=1&sort=1&p1=215>
 CET.

We've synced back up on DST, so it's back to the usual time for everyone.

Cheers,
Torben

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

[Torben B. <tor...@gm...>]

We did not make quorum today, and as such wrapped up early.
Talk to everyone in two weeks.

Cheers,
Torben

On Mon, Mar 23, 2026 at 12:11 PM Torben Barsballe <tor...@gm...>
wrote:

> Reminder that the next PMC meeting is scheduled for tomorrow, March 24, at
> 18:30
> <https://www.timeanddate.com/worldclock/fixedtime.html?year=2026&month=3&day=24&hour=18&min=30&sec=0&msg=GeoTools%20/%20GeoServer%20Meeting&ah=1&sort=1&p1=215>
>  CET.
>
> We're still off-sync on DST this week, so this is 1 hour later than usual
> for those of us in the Pacific time zone.
>
> Cheers,
> Torben
>
>

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

[Torben B. <tor...@gm...>]

 Reminder that the next PMC meeting is scheduled for tomorrow, March 24, at
18:30
<https://www.timeanddate.com/worldclock/fixedtime.html?year=2026&month=3&day=24&hour=18&min=30&sec=0&msg=GeoTools%20/%20GeoServer%20Meeting&ah=1&sort=1&p1=215>
 CET.

We're still off-sync on DST this week, so this is 1 hour later than usual
for those of us in the Pacific time zone.

Cheers,
Torben

[Geotools-devel] Dependabot automatic update PRs incoming

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

Hi all,
I've been playing with dependabot as a tool to get automatic update PRs
when a project releases. First I've experimented on a separate codebase,
then used it on imageio-ext with good success, and finally on
GeoWebCache... why those two? Because they are small.

At first one receives quite a bit of PRs (I set the limit to at most 10 per
day) and most of them are easily actionable
<https://github.com/GeoWebCache/geowebcache/pulls?q=is%3Apr+is%3Aclosed>.
Others are larger upgrades that break API or
<https://github.com/GeoWebCache/geowebcache/pulls/dependabot%5Bbot%5D>come
with deprecation
<https://github.com/GeoWebCache/geowebcache/pulls/dependabot%5Bbot%5D>, and
will need some manual work. A small amount get confused by the too many
concurrent changes to pom and configuration and will need to be recreated
manually.

Here is the configuration file that I've been using
<https://github.com/GeoWebCache/geowebcache/blob/main/.github/dependabot.yml>
.

Now... I plan to land this on GeoTools as well. Since it's the central
management point for most dependencies, I expect to see quite a bit of
traffic and some further adjustments to the configuration. This
canon the done in the safety of a PR, the config needs to be committed for
dependabot to take action, so expect a bit of traffic.

I plan to do that in the next few days, if there are concerns please speak
up.

Regards,

Andrea Aime


==


GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax:     +39 0584 1660272

mob:   +39  339 8844549

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail

Re: [Geotools-devel] SF about to remove prior releases

[Torben B. <tor...@gm...>]

Created https://trac.osgeo.org/osgeo/ticket/3543

Jody - I've cc'd you on that ticket for visibility.

Cheers,
Torben

On Thu, Mar 12, 2026 at 11:16 AM Torben Barsballe <tor...@gm...>
wrote:

> Alright, everything is now saved at least. I grabbed GWC as well just for
> completeness.
>
>    - GeoTools - 64 GB
>    - GeoWebCache - 9.4 GB
>    - GeoServer - 125 GB
>
> So we're going to need around 200 GB of space wherever we end up putting
> these.
> I'll look into opening a trac ticket tomorrow.
>
> Cheers,
> Torben
>
> On Tue, Mar 10, 2026 at 6:37 PM Torben Barsballe <
> tor...@gm...> wrote:
>
>> rsync to OSGeo would definitely be easier - sounds like a plan to me.
>>
>> GeoTools download is done -  came in at about 67 G - though I still need
>> to do a bit of post processing, as the fetch from SF requires a query param
>> that winds up getting included in the filename, and the rename command
>> included in the script to fix this didn't work on MacOS.
>> GeoServer download is in progress - looks like it's going to be quite a
>> bit bigger, and take significantly longer.
>>
>> Cheers,
>> Torben
>>
>> On Tue, Mar 10, 2026 at 6:03 PM Jody Garnett <jod...@gm...>
>> wrote:
>>
>>> How about rsync to OSGeo? We can open en a trac ticket to ask
>>>
>>> - -
>>> Jody Garnett
>>>
>>>
>>> On Tue, Mar 10, 2026 at 11:38 AM Torben Barsballe <
>>> tor...@gm...> wrote:
>>>
>>>> Following on from today's PSC meeting discussion, I can save the data
>>>> at least.
>>>> Uploading to GitHub looks like it'll be a difficult manual task - with
>>>> no upload API, this may not be automatable.
>>>>
>>>> Cheers,
>>>> Torben
>>>>
>>>> On Sun, Mar 8, 2026 at 11:25 PM Jody Garnett <jod...@gm...>
>>>> wrote:
>>>>
>>>>> SourceForge sent a request if February to remove large files with zero
>>>>> recent downloads.
>>>>>
>>>>> This project is using a large amount of storage.
>>>>>
>>>>> We need your help removing a lot of your old releases.
>>>>>> Please remove as much as you can of your old releases and unused
>>>>>> files within 14 days.
>>>>>>
>>>>>> You can use this tool to help you identify the files that aren't
>>>>>> getting many downloads and take up a lot of space.
>>>>>> https://sourceforge.net/p/geotools/admin/files/large_files
>>>>>>
>>>>>> We are letting you know so you can choose which files to remove.
>>>>>> Please be aware that if we don't see any difference after 14 days, we
>>>>>> will have to remove all the files and folders with 0 or a few monthly
>>>>>> downloads ourselves.
>>>>>>
>>>>>
>>>>> We actually depend on this historical record as our commit history is
>>>>> not 100% complete (due to svn / git etc...) so sent the following reply:
>>>>>
>>>>> This is a long term project used for a lot of scientific and mapping
>>>>>> applications.
>>>>>>
>>>>>> Since it is such an established project it is our intension to keep
>>>>>> the historical artifacts online. Because we use the maven build system we
>>>>>> cannot always be sure that keeping just the source code is sufficient to
>>>>>> rebuild prior configurations (as their dependencies may not remain
>>>>>> available).
>>>>>>
>>>>>> I look forward to your response.
>>>>>>
>>>>>
>>>>> They have now sent a second warning:
>>>>>
>>>>> Hello,
>>>>>>
>>>>>> This is a reminder that you must clean up files on your project.
>>>>>>
>>>>>> We are giving you an additional 14 days and then will begin removing
>>>>>> files ourselves.
>>>>>> Please remove as much as you can of your old releases and unused
>>>>>> files within 14 days.
>>>>>>
>>>>>> We need to see a substantial amount removed.
>>>>>>
>>>>>
>>>>> With this in mind what do we wish to do?
>>>>>
>>>>>
>>>>>    - Anyone wish to write a script to create tags in GitHub, and
>>>>>    transfer the assets over?
>>>>>
>>>>>
>>>>> - -
>>>>> Jody Garnett
>>>>>
>>>> _______________________________________________
>>>>> GeoTools-Devel mailing list
>>>>> Geo...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>>>
>>>>

Re: [Geotools-devel] SF about to remove prior releases

[Torben B. <tor...@gm...>]

Alright, everything is now saved at least. I grabbed GWC as well just for
completeness.

   - GeoTools - 64 GB
   - GeoWebCache - 9.4 GB
   - GeoServer - 125 GB

So we're going to need around 200 GB of space wherever we end up putting
these.
I'll look into opening a trac ticket tomorrow.

Cheers,
Torben

On Tue, Mar 10, 2026 at 6:37 PM Torben Barsballe <tor...@gm...>
wrote:

> rsync to OSGeo would definitely be easier - sounds like a plan to me.
>
> GeoTools download is done -  came in at about 67 G - though I still need
> to do a bit of post processing, as the fetch from SF requires a query param
> that winds up getting included in the filename, and the rename command
> included in the script to fix this didn't work on MacOS.
> GeoServer download is in progress - looks like it's going to be quite a
> bit bigger, and take significantly longer.
>
> Cheers,
> Torben
>
> On Tue, Mar 10, 2026 at 6:03 PM Jody Garnett <jod...@gm...>
> wrote:
>
>> How about rsync to OSGeo? We can open en a trac ticket to ask
>>
>> - -
>> Jody Garnett
>>
>>
>> On Tue, Mar 10, 2026 at 11:38 AM Torben Barsballe <
>> tor...@gm...> wrote:
>>
>>> Following on from today's PSC meeting discussion, I can save the data at
>>> least.
>>> Uploading to GitHub looks like it'll be a difficult manual task - with
>>> no upload API, this may not be automatable.
>>>
>>> Cheers,
>>> Torben
>>>
>>> On Sun, Mar 8, 2026 at 11:25 PM Jody Garnett <jod...@gm...>
>>> wrote:
>>>
>>>> SourceForge sent a request if February to remove large files with zero
>>>> recent downloads.
>>>>
>>>> This project is using a large amount of storage.
>>>>
>>>> We need your help removing a lot of your old releases.
>>>>> Please remove as much as you can of your old releases and unused files
>>>>> within 14 days.
>>>>>
>>>>> You can use this tool to help you identify the files that aren't
>>>>> getting many downloads and take up a lot of space.
>>>>> https://sourceforge.net/p/geotools/admin/files/large_files
>>>>>
>>>>> We are letting you know so you can choose which files to remove.
>>>>> Please be aware that if we don't see any difference after 14 days, we
>>>>> will have to remove all the files and folders with 0 or a few monthly
>>>>> downloads ourselves.
>>>>>
>>>>
>>>> We actually depend on this historical record as our commit history is
>>>> not 100% complete (due to svn / git etc...) so sent the following reply:
>>>>
>>>> This is a long term project used for a lot of scientific and mapping
>>>>> applications.
>>>>>
>>>>> Since it is such an established project it is our intension to keep
>>>>> the historical artifacts online. Because we use the maven build system we
>>>>> cannot always be sure that keeping just the source code is sufficient to
>>>>> rebuild prior configurations (as their dependencies may not remain
>>>>> available).
>>>>>
>>>>> I look forward to your response.
>>>>>
>>>>
>>>> They have now sent a second warning:
>>>>
>>>> Hello,
>>>>>
>>>>> This is a reminder that you must clean up files on your project.
>>>>>
>>>>> We are giving you an additional 14 days and then will begin removing
>>>>> files ourselves.
>>>>> Please remove as much as you can of your old releases and unused files
>>>>> within 14 days.
>>>>>
>>>>> We need to see a substantial amount removed.
>>>>>
>>>>
>>>> With this in mind what do we wish to do?
>>>>
>>>>
>>>>    - Anyone wish to write a script to create tags in GitHub, and
>>>>    transfer the assets over?
>>>>
>>>>
>>>> - -
>>>> Jody Garnett
>>>>
>>> _______________________________________________
>>>> GeoTools-Devel mailing list
>>>> Geo...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>>
>>>

Re: [Geotools-devel] SF about to remove prior releases

[Torben B. <tor...@gm...>]

rsync to OSGeo would definitely be easier - sounds like a plan to me.

GeoTools download is done -  came in at about 67 G - though I still need to
do a bit of post processing, as the fetch from SF requires a query param
that winds up getting included in the filename, and the rename command
included in the script to fix this didn't work on MacOS.
GeoServer download is in progress - looks like it's going to be quite a bit
bigger, and take significantly longer.

Cheers,
Torben

On Tue, Mar 10, 2026 at 6:03 PM Jody Garnett <jod...@gm...> wrote:

> How about rsync to OSGeo? We can open en a trac ticket to ask
>
> - -
> Jody Garnett
>
>
> On Tue, Mar 10, 2026 at 11:38 AM Torben Barsballe <
> tor...@gm...> wrote:
>
>> Following on from today's PSC meeting discussion, I can save the data at
>> least.
>> Uploading to GitHub looks like it'll be a difficult manual task - with no
>> upload API, this may not be automatable.
>>
>> Cheers,
>> Torben
>>
>> On Sun, Mar 8, 2026 at 11:25 PM Jody Garnett <jod...@gm...>
>> wrote:
>>
>>> SourceForge sent a request if February to remove large files with zero
>>> recent downloads.
>>>
>>> This project is using a large amount of storage.
>>>
>>> We need your help removing a lot of your old releases.
>>>> Please remove as much as you can of your old releases and unused files
>>>> within 14 days.
>>>>
>>>> You can use this tool to help you identify the files that aren't
>>>> getting many downloads and take up a lot of space.
>>>> https://sourceforge.net/p/geotools/admin/files/large_files
>>>>
>>>> We are letting you know so you can choose which files to remove.
>>>> Please be aware that if we don't see any difference after 14 days, we
>>>> will have to remove all the files and folders with 0 or a few monthly
>>>> downloads ourselves.
>>>>
>>>
>>> We actually depend on this historical record as our commit history is
>>> not 100% complete (due to svn / git etc...) so sent the following reply:
>>>
>>> This is a long term project used for a lot of scientific and mapping
>>>> applications.
>>>>
>>>> Since it is such an established project it is our intension to keep the
>>>> historical artifacts online. Because we use the maven build system we
>>>> cannot always be sure that keeping just the source code is sufficient to
>>>> rebuild prior configurations (as their dependencies may not remain
>>>> available).
>>>>
>>>> I look forward to your response.
>>>>
>>>
>>> They have now sent a second warning:
>>>
>>> Hello,
>>>>
>>>> This is a reminder that you must clean up files on your project.
>>>>
>>>> We are giving you an additional 14 days and then will begin removing
>>>> files ourselves.
>>>> Please remove as much as you can of your old releases and unused files
>>>> within 14 days.
>>>>
>>>> We need to see a substantial amount removed.
>>>>
>>>
>>> With this in mind what do we wish to do?
>>>
>>>
>>>    - Anyone wish to write a script to create tags in GitHub, and
>>>    transfer the assets over?
>>>
>>>
>>> - -
>>> Jody Garnett
>>>
>> _______________________________________________
>>> GeoTools-Devel mailing list
>>> Geo...@li...
>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>
>>

Re: [Geotools-devel] SF about to remove prior releases

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

How about rsync to OSGeo? We can open en a trac ticket to ask

- -
Jody Garnett


On Tue, Mar 10, 2026 at 11:38 AM Torben Barsballe <tor...@gm...>
wrote:

> Following on from today's PSC meeting discussion, I can save the data at
> least.
> Uploading to GitHub looks like it'll be a difficult manual task - with no
> upload API, this may not be automatable.
>
> Cheers,
> Torben
>
> On Sun, Mar 8, 2026 at 11:25 PM Jody Garnett <jod...@gm...>
> wrote:
>
>> SourceForge sent a request if February to remove large files with zero
>> recent downloads.
>>
>> This project is using a large amount of storage.
>>
>> We need your help removing a lot of your old releases.
>>> Please remove as much as you can of your old releases and unused files
>>> within 14 days.
>>>
>>> You can use this tool to help you identify the files that aren't getting
>>> many downloads and take up a lot of space.
>>> https://sourceforge.net/p/geotools/admin/files/large_files
>>>
>>> We are letting you know so you can choose which files to remove.
>>> Please be aware that if we don't see any difference after 14 days, we
>>> will have to remove all the files and folders with 0 or a few monthly
>>> downloads ourselves.
>>>
>>
>> We actually depend on this historical record as our commit history is not
>> 100% complete (due to svn / git etc...) so sent the following reply:
>>
>> This is a long term project used for a lot of scientific and mapping
>>> applications.
>>>
>>> Since it is such an established project it is our intension to keep the
>>> historical artifacts online. Because we use the maven build system we
>>> cannot always be sure that keeping just the source code is sufficient to
>>> rebuild prior configurations (as their dependencies may not remain
>>> available).
>>>
>>> I look forward to your response.
>>>
>>
>> They have now sent a second warning:
>>
>> Hello,
>>>
>>> This is a reminder that you must clean up files on your project.
>>>
>>> We are giving you an additional 14 days and then will begin removing
>>> files ourselves.
>>> Please remove as much as you can of your old releases and unused files
>>> within 14 days.
>>>
>>> We need to see a substantial amount removed.
>>>
>>
>> With this in mind what do we wish to do?
>>
>>
>>    - Anyone wish to write a script to create tags in GitHub, and
>>    transfer the assets over?
>>
>>
>> - -
>> Jody Garnett
>>
> _______________________________________________
>> GeoTools-Devel mailing list
>> Geo...@li...
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
>

Re: [Geotools-devel] SF about to remove prior releases

[Torben B. <tor...@gm...>]

Following on from today's PSC meeting discussion, I can save the data at
least.
Uploading to GitHub looks like it'll be a difficult manual task - with no
upload API, this may not be automatable.

Cheers,
Torben

On Sun, Mar 8, 2026 at 11:25 PM Jody Garnett <jod...@gm...> wrote:

> SourceForge sent a request if February to remove large files with zero
> recent downloads.
>
> This project is using a large amount of storage.
>
> We need your help removing a lot of your old releases.
>> Please remove as much as you can of your old releases and unused files
>> within 14 days.
>>
>> You can use this tool to help you identify the files that aren't getting
>> many downloads and take up a lot of space.
>> https://sourceforge.net/p/geotools/admin/files/large_files
>>
>> We are letting you know so you can choose which files to remove.
>> Please be aware that if we don't see any difference after 14 days, we
>> will have to remove all the files and folders with 0 or a few monthly
>> downloads ourselves.
>>
>
> We actually depend on this historical record as our commit history is not
> 100% complete (due to svn / git etc...) so sent the following reply:
>
> This is a long term project used for a lot of scientific and mapping
>> applications.
>>
>> Since it is such an established project it is our intension to keep the
>> historical artifacts online. Because we use the maven build system we
>> cannot always be sure that keeping just the source code is sufficient to
>> rebuild prior configurations (as their dependencies may not remain
>> available).
>>
>> I look forward to your response.
>>
>
> They have now sent a second warning:
>
> Hello,
>>
>> This is a reminder that you must clean up files on your project.
>>
>> We are giving you an additional 14 days and then will begin removing
>> files ourselves.
>> Please remove as much as you can of your old releases and unused files
>> within 14 days.
>>
>> We need to see a substantial amount removed.
>>
>
> With this in mind what do we wish to do?
>
>
>    - Anyone wish to write a script to create tags in GitHub, and transfer
>    the assets over?
>
>
> - -
> Jody Garnett
> _______________________________________________
> GeoTools-Devel mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>

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

[Torben B. <tor...@gm...>]

Reminder that the next PMC meeting is scheduled for tomorrow, March 10, at
18:30
<https://www.timeanddate.com/worldclock/fixedtime.html?year=2026&month=3&day=10&hour=18&min=30&sec=0&msg=GeoTools%20/%20GeoServer%20Meeting&ah=1&sort=1&p1=215>
 CET.

Note that we're off-sync on DST this week, so this is 1 hour later than
usual for those of us in the Pacific time zone.

Cheers,
Torben

[Geotools-devel] SF about to remove prior releases

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

SourceForge sent a request if February to remove large files with zero
recent downloads.

This project is using a large amount of storage.

We need your help removing a lot of your old releases.
> Please remove as much as you can of your old releases and unused files
> within 14 days.
>
> You can use this tool to help you identify the files that aren't getting
> many downloads and take up a lot of space.
> https://sourceforge.net/p/geotools/admin/files/large_files
>
> We are letting you know so you can choose which files to remove.
> Please be aware that if we don't see any difference after 14 days, we will
> have to remove all the files and folders with 0 or a few monthly downloads
> ourselves.
>

We actually depend on this historical record as our commit history is not
100% complete (due to svn / git etc...) so sent the following reply:

This is a long term project used for a lot of scientific and mapping
> applications.
>
> Since it is such an established project it is our intension to keep the
> historical artifacts online. Because we use the maven build system we
> cannot always be sure that keeping just the source code is sufficient to
> rebuild prior configurations (as their dependencies may not remain
> available).
>
> I look forward to your response.
>

They have now sent a second warning:

Hello,
>
> This is a reminder that you must clean up files on your project.
>
> We are giving you an additional 14 days and then will begin removing files
> ourselves.
> Please remove as much as you can of your old releases and unused files
> within 14 days.
>
> We need to see a substantial amount removed.
>

With this in mind what do we wish to do?


   - Anyone wish to write a script to create tags in GitHub, and transfer
   the assets over?


- -
Jody Garnett

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

[Torben B. <tor...@gm...>]

 Reminder that the next PMC meeting is scheduled for tomorrow, February 24,
at 18:30
<https://www.timeanddate.com/worldclock/fixedtime.html?year=2026&month=2&day=24&hour=18&min=30&sec=0&msg=GeoTools%20/%20GeoServer%20Meeting&ah=1&sort=1&p1=215>
 CET.

I've got a conflicting meeting and will be unable to attend.

Cheers,
Torben

Re: [Geotools-devel] GeoTools 33.5, GWC 1.27.5, GeoServer 2.27.5 maintenance release

[Peter S. <gs...@sm...>]

Hi all

GeoTools 33.5 has been released:
https://geotoolsnews.blogspot.com/2026/02/geotools-335-released.html
So too has GeoWebCache 1.27.5
https://github.com/GeoWebCache/geowebcache/releases/tag/1.27.5
And GeoServer 2.27.5
https://geoserver.org/announcements/2026/02/18/geoserver-2-27-5-released.html
<< includes special announcement

Please visit the above links for more details.

Regards

Peter

GeoServer PSC
AWS Solutions Architect
https://github.com/petersmythe


On Wed, 18 Feb 2026 at 09:39, Peter Smythe <gs...@sm...> wrote:

> Hi devs
>
> I am starting with the scheduled maintenance release of GeoTools 33.5, GWC
> 1.27.5 and ultimately GeoServer 2.27.5.  Follow along on
> https://discourse.osgeo.org/t/geoserver-2-27-5-release/152395
>
> Peter
>
> Peter
>
> GeoServer PSC
> AWS Solutions Architect
> https://github.com/petersmythe
>

[Geotools-devel] GeoTools 33.5, GWC 1.27.5, GeoServer 2.27.5 maintenance release

[Peter S. <gs...@sm...>]

Hi devs

I am starting with the scheduled maintenance release of GeoTools 33.5, GWC
1.27.5 and ultimately GeoServer 2.27.5.  Follow along on
https://discourse.osgeo.org/t/geoserver-2-27-5-release/152395

Peter

Peter

GeoServer PSC
AWS Solutions Architect
https://github.com/petersmythe

Re: [Geotools-devel] SF Storage warning

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

 For now I have responded with:

This is a long term project used for a lot of scientific and mapping
> applications.
>
Since it is such an established project it is our intension to keep the
> historical artifacts online. Because we use the maven build system we
> cannot always be sure that keeping just the source code is sufficient to
> rebuild prior configurations (as their dependencies may not remain
> available).
>
I look forward to your response.
>

As for clean up:

   - I could see keeping the most recent release of each branch
   - source + bin downloads (trusting that javadocs and docs can be
   recreated)


Or alternatively we could transfer to github, or OSGeo, but this would take
some effort with a script.

I personally do not have time for this, it looks like PSC maintenance
activity.
- -
Jody Garnett


On Feb 13, 2026 at 9:15:44 AM, Jody Garnett <jod...@gm...> wrote:

> Sourceforge has sent a message that we are using a lot of storage and asks
> us to clean up old releases with in 14 days.
>
> Thoughts?
> - -
> Jody Garnett
>

[Geotools-devel] SF Storage warning

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

Sourceforge has sent a message that we are using a lot of storage and asks
us to clean up old releases with in 14 days.

Thoughts?
- -
Jody Garnett

[Geotools-devel] GeoTools PMC meeting, February 10th 2026

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

GeoTools / GeoServer PMC meeting - 2026-02-10Attending

   -

   Torben Barsballe


   -

   Cécile Vuilleumier
   -

   Jukka Rahkonen
   -

   Peter Smythe
   -

   Andrea Aime
   -

   Jody Garnett
   -

   Kevin Smith

Actions from prior meetings:

   - [image: non selezionata]

   Jody: Write blog post for 2026 Sponsorship, update wiki page, etc..
   - [image: non selezionata]

   action: Peter can make a CITE landing page with the new sticker, and
   thanking sponsors/in-kind
   - [image: non selezionata]

   action: Andrea small spring 7 proposal for the record

Agenda

   1.

   GS3 Update
   2.

   UI/UX Proposal
   3.

   AI Policy Chat
   4.

   Chit Chat

Actions

   - [image: non selezionata]

   peter: static image of gs3 gauge update website and blog posts
   - [image: non selezionata]

   jody: make an email or proposal about this so we have a wider discussion
   about choice of mkdocs for 2.28.x


GS3 Update

aside:

   -

   The crowdfunding graphic is broken? Perhaps permission change on
   spreadsheet
   -

      action: take a static image as the spreadsheet is done, update
      website and blog posts


Spring 7 is merged! Milestone 2 is completed

   -

   this is great :)


What is next:

   -

   Milestone 3: Delayed a bit until April 18th
   -

   Milestone 4 (this is new): for the integration topics like GeoNode


What are we doing with the delay:

   -

   The main one is spring 7 update stretched out milestone 2 a bit, very
   much worthwhile
   -

   The next one is doing some UI / UX updates for the major version change
   -

      https://github.com/geoserver/geoserver/wiki/GSIP-238 (next meeting
      topic)


Other updates:

   -

   Cecile: SQLite updates is working on it
   -

      Andrea confirms this is annoying, primary keys not supported in
      batch, sigh…
      -

      Breakout discussion on details, …
      -

      Problems creating two tables in a test and locking on itself
      -

   Alessio: Major work done on OIDC as a replacement for previous
   implementations
   -

      Q: Is this backported to 2.28.x?
      -

      It would be possible, but perhaps no longer due to change of spring
      security version due to spring 7 change
      -

      No the PRs are not backported
      -

   Gabe: Has GeoServer Cloud working already, ported to Spring Boot 4, nice
   work!

UI/UX Proposal

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

Jody is working with Stephano on this PR, discussed in previous meetings,
now a GSIP

Discussion:

   -

   how much javascript?
   -

      We are fine for now, Stephano is an expert, but long term we will
      have some things to maintain. Example not using bootstrap flex, give us
      some other javascript for responsive UI resizing
      -

   what do you mean make room for OGC API Services?
   -

      Make a page for "Features", with tabs for "General", "WFS", "OGCAPI"

AI Policy Chat

GDAL and others are making AI Policies:

   -

   We have been pretty informal so far
   -

   Other projects are being hit with AI Generated Junk PRs and are making a
   policy in response
   -

      we want to be clear to not waste maintainers time with pull requests
      that you do not understand yourself
      -


GDAL has:

   -

   https://github.com/OSGeo/gdal/pull/13880
   -

   This is a good start, let GDAL finish and then revisit this topic, in
   case they make good progress.
   -

   Jukka offers perspective that it is okay close these PRs,
   -

      GDAL set up policy to make this clear
      -

      Google summer code


GeoServer:

   -

   Not sure of need right now, …but we see having it in place could be
   useful
   -

   We do get security vulnerabilities reported this way, and they are
   annoying, and more importantly not effective. See presentation where auto
   report was correct, but no action occurred until a human was in place to
   explain impact etc…


sidebar on google summer code:

   -

   Yes GeoTools and GeoServer have history of taking part, mixed results, …
   -

      Beneficial for student, Ian was good at this 🙂
      -

      Mixed tracked record of keeping the resulting code
      -

      Our real goal is to keep a developer after the program finished
      -

   Other OSGeo projects, pgrouting for example, have good experience


Chit Chat

https://github.com/geoserver/geoserver/pull/9091

   -

   Work in progress, for example needs a better PR title
   -

   Ability to disable service versions


mkdocs:

   -

   tables within tables are the trouble?
   -

      Can we start rewriting the rst?
      -

      To fix table, un-indent, but that breaks numbering (for example)
      -

   Image mosaic looks better:
   https://geoserver.org/geoserver/en/user/data/raster/imagemosaic/configuration/

   -

   But other problems remain, developer guide wicket development page
   -

      notes in tables for example
      -

   Image + caption can end on the same line?
   -

      we can do two spaces after the image, then that will act as a <br/>
      tag
      -

   Q: Can we leave 2.28 as RST? But it makes backporting harder
   -

      This would simplify a lot of the challenge
      -

      however backport bot would not longer work for 6 months
      -

         We could break PR into change, and doc-change, …
         -

   Q: Could we accept the 2.28.x with glitches after the change?
   -

      We would have trouble with docs that update screen snap, and update
      the markdown changes
      -

      huh, backporting docs that includes screen snaps would always cause
      conflicts
      -

   https://github.com/petersmythe/translate
   -

      AI "improved" fork :)



Action:

   -

   jody: make an email or proposal about this so we have a wider discussion
   about choice of mkdocs for 2.28.x

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

[Torben B. <tor...@gm...>]

 Reminder that the next PMC meeting is scheduled for tomorrow, February 10,
at 18:30
<https://www.timeanddate.com/worldclock/fixedtime.html?year=2026&month=2&day=10&hour=18&min=30&sec=0&msg=GeoTools%20/%20GeoServer%20Meeting&ah=1&sort=1&p1=215>
 CET.

Cheers,
Torben

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

[Torben B. <tor...@gm...>]

Reminder that the next PMC meeting is scheduled for tomorrow, January 27,
at 18:30
<https://www.timeanddate.com/worldclock/fixedtime.html?year=2026&month=1&day=27&hour=18&min=30&sec=0&msg=GeoTools%20/%20GeoServer%20Meeting&ah=1&sort=1&p1=215>
 CET.

Cheers,
Torben

Re: [Geotools-devel] GeoTools 34.2, GeoServer 2.28.2, GeoWebCache 1.28.2 release

[Gabriel R. <gab...@ca...>]

Hi all

The coordinated releases are available:
- GeoTools 34.2 <https://geotoolsnews.blogspot.com/2026/01/geotools-34.html>
- GeoWebCache 1.28.2
<https://github.com/GeoWebCache/geowebcache/releases/tag/1.28.2>
- GeoServer 2.28.2
<https://geoserver.org/announcements/2026/01/21/geoserver-2-28-2-released.html>
- GeoServer Cloud 2.28.2.0
<https://github.com/geoserver/geoserver-cloud/releases/tag/v2.28.2.0>

Enjoy!

Gabe

*camptocamp*
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

*Gabriel Roldán*
Geospatial Solutions Architect



On Tue, Jan 20, 2026 at 9:45 AM Gabriel Roldan <
gab...@ca...> wrote:

> Hi developers,
>
> Sorry for the delay in starting this release train. I'm starting it today,
> but first will try to address this outstanding pull request as Pete
> requested a review last week:
>
> - https://github.com/geoserver/geoserver/pull/9037
>
> And this one as it's important for GeoServer Cloud:
> - https://github.com/geotools/geotools/pull/5494
>
> Thanks
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
> *Gabriel Roldán*
> Geospatial Solutions Architect
>

[Geotools-devel] GeoTools 34.2, GeoServer 2.28.2, GeoWebCache 1.28.2 release

[Gabriel R. <gab...@ca...>]

Hi developers,

Sorry for the delay in starting this release train. I'm starting it today,
but first will try to address this outstanding pull request as Pete
requested a review last week:

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

And this one as it's important for GeoServer Cloud:
- https://github.com/geotools/geotools/pull/5494

Thanks
*camptocamp*
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

*Gabriel Roldán*
Geospatial Solutions Architect