[postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true

[PostGIS]

#845: ST_Intersects() precision error - returns false instead of true
------------------------+---------------------------------------------------
 Reporter:  cdestigter  |       Owner:  pramsey      
     Type:  defect      |      Status:  new          
 Priority:  medium      |   Milestone:  PostGIS 2.0.0
Component:  postgis     |     Version:  1.5.X        
 Keywords:              |  
------------------------+---------------------------------------------------

Comment(by nicklas):

 Ok, does this mean that ST_Within, ST_Contains, ST_Intersects and so on
 uses native PostGIS functions for simplier cases where a point is one of
 the geometries?

 As you say that must be the reason that the new point in polygon is
 implemented to make that distinction.

 So, the wisest probably is to sit down and get a grip of the winding
 algorithm and review it. As discussed in the link above there is
 significant performance differences depending on how the counting winding
 is implemented.

 It would be nice to have the fastest and most stable way of doing it of
 course.

 I think I can look at it in a few days, if it is not clear to someone else
 what should be done, already now.

 And I suggest we leave 3d out of this. Maybe it should be rewritten to the
 same algorithm but I think it has to be separate code.


 /Nicklas

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