On 5/24/2016 6:31 PM, Timothy Asquith wrote:
- I’m experimenting with ST_Snap and filtering out ST_Touches, but
it still returning the same 3 results
You may want to use the dimensionally extended 9 intersection model
(http://postgis.net/docs/manual-2.2/using_postgis_dbmanagement.html#DE-
Thanks Paul,
You’re absolutely right that the intersect query should always have returned
touching polygons. I’m not sure how we were ever getting the desired results.
That’s what I’m looking into now.
Interestingly, the critical difference seems to be the use of binary geometry.
The land parc
The question is not why ST_Intersects() is returning boundary touching
results, it's why your old version did not (at least, as far as you
observed). Because, ST_Intersects(A,B) is *supposed* to return true
for any object B that is not disjoint from A. So, either you were not
observing what you tho
I have a table of land parcels in my PostGIS database, and I'm doing a basic
spatial join against zoning polygons.
I'm having issues where a previously-correct query is now returning different
results.
Up until now, I've been using a Geoserver WFS, and making these queries using
CQL's INTERSEC
Hey,
postgres list PostgreSQL General ,
or postgres dev list PostgreSQL Hackers .
I would more likely say dev list.
I do not know how you use your in memory layer, but you have to keep in
mind that postgres wipes memory of pl functions.
In python, one way to bypass that (for the same session) is
