Timeline for Acquiring ArcGIS-like speed in Postgis
Current License: CC BY-SA 3.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 16, 2012 at 6:22 | vote | accept | THX1138 | ||
| Aug 15, 2012 at 20:46 | history | edited | underdark |
edited tags
|
|
| Aug 15, 2012 at 20:43 | answer | added | Paul Ramsey | timeline score: 99 | |
| Aug 15, 2012 at 5:38 | answer | added | vinayan | timeline score: 4 | |
| Aug 13, 2012 at 15:40 | comment | added | THX1138 | @NicklasAvén Yes, I included the links to the exact datasets I used in the post | |
| Aug 13, 2012 at 11:13 | comment | added | Nicklas Avén | Is it possible to get the data sets to take a look at it? | |
| Aug 13, 2012 at 4:36 | comment | added | Nicklas Avén | you should also be aware that you are running different data sets on postgis vs arcgis since you say that you neex to make them valid to be accepted vy postgis. | |
| Aug 13, 2012 at 4:33 | comment | added | Nicklas Avén | It is still very difficult to say whaat is happening. Your numbers about the daata sets does not say very much becauase the effort needed depends on how many polygon-polygon combinations that passes the st_intersects filter to get computes by st_intersection. | |
| Aug 12, 2012 at 4:13 | comment | added | THX1138 | @NathanW Explain Analyze results are added to post now. | |
| Aug 12, 2012 at 4:12 | history | edited | THX1138 | CC BY-SA 3.0 |
added 186 characters in body
|
| Aug 12, 2012 at 3:07 | history | edited | THX1138 | CC BY-SA 3.0 |
added 1 characters in body
|
| Aug 12, 2012 at 2:51 | history | tweeted | twitter.com/#!/StackGIS/status/234482216799981568 | ||
| Aug 12, 2012 at 1:10 | comment | added | Nathan W | Can you run you query using EXPLAIN ANALYZE and post the results | |
| Aug 11, 2012 at 23:14 | comment | added | THX1138 | st_intersects() includes a bounding box query before performing any intersection testing in postgis 2.x so unfortunately that won't save any time. | |
| Aug 11, 2012 at 22:44 | comment | added | Sean | It's a common idiom in PostGIS to add a bounding box intersection check to speed things up. Try adding 'AND a.geom && b.geom' to your WHERE clause and see how much of a difference it makes. | |
| Aug 11, 2012 at 22:14 | history | edited | THX1138 | CC BY-SA 3.0 |
added 142 characters in body
|
| Aug 11, 2012 at 21:59 | history | asked | THX1138 | CC BY-SA 3.0 |