> ... Turned out that npts of the
> polygon retrieved from the table is 0 (the other polygon is a constant
> and its attributes are correct). I suspect the feature might
> affect other functions that uses polygons->npts like poly_contain.
> Would anyone happens to know the identity of the offe
"Kenneth Chan" <[EMAIL PROTECTED]> writes:
> ... Turned out that npts of the
> polygon retrieved from the table is 0 (the other polygon is a constant
> and its attributes are correct). I suspect the feature might
> affect other functions that uses polygons->npts like poly_contain.
> Would anyon
This feature does not affect the original version of poly_overlap as only a bounding
box test is preformed. I modified poly_overlap in an attempt to improve the
preciseness of poly_overlap. The function works when the column is not indexed or
when the column is indexed using rtree_gist fro
