New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ST_Intersects takes too long time #672
Comments
Can you post the WKT of STUDY.the_geom ? |
I upload the shape file instead, because the WKT is too long for GitHub |
You test geometry is composed by 31789 points. That explains the query time. |
In order to optimize this, I would go for a st_polygonize. |
Yes this geometry is complex (even if it's a simple geometry and there is no hole), but this kind of process used to works well in the past. I'll try ST_Polygonize |
Sorry I was talking about tessellate create table studypol as select * from st_explode('select ST_TESSELLATE(the_geom) the_geom from study'); |
then use spatial index on studypol |
Thanks @nicolas-f it works. The process takes 47s but I have a result ! |
I'm curious to know how many times PostGIS require to do intersection with a 31789 points geometry and thousands of buildings. |
No result with QGis after 10mn (QGis freezed). |
Tested on a local postgis server, this is the same pb |
... and same with spatial indexes on QGis --> freeze |
Solved ? |
Yes we can close |
I'm using the last realease of OrbisGIS.
I'm trying to select buildings from the departement 56 (table "BATI_INDIFFERENCIE") which intersects the agglomeration of Vannes.
So I created a unique polygon that represent my study area (table STUDY).
Then I created spatial indexes on both tables.
Now, I execute the following SQL instruction
The process is really too long (no result after 5mn).
I tried with or without spatial index on both tables, but the result is the same
@ebocher @nicolas-f
The text was updated successfully, but these errors were encountered: