Opened 12 years ago
Closed 11 years ago
#2110 closed defect (fixed)
POINT(0 0) = POINT EMPTY != POINT(1 1)
| Reported by: | strk | Owned by: | strk |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 2.0.4 |
| Component: | postgis | Version: | 2.0.x |
| Keywords: | history 2.0.4 | Cc: |
Description
This doesn't help analisys:
strk=# select 'POINT EMPTY'::geometry = 'POINT(1 1)'::geometry; ?column? ---------- f (1 row) strk=# select 'POINT EMPTY'::geometry = 'POINT(0 0)'::geometry; ?column? ---------- t (1 row)
I suspect it has to do with bounding box of EMPTY being arbitrarily taken as 0,0,0,0
Change History (4)
comment:1 by , 12 years ago
| Milestone: | PostGIS 2.0.2 → PostGIS 2.0.3 |
|---|
comment:2 by , 12 years ago
I'm not sure it's simple. It is the btree (bounding box based) comparison. I belive we did something low-level to fix the EMPTY=EMPTY case so maybe this one just isn't hitting the fixed path.
comment:3 by , 11 years ago
| Milestone: | PostGIS 2.0.3 → PostGIS 2.0.4 |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
comment:4 by , 11 years ago
| Keywords: | history 2.0.4 added |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.

Let's not try to solve this in 2.0.2 unless you think it's a simple solution.