#728 closed defect (fixed)
GEOSDelaunayTriangulation() utterly slow on big point cloud (133 000 points)
Reported by: | rouault | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 3.5.1 |
Component: | Default | Version: | 3.4.2 |
Severity: | Unassigned | Keywords: | |
Cc: | dbaston |
Description
GEOSDelaunayTriangulation() doesn't complete in a reasonable time (I stopped it after ~ 15 minutes) when run on the multipoint aggregating all the points of the attashed shapefile. On the contrary,QHull Delaunay triangulation completes in less than one second.
Change History (13)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Summary: | GEOSDelaunayTriangulation() utterly slow on cloud → GEOSDelaunayTriangulation() utterly slow on big point cloud (133 000 points) |
---|
comment:3 by , 9 years ago
There are 3 dimensions in the shapefile. Using two dimensions only, R deldir::deldir completes in 444 seconds on my laptop, but does this make sense, given that the points are in geographical coordinates? Does Qhull use GC distances - I don't think so, nor does GEOS - is this just a test case?
> bbox(out) min max coords.x1 145.77283 216.073340 coords.x2 -78.36998 -7.316789 coords.x3 -4.00000 10632.000000
comment:4 by , 9 years ago
Possible explanation: https://github.com/postgis/postgis/pull/73#issuecomment-158551270
comment:5 by , 9 years ago
Cc: | added |
---|
comment:11 by , 6 years ago
Milestone: | 3.6.3 → 3.8.0 |
---|
comment:12 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I'm pretty confident this was resolved by the linked pull request.
comment:13 by , 6 years ago
Milestone: | 3.8.0 → 3.5.1 |
---|
Link is http://even.rouault.free.fr/delaunay_input.shp.zip