Timeline for Use area of intersection as a variable in PostGIS
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 16, 2017 at 22:30 | history | edited | Jakub Kania | CC BY-SA 3.0 |
deleted 59 characters in body
|
| May 16, 2017 at 22:29 | comment | added | Jakub Kania |
@EvanCarroll You may be right about the explicity, though ST_Touches requires another function call while this only reuses what's already there. Though with Sum() it doesn't really matter...I'll guess I'll remove it.
|
|
| May 16, 2017 at 22:22 | comment | added | Evan Carroll |
you're right to say that. ST_Intersects will return true if they ST_Touches. Though I would write that as not ST_Touches() or something more explicit.
|
|
| May 16, 2017 at 22:19 | comment | added | Jakub Kania | @EvanCarroll Well, I just simplified the original query. TBH I haven't used postgis in a bit and I'm not really sure if intersection always has an area greater than zero | |
| May 16, 2017 at 22:07 | comment | added | Evan Carroll |
I'm still not sure what that does. You're just writing another slower version of ST_Intersects that you already have.
|
|
| May 16, 2017 at 22:06 | history | edited | Jakub Kania | CC BY-SA 3.0 |
edited body
|
| May 16, 2017 at 21:58 | comment | added | Evan Carroll |
I don't understand what this clause >0 is supposed to do with ST_Intersection(t.geom,m.geom) > 0`
|
|
| May 16, 2017 at 19:30 | history | answered | Jakub Kania | CC BY-SA 3.0 |