Timeline for Selecting features that do NOT intersect in PostGIS
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 18, 2022 at 21:38 | comment | added | RyanKDalton | @DPSSpatial_BoycottingGISSE This only works because you are choosing a single neighborhood polygon from "n", which is essentially removing the pair-wise comparison of multiple features in the source to multiple features in the destination | |
| Jan 5, 2018 at 17:16 | comment | added | Evan Carroll |
Here is an example WITH t(x) AS (VALUES (1),(2),(3),(4)) SELECT * FROM t AS t1 JOIN t AS t2 ON NOT t1.x = t2.x;
|
|
| Jan 5, 2018 at 17:10 | comment | added | Evan Carroll | This is what you want: gis.stackexchange.com/a/136177/6052 | |
| Jan 5, 2018 at 17:07 | comment | added | Evan Carroll | It means if you're not just getting 1 denver.address, you're getting one for every not-matching denver.neighborhood. | |
| Jan 5, 2018 at 16:46 | comment | added | Inactivated Account | @EvanCarroll what does that mean? | |
| Jan 3, 2018 at 2:05 | comment | added | Evan Carroll | This is actually a pretty bad idea because you're getting the cartesian product | |
| Sep 6, 2017 at 18:55 | history | edited | Inactivated Account | CC BY-SA 3.0 |
added 128 characters in body
|
| Jan 26, 2017 at 18:22 | comment | added | Inactivated Account | @NateWanner good to know! I can't believe how easy and fast that is!!! | |
| Jan 26, 2017 at 17:57 | comment | added | Nate Wanner | Also worked for "NOT ST_Within". My query completed in ~30.0 seconds for both the NOT ST_Within and using an outer join then checking for Null on the right side, so there doesn't seem to be any performance hit. Thanks! | |
| Jan 20, 2017 at 21:54 | history | answered | Inactivated Account | CC BY-SA 3.0 |