Opened 8 years ago

Closed 8 years ago

#28433 closed Bug (fixed)

comparing GEOSGeometry with non-canonical WKT string return False

Reported by: Sergey Fedoseev Owned by: Sergey Fedoseev
Component: GIS Version: 1.11
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description 

In [2]: from django.contrib.gis.geos import GEOSGeometry

In [3]: GEOSGeometry('POINT (0 0)') == 'POINT (0 0)'                                                                                                                                                  
Out[3]: True

In [4]: GEOSGeometry('POINT (0 0)') == GEOSGeometry('POINT (0.0 0.0)')
Out[4]: True

In [5]: GEOSGeometry('POINT (0 0)') == 'POINT (0.0 0.0)'
Out[5]: False

Change History (6)

comment:1 by Sergey Fedoseev, 8 years ago

Owner: changed from nobody to Sergey Fedoseev
Status: new → assigned

comment:2 by Sergey Fedoseev, 8 years ago

​PR

comment:3 by Sergey Fedoseev, 8 years ago

Has patch: set

comment:4 by Tim Graham, 8 years ago

Patch needs improvement: set
Triage Stage: Unreviewed → Accepted

comment:5 by Sergey Fedoseev, 8 years ago

Patch needs improvement: unset

comment:6 by Tim Graham <timograham@…>, 8 years ago

Resolution: → fixed
Status: assigned → closed

In 5ccbcc5b:

Fixed #28433 -- Made GEOSGeometry.eq() work correctly with non-canonical EWKT string.

Note: See TracTickets for help on using tickets.
Back to Top