#1837 closed enhancement (wontfix)
Petascope_No need to send rasql to get sdom() for clipped output's domain if possible
| Reported by: | Bang Pham Huu | Owned by: | Bang Pham Huu |
|---|---|---|---|
| Priority: | major | Milestone: | 9.7 |
| Component: | petascope | Version: | development |
| Keywords: | Cc: | Dimitar Misev, Vlad Merticariu | |
| Complexity: | Medium |
Description
Current, when doing clipping, Petascope needs to send 2 rasql queries (1 for the sdom() of the clipped output and 1 for the real data encoded of the clipped output).
From Brennan's suggestion, it seems it could be done easily inside Petascope (especially Linestring with Bresenham's formula) so this should be improved.
Change History (7)
follow-up: 2 comment:1 by , 6 years ago
| Cc: | removed |
|---|
comment:2 by , 6 years ago
Replying to dmisev:
Why does petascope need the sdom of Linestring result before the Linestring can be evaluated by rasdaman?
It needs to update WCPS coverage’s axes grid domains, especially when encoding as GML.
comment:3 by , 6 years ago
Sure, but does it have to do this _before_ executing the actual rasql query?
follow-up: 6 comment:5 by , 6 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Ok in my opinion this needs to be fixed in rasdaman (the sdom query should be fast to execute). So nothing to do in petascope, it would be unnecessary duplication to reimplement Linestring.
comment:6 by , 6 years ago
Replying to dmisev:
Ok in my opinion this needs to be fixed in rasdaman (the sdom query should be fast to execute). So nothing to do in petascope, it would be unnecessary duplication to reimplement Linestring.
Note: it is the sdom(of clipped (c, linestring)) not sdom(of c), so it cannot be really fast.
Why does petascope need the sdom of Linestring result before the Linestring can be evaluated by rasdaman?