Opened 12 years ago
Closed 8 years ago
#594 closed defect (duplicate)
geos turns 'POLYGON EMPTY' into 'POLYGON(EMPTY)'
| Reported by: | cdestigter | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 3.6.1 |
| Component: | Default | Version: | 3.3.3 |
| Severity: | Unassigned | Keywords: | |
| Cc: |
Description
I wouldn't mind except that in postgis, ST_IsEmpty('POLYGON(EMPTY)') ==> False.
Using the geodjango bindings:
>>> from django.contrib.gis import geos
>>> g = geos.GEOSGeometry('POLYGON EMPTY')
>>> print g.wkt, g.hex
'01030000000100000000000000'
>>> g = geos.GEOSGeometry('POLYGON(EMPTY)')
>>> print g.wkt, g.hex
'01030000000100000000000000'
Change History (9)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Even worse, I can't even use hex to create the geometry, which means I can't work around the bug:
>>> geos.GEOSGeometry('010300000000000000').hex
'01030000000100000000000000'
comment:3 by , 12 years ago
| Milestone: | 3.3.6 → 3.3.7 |
|---|
I see the postgis side has been fixed (but only 2.1.x) Have a patch for the GEOS side of it ?
comment:4 by , 12 years ago
| Milestone: | 3.3.7 → 3.3.x |
|---|
comment:5 by , 11 years ago
| Milestone: | 3.3.9 → 3.5.0 |
|---|
oh no the empty typed space again with no patch to support it. Push.
comment:6 by , 9 years ago
| Milestone: | 3.5.0 → 3.6.0 |
|---|
comment:9 by , 8 years ago
| Milestone: | 3.7.0 → 3.6.1 |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Yep, confirmed, thanks for checking.
Note:
See TracTickets
for help on using tickets.

I filed a postgis bug for that ST_IsEmpty issue: http://trac.osgeo.org/postgis/ticket/2015