Re: [postgis-users] what does it really mean for one geometry to be equal to another

2016-09-15 Thread Paul Norman
On 9/15/2016 10:11 PM, Sandro Santilli wrote: you could create an index on ST_SnapToGrid(geom, ), for points to be no closer than . This won't check that points are no closer than , nor will it solve floating point issues. It's the same as rounding. If two points are on either side of the lin

Re: [postgis-users] what does it really mean for one geometry to be equal to another

2016-09-15 Thread Paul Norman
On 9/15/2016 11:19 PM, Paul Norman wrote: I don't know of a great way to do this, but a bad way that might work is EXCLUDE USING GIST (ST_Buffer(geom, 0.1) WITH &&). See https://www.postgresql.org/docs/current/static/rangetypes.html#RANGETYPES-CONSTRAINT and the links from there. I haven't test

Re: [postgis-users] what does it really mean for one geometry to be equal to another

2016-09-15 Thread Paul Norman
On 9/15/2016 6:53 PM, Rhys A.D. Stewart wrote: = select premises, st_astext(g), g from service.location where st_astext(g) = 'POINT(727895.4 663599.3)' - premise

Re: [postgis-users] what does it really mean for one geometry to be equal to another

2016-09-15 Thread Sandro Santilli
On Thu, Sep 15, 2016 at 08:53:25PM -0500, Rhys A.D. Stewart wrote: > Now I'm just confused, the 2 premises have the same st_astext, but > different wkb representations and as such are not being caught in the > st_equals call. > > Is there some gotcha that I don't know about, maybe something in th

[postgis-users] what does it really mean for one geometry to be equal to another

2016-09-15 Thread Rhys A.D. Stewart
Greetings all, I maintain a medium size table of customer locations, which, for business purposes now needs to not have any coincident points. Table definition follows: = service.location ( premises text NOT NULL, matchtype te

Re: [postgis-users] OGC Simple Features Acces 1.21

2016-09-15 Thread Paul Ramsey
An inconsistency in an OGC specification!?!?!? Could be. Fact remains, they do provide examples of mixed dimensional inputs to the predicates, and they are the most confusing examples imaginable, since what does it mean for polygons (or points) to "cross"? Or for points to "overlap" vs "intersect".

[postgis-users] OGC Simple Features Acces 1.21

2016-09-15 Thread Ivan Santiago
Hello all This is not directly related to Postgis but... I was reading the PDF document: http://portal.opengeospatial.org/files/?artifact_id=25355

Re: [postgis-users] fuzzy tolerance

2016-09-15 Thread Daniel Baston
> Any words of warning about using a trigger and storing the data on a 10 cm > grid like i suggest? You may need to be aware of the differences between coordinates generated by ST_SnapToGrid, and coordinates generated by conversion from text. I wrote a bit about this at http://gis.stackexchange.c

Re: [postgis-users] Fw: just a message

2016-09-15 Thread Sandro Santilli
WARNING: this message is SCAM [1] - Nicklas system has evidently been compromised. I've set his account in moderation until the problem is resolved. [1] https://en.wikipedia.org/wiki/Confidence_trick --strk; On Wed, Sep 07, 2016 at 10:51:33AM +0300, Nicklas Aven wrote: > Dear, > > I just want