Opened 7 years ago
Closed 7 years ago
#1668 closed feature (fixed)
curtain queries
Reported by: | bbell | Owned by: | bbell |
---|---|---|---|
Priority: | major | Milestone: | 10.0 |
Component: | qlparser | Version: | development |
Keywords: | curtain, polygon, clip, select | Cc: | Dimitar Misev |
Complexity: | Medium |
Description
implement curtain rod type queries via rasql for line segments, linestrings, and polygons in 2D cross-sections.
the idea for now would be to have query options for:
select clip(curtain(c, range( arg ), polygon( arg )) from test_coll as c select clip(curtain(c, range( arg ), line( arg )) from test_coll as c select clip(curtain(c, range( arg ), linestring( arg )) from test_coll as c
Change History (3)
comment:1 by , 7 years ago
comment:3 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
updated syntax to:
select clip(c[], curtain(…))
and as such, should be closed
Note:
See TracTickets
for help on using tickets.
polygon curtains have been introduced for 3D datasets in community, and we will continue to expand upon it and modify the syntax
currently, you can do a polygon clipping on a 3D dataset by specifying the 2D slice you want it in, but a curtain by default (for now) uses the last 2 dimensions for the polygonal crossection, and the range argument is the limits of integration for the curtain. i.e.:
future modifications will include specifying the range subset via c[0:19,*,*] in the mddexp argument to simplify the syntax, and to permit selection of the crossectional dimensions automatically through the subsetting, as well.