-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Selecting by Expression aborts with a minidump #22412
Comments
Author Name: Peter Cooper (@PeterC66) files keep not completing load, so I will do them individually. |
Author Name: Peter Cooper (@PeterC66) minidump "could not be saved" so I will try the shapefile - 2 of 4 elements.
|
Author Name: Peter Cooper (@PeterC66) Ignore files before. shapefile is now in zip.
|
Author Name: Anita Graser (@anitagraser)
|
Author Name: Anita Graser (@anitagraser)
|
Author Name: Nyall Dawson (@nyalldawson) No segfault here (Linux, using 2.14). Can you please test with 2.14 and also confirm your O/S?
|
Author Name: Peter Cooper (@PeterC66) I am using Windows 10. I can confirm there is no problem with QGIS 2.14. Thanks. Sorry - I should have tested with the latest version before logging the issue. I am using 2.8 for a reason relating to BoundlessGeo's OpenGeo plugin.
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Peter Cooper (@PeterC66)
Original Redmine Issue: 14433
Affected QGIS version: 2.8.3
Redmine category:unknown
I am processing a series of shapefiles (from OS Open Map - Local in the UK) using an expression (see below) to pick out a rectangle of features, so that I can Copy/Paste to new vector layers and concentrate on a small area around my village. Some work fine, but others cause QGIS to abort during the selection with a minidump (2 attached).
I suspect it might be because there were no features in the shapefile within the rectangle, because all the ones I expected to have features within the rectangle worked OK.
Expression used: (xmin($geometry) < 537114.565 and xmax($geometry)>532059.373) and (ymin($geometry) <274187.017 and ymax($geometry) >269687.748)
The text was updated successfully, but these errors were encountered: