Opened 9 years ago
Closed 6 years ago
#913 closed defect (fixed)
Move coverage's grid origin when domain is extended
| Reported by: | Vlad Merticariu | Owned by: | Vlad Merticariu |
|---|---|---|---|
| Priority: | major | Milestone: | 9.7 |
| Component: | petascope | Version: | development |
| Keywords: | Cc: | ||
| Complexity: | Medium |
Description
Right now a coverage's grid origin is in O (0 on every dimension). However, when a coverage is extended, the new information might be added at negative axis coordinates (e.g. adding a slice at the bottom of a time-series cube).
In this case the grid origin should be changed to reflect the new corner point.
Change History (6)
comment:1 by , 9 years ago
| Milestone: | → 9.2 |
|---|
comment:2 by , 7 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 7 years ago
No, not in its current form. In the meanwhile I have seen several arguments for which it makes sense to have the origin pointing to 0,0.
If this is not ok for GIS people, we can do something about it at retrieval. But for us, internally, it makes sense for the origin to give us the geo-coordinates of 0,0.. as we work in ND.
comment:5 by , 7 years ago
| Milestone: | 9.2 → Future |
|---|
comment:6 by , 6 years ago
| Milestone: | Future → 9.7 |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
It has been fixed quite a while, consider the effect on this ticket http://rasdaman.org/ticket/1789.
Is this ticket still valid?