From lr at pcorp.us Fri Oct 9 15:42:37 2026 From: lr at pcorp.us (Regina Obe) Date: Fri, 9 Oct 2026 18:42:37 -0400 Subject: PostGIS Day 2026 Virtual Conference CFP deadline October 15th Message-ID: <000001dd583f$7c29a1b0$747ce510$@pcorp.us> The call for proposals for PostGIS Day 2026 happening on November 19th is ending in a little under a week. Get your talks in by October 15th or miss out. https://talks.osgeo.org/postgis-day-2026/cfp This is a virtual conference. Details here - https://postgis.net/community/events/2026-postgis-day/ Thanks, Regina From johncarmack at me.com Sat Oct 10 08:28:11 2026 From: johncarmack at me.com (John Carmack) Date: Sat, 10 Oct 2026 08:28:11 -0700 Subject: ST_AsMVTGeom: skipping wagyu for polygons it would leave alone Message-ID: <4D53305D-8B77-4173-8B1C-549852A3D2F2@me.com> Hi all, I contribute to Martin, MapLibre's tile server, and found this benchmarking PostGIS tile servers. ST_AsMVTGeom sends every polygon through wagyu, even when wagyu will hand it back unchanged. On dense building tiles that's most of the database's CPU. I've opened a patch that finds those rings with exact integer tests and writes them the way wagyu would, so the output stays identical byte for byte. Everything else still goes to wagyu. On Berlin's buildings it makes Martin's tile query 2.45x faster on a dense z14 tile and 2.44x on random z14 tiles, 1.65x at z16 and 1.12x at z18. On GH-647 Paul wrote that "maintaining valid outputs from MVT processing is just as important as performance." This only skips wagyu when it can prove what wagyu would return: 40,276,961 rings from Berlin, random rings and exhaustive small grids all came out identical. The pull request has the details. Ticket: https://trac.osgeo.org/postgis/ticket/6145 Pull request: https://github.com/postgis/postgis/pull/1182 It's for 3.8. I'd appreciate a review whenever you have time. Thanks! John From lr at pcorp.us Thu Oct 15 08:44:34 2026 From: lr at pcorp.us (Regina Obe) Date: Thu, 15 Oct 2026 11:44:34 -0400 Subject: PostGIS 3.7.0rc3 coming this monday or tuesday Message-ID: <000301dd5cbc$14109120$3c31b360$@pcorp.us> Just a heads up that I plan to release a 3.7.0 rc3 this coming Monday or Tuesday. I have a couple of loose ends to clear up like the documentation build before then. I'm hoping this will be the last rc before we release. As a side note PostgreSQL 19 rc1 came out today. Thanks, Regina From pjduplooy.gis at gmail.com Fri Oct 16 22:05:29 2026 From: pjduplooy.gis at gmail.com (Gandalf the Gray) Date: Sat, 17 Oct 2026 07:05:29 +0200 Subject: Winnie down Message-ID: Hi Regina. Winnie is down again. Pieter -------------- next part -------------- An HTML attachment was scrubbed... URL: From lr at pcorp.us Fri Oct 16 22:19:57 2026 From: lr at pcorp.us (Regina Obe) Date: Sat, 17 Oct 2026 01:19:57 -0400 Subject: Winnie down In-Reply-To: References: Message-ID: <002a01dd5df7$27c610a0$775231e0$@pcorp.us> Fixed From: Gandalf the Gray Sent: Saturday, October 17, 2026 1:05 AM To: postgis-devel at lists.osgeo.org Subject: Winnie down Hi Regina. Winnie is down again. Pieter -------------- next part -------------- An HTML attachment was scrubbed... URL: From lr at pcorp.us Tue Oct 20 22:21:53 2026 From: lr at pcorp.us (Regina Obe) Date: Wed, 21 Oct 2026 01:21:53 -0400 Subject: PostGIS 3.7.0rc3 release Message-ID: <001001dd611c$164ce6a0$42e6b3e0$@pcorp.us> The PostGIS Team is pleased to release PostGIS 3.7.0rc3! Best Served with PostgreSQL 19 RC1 , GEOS 3.15.0 , This version requires PostgreSQL 14 - 19rc1, GEOS 3.10 or higher, and Proj 6.1+. To take advantage of all features, GEOS 3.15+ is needed. To take advantage of all SFCGAL features SFCGAL 2.3.0+ is needed. This release contains fixes since 3.7.0rc2 release. Details at: https://postgis.net/2026/10/PostGIS-3.7.0rc3/ Source: https://download.osgeo.org/postgis/source/postgis-3.7.0rc3.tar.gz PDF En: https://download.osgeo.org/postgis/docs/postgis-3.7.0rc3-en.pdf HTML: https://download.osgeo.org/postgis/docs/doc-html-3.7.0rc3.tar.gz NOTE: postgis_tiger_geocoder and address_standardizer are no longer part of the PostGIS source code. Latest release of postgis_tiger_geocoder is noted - https://postgis.net/2026/08/PostGIS-Tiger-Geocoder-2025.2/ address_standardizer latest version is https://github.com/postgis/address_standardizer/releases/tag/v3.7.0 If you run into any issues, feel free to reply to this email or report on our ticket tracker as detailed on https://postgis.net/development/bug_reporting/ From pjduplooy.gis at gmail.com Wed Oct 21 00:49:26 2026 From: pjduplooy.gis at gmail.com (Gandalf the Gray) Date: Wed, 21 Oct 2026 09:49:26 +0200 Subject: Winnie down Message-ID: Hi Regina. Winnie is down again. Pieter -------------- next part -------------- An HTML attachment was scrubbed... URL: From lr at pcorp.us Fri Oct 23 12:53:00 2026 From: lr at pcorp.us (Regina Obe) Date: Fri, 23 Oct 2026 15:53:00 -0400 Subject: Branching off 3.7 later today Message-ID: <000f01dd6328$1c0675d0$54136170$@pcorp.us> Just a heads up I'm going to create a branch for stable-3.7 later today or over the weekend. Then I plan to release 3.7.0 Monday or Tuesday following. Let me know if you have any objections. Thanks, Regina