[postgis-tickets] [PostGIS] #1979: TopoGeo_AddLinestring: return duplicated edge id, misses a created edge id

[PostGIS]

#1979: TopoGeo_AddLinestring: return duplicated edge id, misses a created edge id
----------------------+-----------------------------------------------------
 Reporter:  amartin   |       Owner:  strk         
     Type:  defect    |      Status:  new          
 Priority:  medium    |   Milestone:  PostGIS 2.0.4
Component:  topology  |     Version:  2.0.x        
 Keywords:            |  
----------------------+-----------------------------------------------------

Comment(by strk):

 Taking a closer look at this I don't see any problem with the duplicated
 edge id, as that's due to a different component of the multilinestring. If
 you add the path to the SELECT you get:
 {{{
 SELECT path, TopoGeo_AddLineString('t',geom, 0.8)
 FROM (SELECT (ST_Dump(p_geom)).*
  FROM (SELECT ST_GeomFromText('MULTILINESTRING ((535695.149659
 4352913.865809, 535688.723014 4352898.92539, 535723.74701 4352895.150892,
 535753.102703 4352892.178469, 535795.04699 4352887.189505, 535796.627126
 4352887.671191, 535833.621825 4352884.315548, 535876.015985
 4352880.471036),  (535688.497742 4352897.353794, 535688.721074
 4352898.927358, 535695.149659 4352913.865809))',25830) AS p_geom) AS
 geom_squery) AS lines;

  path | topogeo_addlinestring
 ------+-----------------------
  {1}  |                     5
  {1}  |                     4
  {2}  |                     6
  {2}  |                     4
 (4 rows)
 }}}

 You can see there's no duplicate within the same invocation of
 topogeo_addLineString.There are two invocations, each returning 2 edges.
 One edge is the same. All is ok about that.

 What would you expect amartin ?

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1979#comment:6>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.