Your message dated Tue, 25 Jul 2023 21:32:27 +0000
with message-id <[email protected]>
and subject line Bug#1035921: fixed in postgis 3.1.1+dfsg-1+deb11u2
has caused the Debian Bug report #1035921,
regarding postgis: Axis order regression since 3.1.1+dfsg-1+deb11u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1035921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035921
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: postgis
Version: 3.1.1+dfsg-1+deb11u1
Severity: important
Tags: upstream fixed-upstream pending
Control: submitter -1 Stephan Großberndt <[email protected]>
Control: fixed -1 postgis/3.1.4+dfsg-1
Dear Maintainer,
As reported by Stephan Großberndt <[email protected]> in #1031410:
"
at our company we were quite surprised by this seemingly minor update
3.1.1+dfsg-1+deb11u1, because it completely broke an application: Due to the
change the x and y axis are now inverted when converting coordinates to EPSG
31466:
Before (this output is from 11.19, but was like this on 13 before as well):
SELECT geometry,ST_AsGeoJSON(ST_Transform(ST_SetSRID(geometry, 3857), 31466))
FROM osm_car_sharing_node LIMIT 1;
geometry | st_asgeojson
----------------------------------------------------+--------------------------------------------------------------------
0101000020110F000004F0844A1349264120ED527FE9DD5841 |
{"type":"Point","coordinates":[2539841.86185744,5586869.51937972]}
(1 row)
Now:
SELECT geometry, ST_AsGeoJSON(ST_Transform(ST_SetSRID(geometry, 3857), 31466))
FROM osm_car_sharing_node LIMIT 1;
-[ RECORD 1
]+------------------------------------------------------------------------------------------------------------------------------
geometry | 0101000020110F000004F0844A1349264120ED527FE9DD5841
st_asgeojson |
{"type":"Point","crs":{"type":"name","properties":{"name":"EPSG:31466"}},"coordinates":[5586869.519378289,2539841.861857439]}
I understand the rationale for the change in general, but in my opinion such a
major change really should not be part of such a minor update.
Is there an option to fix this apart from changing all queries?
"
And:
"
after further investigation this looks more like a bug in the backport.
At first I thought the change was about flipping x and y for all coordinate
systems except those containing "lat/lon", which did not make much sense to me,
but I would have been willing to accept this.
But apparently this flip is only in this PostGIS 3.1.1+dfsg-1+deb11u1 version,
earlier and later PostGIS versions correctly return x as x and y as y.
For this query:
SELECT
ST_AsGeoJSON(ST_Transform(ST_SetSRID('0101000020110F000004F0844A1349264120ED527FE9DD5841'::geometry,
3857), 31466));
the following versions correctly return x=2539841,y=5586869:
- PostgresQL 11 with PostGIS 2.5.1+dfsg-1 from Debian Sources
- PostgresQL 11 with PostGIS 2.5.5+dfsg-1.pgdg100+2 from PostgreSQL Sources
- PostgresQL 13 with PostGIS 3.1.1+dfsg-1 from Debian Sources
- PostgresQL 13 with PostGIS 3.3.2+dfsg-1.pgdg110+1 from Debian Sources
Only
- PostgresQL 13 with PostGIS 3.1.1+dfsg-1+deb11u1 from Debian Sources
incorrectly returns x=5586869,y=2539841
Should I file another bug report for this?
"
Some digging in the upstream stable-3.1 branch reveals two additional commits
required to resolve this regression:
https://trac.osgeo.org/postgis/changeset/11efb9f0cdc71cf2bdc4850491218495a07b18ba/git
https://trac.osgeo.org/postgis/changeset/8baf0b07b26df12d246c82bdae8ecd77371f3d24/git
With these two commits added as patches to the postgis (3.1.1+dfsg-1+deb11u1)
package, the order is correct again:
gis=# SELECT
ST_AsGeoJSON(ST_Transform(ST_SetSRID('0101000020110F000004F0844A1349264120ED527FE9DD5841'::geometry,
3857), 31466));
st_asgeojson
-------------------------------------------------------------------------------------------------------------------------------
{"type":"Point","crs":{"type":"name","properties":{"name":"EPSG:31466"}},"coordinates":[2539841.861857439,5586869.519378289]}
(1 row)
The axis order for the issue reported in #1031392 is also still correct:
gis=# SELECT ST_AsEWKT(ST_Transform(ST_GeomFromEWKT('SRID=3976;POINT(-25000
75000)'), 4326));
st_asewkt
--------------------------------------------------------
SRID=4326;POINT(-18.43494882292201 -89.27021258118658)
(1 row)
--- End Message ---
--- Begin Message ---
Source: postgis
Source-Version: 3.1.1+dfsg-1+deb11u2
Done: Bas Couwenberg <[email protected]>
We believe that the bug you reported is fixed in the latest version of
postgis, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bas Couwenberg <[email protected]> (supplier of updated postgis package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 11 May 2023 10:39:28 +0200
Source: postgis
Architecture: source
Version: 3.1.1+dfsg-1+deb11u2
Distribution: bullseye
Urgency: medium
Maintainer: Debian GIS Project <[email protected]>
Changed-By: Bas Couwenberg <[email protected]>
Closes: 1035921
Changes:
postgis (3.1.1+dfsg-1+deb11u2) bullseye; urgency=medium
.
* Add upstream patches to fix axis order regession.
(closes: #1035921)
Checksums-Sha1:
70e07671c93ff08e4cb5f33bc3989859622c510b 2935 postgis_3.1.1+dfsg-1+deb11u2.dsc
3129247cce3fe693d4c4aea6b71d4b3a11196c7e 42568
postgis_3.1.1+dfsg-1+deb11u2.debian.tar.xz
0e51d97d191ea0704db9f8e1b665b5e435b16cf2 19561
postgis_3.1.1+dfsg-1+deb11u2_amd64.buildinfo
Checksums-Sha256:
eb1e791aba4456eaa47e54666278e7dcc515ff347ba7b693ede46b173f165527 2935
postgis_3.1.1+dfsg-1+deb11u2.dsc
2389d4821aaafe27b484d6d0d050a19acce9f127becb99264f6e1bd5a157dc5a 42568
postgis_3.1.1+dfsg-1+deb11u2.debian.tar.xz
88792baa7ff7bf626057dc2ed98bb624777c365d4482525796f56d9cab6a02f9 19561
postgis_3.1.1+dfsg-1+deb11u2_amd64.buildinfo
Files:
e4aa2807a4342e16809bdbd8dbeb409b 2935 misc optional
postgis_3.1.1+dfsg-1+deb11u2.dsc
6dba9a33ce34acb3fe3140858230830f 42568 misc optional
postgis_3.1.1+dfsg-1+deb11u2.debian.tar.xz
d884f2619d7e1b0b92a0d45838bd226f 19561 misc optional
postgis_3.1.1+dfsg-1+deb11u2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmTAByAACgkQZ1DxCuiN
SvHPWBAAiH0jWTH+z20t/sBtMr6ho7xrmqr+vZ4Yf6Z7/Ays/2LhUuiuVCBD6QYC
0ax1MnQoyo/Y8lp46PTkYVuEFFjkORtaEqtqT9pb+zP4fDkOpOj/cdoNpQL4BZGX
1UaMk04CKVms1UDHARuoP1ojGIYW5e5L2kaftTxYQXt8lIHtVsCXXVAZwaw2in9x
vxdCfbAhOPAAWMiMPJq76V0y2+t8ZzfonSnjTQWBSZgXj9+BMGQZgAdBVn2xaybd
sN74esBgXKpTT7pjpvj/+IRXbdYCGMAZsnkRPqQ4bvL/IHLx2JLro6aJ2HmS9XOq
CLk2dtjI+PC3IKkG97dBJs2UxNZFpfZiSyjeLN0snpRzZ54O/2U2UFr2qHtdEVvz
oyMuee/ryyl8cp7bsnNmWgmkzBv0xUO6Ia65AAaesfq0CgjTt8p2QugGV5Nxa/lu
iGH4pEfy62VxXlSk+rks69cd9yOHGmuQkBThmTpQLMOMQYRu37PfMe3reIS+QWAq
bIHrWfo2QAhHihu2iEOcsJHDqb99f//qQOnGJO4/K9AIDDOHHUgxA1BAJQ1zKcmO
xX35jOSnKdl/Bid39CbORRqkE3QBwqYzk+ZuCgl+Y+3pN3mN8HWO2RbqIbuu9s/r
eh9dvgIk/lxcAOJfBLvLOo5tPrNNTNf42X3FZjI4neLhdLdGuxY=
=fKho
-----END PGP SIGNATURE-----
--- End Message ---
