Skip to content
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

Closed
qgib opened this issue Feb 6, 2019 · 19 comments
Closed

Indexing data takes a very long time #29007

qgib opened this issue Feb 6, 2019 · 19 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption Digitizing Related to feature digitizing map tools or functionality High Priority Regression Something which used to work, but doesn't anymore

Comments

@qgib
Copy link
Contributor

qgib commented Feb 6, 2019

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.

@qgib
Copy link
Contributor Author

qgib commented Feb 7, 2019

Author Name: Giovanni Manghi (@gioman)


can you attach a sample project with data?


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Feb 7, 2019

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.

@qgib
Copy link
Contributor Author

qgib commented Feb 8, 2019

Author Name: Giovanni Manghi (@gioman)


Alexey T wrote:

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.

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?
can we download this dataset somewhere?


  • category_id was changed from Editing to Digitising

@qgib
Copy link
Contributor Author

qgib commented Feb 8, 2019

Author Name: Alexey T (@Xeenych)


Yes, vector lines.
Here is the dataset. 4 Gb zipped.
https://yadi.sk/d/aR605PsV-vrp2A

@qgib
Copy link
Contributor Author

qgib commented Feb 11, 2019

Author Name: Giovanni Manghi (@gioman)


Alexey T wrote:

Yes, vector lines.
Here is the dataset. 4 Gb zipped.
https://yadi.sk/d/aR605PsV-vrp2A

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?

@qgib
Copy link
Contributor Author

qgib commented Feb 11, 2019

Author Name: Alexey T (@Xeenych)


No, I didn't

@qgib
Copy link
Contributor Author

qgib commented Feb 11, 2019

Author Name: Alexey T (@Xeenych)


Snapping shold be enabled.

@qgib
Copy link
Contributor Author

qgib commented Feb 11, 2019

Author Name: Alexey T (@Xeenych)


Take a look at this video
https://yadi.sk/i/-b6yBfba3W967A

@qgib
Copy link
Contributor Author

qgib commented Feb 11, 2019

Author Name: Giovanni Manghi (@gioman)


Alexey T wrote:

Snapping shold be enabled.

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?

@qgib
Copy link
Contributor Author

qgib commented Feb 11, 2019

Author Name: Giovanni Manghi (@gioman)


Alexey T wrote:

Take a look at this video
https://yadi.sk/i/-b6yBfba3W967A

sorry seen this clink only after my last comment.

@qgib
Copy link
Contributor Author

qgib commented Feb 11, 2019

Author Name: Giovanni Manghi (@gioman)


Alexey T wrote:

Take a look at this video
https://yadi.sk/i/-b6yBfba3W967A

ok I replicated, it indeed eats up all memory and eventually will crashes.

Did it worked better on 2.18?


  • priority_id was changed from Normal to High
  • crashes_corrupts_data was changed from 0 to 1
  • status_id was changed from Feedback to Open

@qgib
Copy link
Contributor Author

qgib commented Feb 11, 2019

Author Name: Giovanni Manghi (@gioman)


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Feb 11, 2019

Author Name: Giovanni Manghi (@gioman)


Did it worked better on 2.18?

I answer myself: yes. No such issue on 2.18.


  • status_id was changed from Feedback to Open
  • regression was changed from 0 to 1

@qgib
Copy link
Contributor Author

qgib commented Feb 12, 2019

Author Name: Loïc BARTOLETTI (@lbartoletti)


Can you try to enable the option "Settings->Options->Digitizing->Enable snapping on invisible features" and restart QGIS ?

@qgib
Copy link
Contributor Author

qgib commented Feb 12, 2019

Author Name: Giovanni Manghi (@gioman)


Loïc BARTOLETTI wrote:

Can you try to enable the option "Settings->Options->Digitizing->Enable snapping on invisible features" and restart QGIS ?

it does not make any difference.

@qgib
Copy link
Contributor Author

qgib commented Feb 13, 2019

Author Name: Giovanni Manghi (@gioman)


There have been a update of the linspatialindex library in osgeo4w, and now this problem is gone.


  • resolution was changed from to fixed/implemented
  • status_id was changed from Open to Closed

@qgib qgib closed this as completed Feb 13, 2019
@qgib
Copy link
Contributor Author

qgib commented Feb 13, 2019

Author Name: Alexey T (@Xeenych)


In what version will it be fixed?

@qgib
Copy link
Contributor Author

qgib commented Feb 13, 2019

Author Name: Giovanni Manghi (@gioman)


Alexey T wrote:

In what version will it be fixed?

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).

@qgib
Copy link
Contributor Author

qgib commented Feb 13, 2019

Author Name: Jürgen Fischer (@jef-n)


Giovanni Manghi 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).

The standalones are regularly only updated after releases.

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority Digitizing Related to feature digitizing map tools or functionality Crash/Data Corruption Regression Something which used to work, but doesn't anymore labels May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption Digitizing Related to feature digitizing map tools or functionality High Priority Regression Something which used to work, but doesn't anymore
Projects
None yet
Development

No branches or pull requests

1 participant