-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Indexing data takes a very long time #29007
Comments
Author Name: Giovanni Manghi (@gioman) can you attach a sample project with data?
|
Author Name: Alexey T (@Xeenych) It is 8 Gb of DEM data in shapefiles. Snapping should be enabled. When you try to edit it, QGIS indexes it and consumes 19Gb of RAM. |
Author Name: Giovanni Manghi (@gioman) Alexey T wrote:
a DEM is usually a raster map, in this case I guess you refer to a line vector map where lines represent the same terrain height, correct?
|
Author Name: Alexey T (@Xeenych) Yes, vector lines. |
Author Name: Giovanni Manghi (@gioman) Alexey T wrote:
the dataset is split in several "small" shapes. I don't have any issues while editing any of them. Did you merged those shapes in one unique vector? |
Author Name: Alexey T (@Xeenych) No, I didn't |
Author Name: Alexey T (@Xeenych) Snapping shold be enabled. |
Author Name: Alexey T (@Xeenych) Take a look at this video |
Author Name: Giovanni Manghi (@gioman) Alexey T wrote:
I'm trying with one of those shapes (a 250MB one) with snapping enabled and I don't particular issues to edit on 3.4.4 (but it seems there is a regression on master). What are the exact steps to follow to replicate the problem? |
Author Name: Giovanni Manghi (@gioman) Alexey T wrote:
sorry seen this clink only after my last comment. |
Author Name: Giovanni Manghi (@gioman) Alexey T wrote:
ok I replicated, it indeed eats up all memory and eventually will crashes. Did it worked better on 2.18?
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
I answer myself: yes. No such issue on 2.18.
|
Author Name: Loïc BARTOLETTI (@lbartoletti) Can you try to enable the option "Settings->Options->Digitizing->Enable snapping on invisible features" and restart QGIS ? |
Author Name: Giovanni Manghi (@gioman) Loïc BARTOLETTI wrote:
it does not make any difference. |
Author Name: Giovanni Manghi (@gioman) There have been a update of the linspatialindex library in osgeo4w, and now this problem is gone.
|
Author Name: Alexey T (@Xeenych) In what version will it be fixed? |
Author Name: Giovanni Manghi (@gioman) Alexey T wrote:
it is already fixed if you use the osgeo4w installer, if not yo will need to wait for the next build of the standalone installer (not sure if it was generated one in the last hours). |
Author Name: Jürgen Fischer (@jef-n) Giovanni Manghi wrote:
The standalones are regularly only updated after releases. |
Author Name: Alexey T (@Xeenych)
Original Redmine Issue: 21189
Affected QGIS version: 3.4.4
Redmine category:digitising
I have a large project with vector DEM loaded.
When I try to edit any feature QGis starts indexing data.
First, it takes a veeery long time to index.
Second, it takes more than 8 Gigs of RAM.
Looks like QGis indexes the whole project. I believe it is sufficient to index only the canvas.
The text was updated successfully, but these errors were encountered: