[postgis-tickets] [SCM] PostGIS branch stable-3.1 updated. 3.1.7-23-ga6966410b
git at osgeo.org
git at osgeo.org
Sat Nov 5 22:12:39 PDT 2022
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "PostGIS".
The branch, stable-3.1 has been updated
via a6966410b0f972577a958825d38902100cd0129d (commit)
via d624047c8d1af68deab8b833e72eccba0a6a9bf7 (commit)
from fe5eb4f5421b753292f74d2f0dc3533387f012b9 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit a6966410b0f972577a958825d38902100cd0129d
Author: Regina Obe <lr at pcorp.us>
Date: Sun Nov 6 01:02:18 2022 -0400
Take out GEOS boundary test that no longer agrees in
yet to be released GEOS micros
References #5282 for PostGIS 3.1.8
diff --git a/regress/core/boundary.sql b/regress/core/boundary.sql
index 68dc883d8..27d24d29b 100644
--- a/regress/core/boundary.sql
+++ b/regress/core/boundary.sql
@@ -1,5 +1,6 @@
SELECT ST_AsText(ST_Boundary(ST_GeomFromText('LINESTRING(1 1,0 0, -1 1)')));
SELECT ST_AsText(ST_Boundary(ST_GeomFromText('POLYGON((1 1,0 0, -1 1, 1 1))')));
SELECT ST_AsEWKT(ST_Boundary(ST_GeomFromEWKT('POLYGON((1 1 1,0 0 1, -1 1 1, 1 1 1))')));
-SELECT ST_AsEWKT(ST_Boundary(ST_GeomFromEWKT('MULTILINESTRING((1 1 1,0 0 0.5, -1 1 1),(1 1 0.5,0 0 0.5, -1 1 0.5, 1 1 0.5) )')));
+-- no longer matches old answer in newer GEOS micros from GEOS 3.9.4
+--SELECT ST_AsEWKT(ST_Boundary(ST_GeomFromEWKT('MULTILINESTRING((1 1 1,0 0 0.5, -1 1 1),(1 1 0.5,0 0 0.5, -1 1 0.5, 1 1 0.5) )')));
SELECT ST_AsText(ST_Boundary(ST_GeomFromText('TRIANGLE((1 1,0 0, -1 1, 1 1))')));
diff --git a/regress/core/boundary_expected b/regress/core/boundary_expected
index 8105f0bcb..0b9dd701b 100644
--- a/regress/core/boundary_expected
+++ b/regress/core/boundary_expected
@@ -1,5 +1,4 @@
MULTIPOINT(1 1,-1 1)
LINESTRING(1 1,0 0,-1 1,1 1)
LINESTRING(1 1 1,0 0 1,-1 1 1,1 1 1)
-MULTIPOINT(-1 1 1,1 1 0.75)
LINESTRING(1 1,0 0,-1 1,1 1)
commit d624047c8d1af68deab8b833e72eccba0a6a9bf7
Author: Regina Obe <lr at pcorp.us>
Date: Sun Nov 6 00:51:19 2022 -0400
Take out relate_bnr tests that gives incorrect answer. References #5282 for PostGIS 3.1.8
diff --git a/regress/core/relate_bnr.sql b/regress/core/relate_bnr.sql
index 2c5d57447..5813e9942 100644
--- a/regress/core/relate_bnr.sql
+++ b/regress/core/relate_bnr.sql
@@ -28,7 +28,8 @@ SELECT '27', st_relate(a,b,1) as r1, st_relate(a,b,2) as r2, st_relate(a,b,3) as
SELECT '28', st_relate(a,b,1) as r1, st_relate(a,b,2) as r2, st_relate(a,b,3) as r3, st_relate(a,b,4) as r4 FROM (select 'LINESTRING(0 0,60 0,60 60,60 0,120 0)'::geometry as a, 'MULTILINESTRING((0 0,60 0),(60 0,120 0),(60 0,60 60))'::geometry as b) as f;
SELECT '29', st_relate(a,b,1) as r1, st_relate(a,b,2) as r2, st_relate(a,b,3) as r3, st_relate(a,b,4) as r4 FROM (select 'LINESTRING(60 0,20 80,100 80,80 120,40 140)'::geometry as a, 'LINESTRING(140 300,220 160,260 200,240 260)'::geometry as b) as f;
SELECT '30', st_relate(a,b,1) as r1, st_relate(a,b,2) as r2, st_relate(a,b,3) as r3, st_relate(a,b,4) as r4 FROM (select 'LINESTRING(60 0,20 80,100 80,80 120,40 140)'::geometry as a, 'LINESTRING(60 40,140 40,140 160,0 160)'::geometry as b) as f;
-SELECT '31', st_relate(a,b,1) as r1, st_relate(a,b,2) as r2, st_relate(a,b,3) as r3, st_relate(a,b,4) as r4 FROM (select 'LINESTRING(60 0,20 80,100 80,80 120,40 140)'::geometry as a, 'LINESTRING(140 280,240 280,240 180,140 180,140 280)'::geometry as b) as f;
+-- Taken out because answer changes in GEOS 3.9.4, 3.10.4, 3.11.1, 3.12.0, and no need to test this border case in PostGIS
+-- SELECT '31', st_relate(a,b,1) as r1, st_relate(a,b,2) as r2, st_relate(a,b,3) as r3, st_relate(a,b,4) as r4 FROM (select 'LINESTRING(60 0,20 80,100 80,80 120,40 140)'::geometry as a, 'LINESTRING(140 280,240 280,240 180,140 180,140 280)'::geometry as b) as f;
SELECT '32', st_relate(a,b,1) as r1, st_relate(a,b,2) as r2, st_relate(a,b,3) as r3, st_relate(a,b,4) as r4 FROM (select 'LINESTRING(140 0,0 0,40 60,0 120,60 200,220 160,220 40)'::geometry as a, 'LINESTRING(80 140,180 100,160 40,100 40,60 100,80 140)'::geometry as b) as f;
SELECT '33', st_relate(a,b,1) as r1, st_relate(a,b,2) as r2, st_relate(a,b,3) as r3, st_relate(a,b,4) as r4 FROM (select 'LINESTRING(20 20,80 80)'::geometry as a, 'LINESTRING(20 20,80 80)'::geometry as b) as f;
SELECT '34', st_relate(a,b,1) as r1, st_relate(a,b,2) as r2, st_relate(a,b,3) as r3, st_relate(a,b,4) as r4 FROM (select 'LINESTRING(40 40,160 160,200 60,60 140)'::geometry as a, 'LINESTRING(40 40,160 160,200 60,60 140)'::geometry as b) as f;
diff --git a/regress/core/relate_bnr_expected b/regress/core/relate_bnr_expected
index 89dabee7d..6f57aeaec 100644
--- a/regress/core/relate_bnr_expected
+++ b/regress/core/relate_bnr_expected
@@ -28,7 +28,6 @@
28|10FF0FFF2|10FF0FFF2|1FFFFFFF2|10FF0FFF2
29|FF1FF0102|FF1FF0102|FF1FF0102|FF1FF0102
30|FF1FF0102|FF1FF0102|FF1FFF1F2|FF1FF0102
-31|FF1FF01F2|FF1FF01F2|FF1FF01F2|FF1FF01F2
32|FF1FF01F2|FF1FF0102|FF1FFF1F2|FF1FF01F2
33|1FFF0FFF2|1FFF0FFF2|1FFFFFFF2|1FFF0FFF2
34|1FFF0FFF2|1FFF0FFF2|1FFFFFFF2|1FFF0FFF2
-----------------------------------------------------------------------
Summary of changes:
regress/core/boundary.sql | 3 ++-
regress/core/boundary_expected | 1 -
regress/core/relate_bnr.sql | 3 ++-
regress/core/relate_bnr_expected | 1 -
4 files changed, 4 insertions(+), 4 deletions(-)
hooks/post-receive
--
PostGIS
More information about the postgis-tickets
mailing list