Opened 8 years ago
Last modified 5 years ago
#3787 new defect
Wrong results when using 3D in topology
Reported by: | aperi2007 | Owned by: | strk |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS Fund Me |
Component: | topology | Version: | 2.3.x |
Keywords: | Cc: |
Description
Hi, working with us rt_topology suite we discovered an issue on the topology. Other test show that the issue is alsoin postgis .
I try the test on postgis 2.3.2.
On postgis 2.3.2:
I try this little sql:
select topology.droptopology('topo_test'); select topology.createtopology('topo_test', 6707, 0.0145,true); select topology.TopoGeo_AddLineString( 'topo_test' , GeomFromEWKT( 'SRID=6707;LineString(0 0 0, 100 0 0)'), 0.0145 ); select topology.TopoGeo_AddLineString( 'topo_test' , GeomFromEWKT( 'SRID=6707;LineString(50 -50 0.001, 50 50 0.001)') , 0.0145 );
The result retrieved using
select ST_Astext(geom) from topo_test.edge_data;
Is
LINESTRING Z(0 0 0, 50 0 0) LINESTRING Z(50 0 0, 100 0 0) LINESTRING Z(50 -50 0.001, 50 0 0.0005) LINESTRING Z(50 0 0.0005, 50 50 0.001)
Istead if I try the same noding using the usual ST_NOde function: The result I have is this other:
ST_AsText(
ST_Node(
ST_Collect(
GeomFromEWKT( 'SRID=6707;MultiLineString((0 0 0, 100 0 0))'), GeomFromEWKT( 'SRID=6707;MultiLineString((50 -50 0.001, 50 50 0.001))')
)
)
)
(0 0 0, 50 0 0.0005), (50 -50 0.001, 50 0 0.0005), (50 0 0.0005, 100 0 0), (50 0 0.0005, 50 50 0.001)
I open a ticket also in the rt_topology issue system:
Change History (8)
comment:1 by , 7 years ago
Milestone: | → PostGIS 2.4.1 |
---|---|
Owner: | changed from | to
comment:2 by , 7 years ago
Milestone: | PostGIS 2.4.1 → PostGIS 2.4.2 |
---|
comment:3 by , 7 years ago
Milestone: | PostGIS 2.4.2 → PostGIS 2.4.3 |
---|
comment:4 by , 7 years ago
Component: | postgis → topology |
---|---|
Milestone: | PostGIS 2.4.3 → PostGIS 2.4.4 |
comment:5 by , 7 years ago
Milestone: | PostGIS 2.4.4 → PostGIS 2.5.0 |
---|
comment:6 by , 6 years ago
Milestone: | PostGIS 2.5.0 → PostGIS 2.4.5 |
---|
comment:7 by , 6 years ago
Milestone: | PostGIS 2.4.5 → PostGIS 2.4.6 |
---|
comment:8 by , 5 years ago
Milestone: | PostGIS 2.4.6 → PostGIS Fund Me |
---|
Results changed in 3.0alpha4. I believe there is no definition on what noding process should do for two non-3D-intersecting 2D-intersecting geometries. How should it be and why?
Proper 3D topology should even not node these as they don't intesect in 3D. That would be a bigger rewrite that needs more definitions.