Changes between Initial Version and Version 1 of Ticket #26920


Ignore:
Timestamp:
Jul 20, 2016, 7:03:50 AM (8 years ago)
Author:
Raphael Das Gupta
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #26920 – Description

    initial v1  
    2020The semantic of coordinates depends completely on the spatial reference system. The same numbers refer to completely different positions when interpreted in different coordinate systems. Therefore, I think the geometries should compare unequal if both have an SRID set and those SRIDs are different. Not sure what should happen when comparing geometries where exactly one of them has an SRID.
    2121
    22 If the currently observed behaviour is the intended one (or if it is retained for backwards compatibility reasons), the documentation should point that out. [https://docs.djangoproject.com/en/1.9/ref/contrib/gis/geos/#geometries-are-pythonic It already points out that the "Equality operator doesn’t check spatial equality"], but to me that only made clear that spatial equality does not imply `GEOSGeometry` object equality, but not that neither does `GEOSGeometry` object equality imply spatial equality. Also, [https://docs.djangoproject.com/en/1.9/ref/contrib/gis/geos/#django.contrib.gis.geos.GEOSGeometry.equals equals()], which is mentioned in that admonition as an alternative doesn't seem to care about SRID, either:
     22If the currently observed behaviour is the intended one (or if it is retained for backwards compatibility reasons), the documentation should point that out. [https://docs.djangoproject.com/en/1.9/ref/contrib/gis/geos/#geometries-are-pythonic It already points out that the "Equality operator doesn’t check spatial equality"], but to me that only made clear that spatial equality does not imply `GEOSGeometry` object equality, but not that neither does `GEOSGeometry` object equality imply spatial equality. Also, [https://docs.djangoproject.com/en/1.9/ref/contrib/gis/geos/#django.contrib.gis.geos.GEOSGeometry.equals equals()], which is mentioned in that admonition as an alternative, doesn't seem to care about SRID, either:
    2323{{{#!python
    2424assert not p0.equals(p1)  # AssertionError
Back to Top