[postgis-devel] [PostGIS] #1160: operator = returns wrong results checking two POINTS
PostGIS
trac at osgeo.org
Tue Aug 16 04:10:59 PDT 2011
#1160: operator = returns wrong results checking two POINTS
-------------------------+--------------------------------------------------
Reporter: gabrimonfa | Owner: pramsey
Type: defect | Status: closed
Priority: medium | Milestone: PostGIS 1.5.4
Component: postgis | Version: 1.5.X
Resolution: wontfix | Keywords:
-------------------------+--------------------------------------------------
Changes (by robe):
* status: new => closed
* resolution: => wontfix
* milestone: PostGIS 2.0.0 => PostGIS 1.5.4
Comment:
gabrimonfa,
I don't think this is a bug. First of all you are using = instead the hex
compare or ST_Equals. The = operator just compares float4 bounding boxes
in prior versions.
In 2.0 this is a double precision box so its not a surprise 2.0 gives a
more correct answer.
If you get true with ST_Equals, then there is an issue, otherwise I'll
just dismiss this as a limitation for float4 boxes. Paul can confirm.
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1160#comment:1>
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.
More information about the postgis-devel
mailing list