Opened 9 years ago

Closed 9 years ago

Last modified 6 years ago

#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:


  -- 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 Changed 9 years ago by robe

comment:2 Changed 9 years ago by strk

Keywords: history added
Resolution: fixed
Status: newclosed

Because it won't give me 2d results when fed 2d input ...

Anyway this case is closed with r10378 in 2.0 branch and r10381 in trunk.

comment:3 Changed 6 years ago by strk

See also #3244

comment:4 Changed 6 years ago by strk

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.