[postgis-devel] [PostGIS] #1345: ST_StartPoint, ST_EndPoint regress failure

[PostGIS]

#1345: ST_StartPoint, ST_EndPoint regress failure
-----------------------+----------------------------------------------------
  Reporter:  robe      |       Owner:  pramsey      
      Type:  defect    |      Status:  closed       
  Priority:  critical  |   Milestone:  PostGIS 2.0.0
 Component:  postgis   |     Version:  trunk        
Resolution:  fixed     |    Keywords:               
-----------------------+----------------------------------------------------

Comment(by robe):

 The ST_NumInteriorRings one might be something we should fix (or at least
 think about a bit more), as that is a well documented behavior which
 arguably is a sometimes useful but stupid behavior as it could trap people
 into thinking multipolygons are properly handled unless they scrutinized
 the docs :)


 http://www.postgis.org/documentation/manual-svn/ST_NumInteriorRings.html

 My ST_StartPoint/ST_EndPoint was an undocumented behavior so people
 relying on that behavior were probably doing so out of share ignorance :).
 It just so happens that tiger edges I always brought them in as
 multilinestrings because even though they were mostly single linestrings,
 there are a few multilinestrings in there.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1345#comment:10>
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.