Opened 2 years ago

Last modified 4 months ago

#913 assigned defect

Move coverage's grid origin when domain is extended

Reported by: vmerticariu Owned by: vmerticariu
Priority: major Milestone: Future
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 (5)

comment:1 Changed 23 months ago by dmisev

  • Milestone set to 9.2

comment:2 Changed 6 months ago by dmisev

  • Owner changed from vmerticariu to bphamhuu
  • Status changed from new to assigned

Is this ticket still valid?

comment:3 Changed 6 months ago by vmerticariu

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:4 Changed 6 months ago by bphamhuu

  • Owner changed from bphamhuu to vmerticariu

back to Vlad as this ticket seems for E version.

comment:5 Changed 4 months ago by dmisev

  • Milestone changed from 9.2 to Future
Note: See TracTickets for help on using tickets.