Bug report #9887
Example script "Hex grid from layer bound" creates topologically incorrect grid
Status: | Closed | ||
---|---|---|---|
Priority: | Normal | ||
Assignee: | |||
Category: | Processing/QGIS | ||
Affected QGIS version: | 2.4.0 | Regression?: | No |
Operating System: | Easy fix?: | No | |
Pull Request or Patch supplied: | No | Resolution: | fixed/implemented |
Crashes QGIS or corrupts data: | No | Copied to github as #: | 18408 |
Description
I think the vertices of the polygons do not have have the exact same coordinates. I performed the following test:
1. Create the hex grid,
2. Run extract nodes
3. Try to remove duplicate geometries
almost no points were removed because they differed somewhere on the 8th decimal position.
History
#1
Updated by Alexander Bruy about 11 years ago
Just tested: extract nodes creates layer with 7980 features, after Delete duplicate geometries I have 2416 features
#2
Updated by Anita Graser about 11 years ago
Should probably mention that the layer CRS was WGS84.
#3
Updated by Anita Graser about 11 years ago
- Category set to 65
#4
Updated by Alexander Bruy over 10 years ago
- Status changed from Open to In Progress
- Category changed from 65 to 67
Bug is not in script itself, but in underlying mmqgisx algorithm
#5
Updated by Alexander Bruy over 10 years ago
- Status changed from In Progress to Feedback
Should be fixed in 558765addf. Please check
#6
Updated by Giovanni Manghi over 10 years ago
- Category deleted (
67) - Crashes QGIS or corrupts data set to No
- Affected QGIS version set to 2.4.0
- Project changed from 78 to QGIS Application
#7
Updated by Giovanni Manghi over 10 years ago
- Category set to Field calculator
#8
Updated by Giovanni Manghi over 10 years ago
- Assignee set to Victor Olaya
#9
Updated by Alexander Bruy over 10 years ago
- Category changed from Field calculator to Processing/QGIS
#10
Updated by Giovanni Manghi over 10 years ago
- Resolution set to fixed/implemented
- Status changed from Feedback to Closed