New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note to ST_Equals that the function does not support geometry collections #14

Closed
wants to merge 1 commit into
base: svn-trunk
from

Conversation

Projects
None yet
5 participants
@nmandery

nmandery commented Dec 2, 2013

I just had a situation where ST_Equals failed to compare GeometryCollections. Looking add the source this is normal behavior, but there is no mention of it in the docs of ST_Equals.

This pull request adds a section to the documentation.

@strk

This comment has been minimized.

Show comment
Hide comment
@strk

strk Sep 24, 2014

Member

@robe2 can you look at this ?

Member

strk commented Sep 24, 2014

@robe2 can you look at this ?

@mwtoews

This comment has been minimized.

Show comment
Hide comment
@mwtoews

mwtoews Apr 12, 2015

The problem is deeper than just ST_Equals. See http://lists.osgeo.org/pipermail/postgis-devel/2015-April/024827.html

If you have a homogeneous geometry collection, e.g. from ST_Polygonize, then use ST_CollectionExtract(geom, 3) to get a MultiPolygon, which works with ST_Equals and other relate functions.

mwtoews commented Apr 12, 2015

The problem is deeper than just ST_Equals. See http://lists.osgeo.org/pipermail/postgis-devel/2015-April/024827.html

If you have a homogeneous geometry collection, e.g. from ST_Polygonize, then use ST_CollectionExtract(geom, 3) to get a MultiPolygon, which works with ST_Equals and other relate functions.

@strk

This comment has been minimized.

Show comment
Hide comment
@strk

strk Nov 20, 2015

Member

@nmandery are you planning to provide better wording for the manual about this ?
It's basically that geometrycollection with proper topology work while those with ambiguous one would not. A workaround is to pass them through ST_UnaryUnion beforehand.
See https://trac.osgeo.org/geos/ticket/725

Member

strk commented Nov 20, 2015

@nmandery are you planning to provide better wording for the manual about this ?
It's basically that geometrycollection with proper topology work while those with ambiguous one would not. A workaround is to pass them through ST_UnaryUnion beforehand.
See https://trac.osgeo.org/geos/ticket/725

@pramsey

This comment has been minimized.

Show comment
Hide comment

@pramsey pramsey closed this Feb 25, 2016

strk pushed a commit that referenced this pull request Feb 25, 2016

Add note per #14
git-svn-id: http://svn.osgeo.org/postgis/trunk@14693 b70326c6-7e19-0410-871a-916f4a2858ee

Algunenano added a commit to Algunenano/postgis that referenced this pull request May 21, 2018

Merge pull request #14 from CartoDB/svn-2.4-cartodb-merge
Merge community 2.4 (2018-05-07) with Carto branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment