[postgis-devel] [PostGIS] #76: ST_DumpPoints - I think we said we would add to TODO

[PostGIS]

#76: ST_DumpPoints - I think we said we would add to TODO
--------------------------+-------------------------------------------------
  Reporter:  robe         |       Owner:  robe         
      Type:  enhancement  |      Status:  assigned     
  Priority:  medium       |   Milestone:  postgis 1.5.0
 Component:  postgis      |     Version:  trunk        
Resolution:  accepted     |    Keywords:               
--------------------------+-------------------------------------------------
Old description:

> As described here
> [http://postgis.refractions.net/pipermail/postgis-devel/2008-
> June/003142.html http://postgis.refractions.net/pipermail/postgis-devel/
> 2008-June/003142.html]
>
> Though I would keep with the path, geom geom_dump structure we have for
> ST_Dump and ST_DumpRings.  Though the path would be rarely used, I think
> there are times it comes in handy to reference back to a geometry.

New description:

 As described here
 [http://postgis.refractions.net/pipermail/postgis-devel/2008-
 June/003142.html http://postgis.refractions.net/pipermail/postgis-devel/
 2008-June/003142.html]

 Though I would keep with the path, geom geom_dump structure we have for
 ST_Dump and ST_DumpRings.  Though the path would be rarely used, I think
 there are times it comes in handy to reference back to a geometry.

Comment (by kneufeld):

 I just attached an implementation of ST_DumpPoints by Maxime van Noppen
 (maxime at altribe.org) recently posted on postgis-users
 (http://postgis.refractions.net/pipermail/postgis-users/2009-
 August/024118.html)

 At first glance it looks promising.  Would a C implementation really be
 noticeably faster?

 Thoughts, team?

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/76#comment:4>
PostGIS <http://trac.osgeo.org/postgis/>
PostGIS