Opened 8 years ago
Closed 7 years ago
#1568 closed enhancement (fixed)
implement polygon clipping
Reported by: | bbell | Owned by: | bbell |
---|---|---|---|
Priority: | major | Milestone: | 9.5 |
Component: | qlparser | Version: | development |
Keywords: | polygon, clipping | Cc: | Dimitar Misev, Vlad Merticariu, Peter Baumann |
Complexity: | Hard |
Description (last modified by )
following the work performed in D399, one should implement the polygon clipping methods in 2-D and 3-D and make any obvious improvements possible to the existing code (in particular, this means reducing present code redundancy).
system tests should be developed for polygon clipping in the following cases:
2D — convex, concave, self-intersecting, vertex revisited, collinear
3D — ", not coplanar
and exceptions should be thrown where the queries are not working/implemented.
Furthermore, it's worth thinking about how polygons are specified in rasql. Currently, D399 implements a simple representation of [x1,y1,x2,y2,x3,y3]
(x/y[/z]
coordinates of each polygon vertex are enumerated as one long list). Instead we could adopt WKT syntax, e.g. POLYGON ((x1 y1, x2 y2, x3 y3)), or something else more appropriate.
Change History (6)
comment:1 by , 8 years ago
Description: | modified (diff) |
---|
comment:2 by , 8 years ago
Description: | modified (diff) |
---|---|
Milestone: | 10.0 → 9.5 |
comment:3 by , 8 years ago
Cc: | added |
---|
comment:4 by , 8 years ago
Description: | modified (diff) |
---|
comment:5 by , 7 years ago
comment:6 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
@bbell: please open a new ticket for interiors.
still needs polygonal interiors from WKT polygons, otherwise this is basically done.