#2033 closed defect (fixed)
2.5D topology: Column has Z dimension but geometry does not
Reported by: | strk | Owned by: | strk |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 2.0.2 |
Component: | topology | Version: | 2.0.x |
Keywords: | history | Cc: |
Description
-- preparation select droptopology('t'); select topology.createtopology('t',0,0,true) as topoid; select topogeo_addpolygon('t', 'POLYGON((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0))'); -- bug exposure select topogeo_addlinestring('t', 'LINESTRING(1 1 0,0 1 0,0 1 1,1 1 1,1 1 0)');
The culprit is ST_ClosestPoint, see ticket #2032 What we could do is re-add the Z to the output of ST_ClosestPoint.
Change History (4)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Keywords: | history added |
---|---|
Resolution: | → fixed |
Status: | new → closed |
comment:4 by , 9 years ago
oh, another reason why I don't use 3DClosestPoint is that I want the closest point in 2d, not in 3d
Note:
See TracTickets
for help on using tickets.
hmm why aren't you using ST_3DClosestPoint? http://www.postgis.org/documentation/manual-svn/ST_3DClosestPoint.html