RE: st_srid lost in st_union

I personally want to release within the next 1-2 weeks cause we found some other issues we’d like to address as well.

 

But we have to discuss first.

 

Thanks,

Regina

 

 

 

From: Łukasz Szałek via postgis-users <[email protected]> 
Sent: Tuesday, January 7, 2025 12:53 PM
To: Paul Ramsey <[email protected]>
Cc: PostGIS Users Discussion <[email protected]>
Subject: Re: st_srid lost in st_union

 

How do you forecast the 3.5.2 release? What is the more/less date?

 

Best regards

Łukasz Szałek

 

 

 

From: Paul Ramsey <[email protected] <mailto:[email protected]> >
Date: Tuesday, 7 January 2025 at 18:22
To: Łukasz Szałek <[email protected] <mailto:[email protected]> >
Cc: PostGIS Users Discussion <[email protected] <mailto:[email protected]> >
Subject: Re: st_srid lost in st_union

[Nie otrzymujesz często wiadomości e-mail z [email protected] <mailto:[email protected]> . Dowiedz się, dlaczego jest to ważne, na stronie https://aka.ms/LearnAboutSenderIdentification ]

Sorry, no, it looks like due to an oversight the fix was applied to earlier branches, but not to 3.5, so 3.5.1 didn’t get it. It’s a one-liner in case you want to apply it yourself.

https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpostgis%2Fpostgis%2Fcommit%2F5b990cc7f4d91560aea78b5fd4b7656a398d2eb8 <https://github.com/postgis/postgis/commit/5b990cc7f4d91560aea78b5fd4b7656a398d2eb8> &data=05%7C02%7CLukasz.Szalek%40tomtom.com%7C48e1366b42a944b1191108dd2f3fd9e6%7C374f80267b544a3ab87d328fa26ec10d%7C0%7C0%7C638718673467028547%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=hhTAsTN3cldIDEu9mdHy%2F%2FPvljcDn5BjonAs7AVCyUQ%3D&reserved=0

Meanwhile, I pull apply it so it lands in 3.5.2.

P

> On Jan 7, 2025, at 9:12 AM, Łukasz Szałek via postgis-users <[email protected] <mailto:[email protected]> > wrote:
>
> Hi all
> I have used postgres 17.2 with postgis 3.5.1
> POSTGIS="3.5.1 48ab069" [EXTENSION] PGSQL="170" GEOS="3.13.0-CAPI-1.19.0" PROJ="9.5.1 NETWORK_ENABLED=OFF URL_ENDPOINT=https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcdn.proj.orguser_writable_directory%2F&data=05%7C02%7CLukasz.Szalek%40tomtom.com%7C48e1366b42a944b1191108dd2f3fd9e6%7C374f80267b544a3ab87d328fa26ec10d%7C0%7C0%7C638718673467047408%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=r5Ynjwi9YPrZpmas%2F70pTuhM%2BJxF%2BmC7bbSOvmIyYZ4%3D&reserved=0=/var/lib/pgsql/.local/share/proj DATABASE_PATH=/usr/proj95/share/proj/proj.db" (compiled against PROJ 9.5.1) LIBXML="2.9.13" LIBJSON="0.14" LIBPROTOBUF="1.3.3" WAGYU="0.5.0 (Internal)" TOPOLOGY
>  As it should already fix the issue of loosing st_srid while doing st_union.
> However when doing :
>  select ST_SRID(ST_GeomFromText('POLYGON ((4.9882543 50.4415584, 4.9882543 50.4415586, 4.9882545 50.4415586, 4.9882545 50.4415584, 4.9882543 50.4415584))',4326)),
> st_srid(ST_UNION(ARRAY[ST_GeomFromText('POLYGON ((4.9882543 50.4415584, 4.9882543 50.4415586, 4.9882545 50.4415586, 4.9882545 50.4415584, 4.9882543 50.4415584))',4326)]))  ;
>  again it is 4326 v 0.
>  Can someone confirm that fix was released in 3.5.1 ?
>  Best regards
> Łukasz Szałek