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

View: New views
2 Messages — Rating Filter:   Alert me  

Parent Message unknown Re: [PostGIS] #76: ST_DumpPoints - I think we said we would add to TODO

by PostGIS-4 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

#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:              
--------------------------+-------------------------------------------------
Comment (by kneufeld):

 This ticket is a year old now and the functionality has again been
 requested on -users.

 I recommend that we add the attached plpgsql solution to PostGIS and close
 this ticket.  A new ticket can be added to document the function, another
 to improve/rewrite it to C, and maybe a third to add regression tests.

 I would much rather have a slow, but functional, method in PostGIS, than a
 really fast / robust '''non-existent''' function in C.

--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/76#comment:10>
PostGIS <http://trac.osgeo.org/postgis/>
PostGIS
_______________________________________________
postgis-devel mailing list
postgis-devel@...
http://postgis.refractions.net/mailman/listinfo/postgis-devel

Parent Message unknown Re: [PostGIS] #76: ST_DumpPoints - I think we said we would add to TODO

by PostGIS-4 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

#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:              
--------------------------+-------------------------------------------------
Comment (by robe):

 +1 I guess enough people have asked for this that a slower implementation
 is better than none at all.  And since its not trivially obvious and
 something we want eventually in our code base.

 FWIW: Nicklas started working on a C implementation.  He has all the
 recursive logic done, and I had promised to try to get this from the
 recursive like model he has (which does just write statements for
 debugging at the moment), into the stack push model employed by the other
 ST_Dump functions.  I'm still not convinced a stack model is the best
 given that most people think in terms of recursion rather than stacks
 (stacks is so assembler) though the stack model is probably more efficient
 for this.

 Anyrate I apologize for letting this slide.  I don't think I'll have time
 to look into it before 1.5 release time especially given my deficient C
 skills and the fact I'm over extended on at least 5 other projects with
 fairly firm approaching deadlines.

--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/76#comment:11>
PostGIS <http://trac.osgeo.org/postgis/>
PostGIS
_______________________________________________
postgis-devel mailing list
postgis-devel@...
http://postgis.refractions.net/mailman/listinfo/postgis-devel