Opened 12 years ago
Closed 9 years ago
#319 closed defect (wontfix)
rasimport resets axis names after updating a cube
Reported by: | Owned by: | Alexander Herzig | |
---|---|---|---|
Priority: | major | Milestone: | 8.5.3 |
Component: | rasgeo | Version: | 8.5 |
Keywords: | rasimport, ps_domain | Cc: | Piero Campalani |
Complexity: | Medium |
Description
When having a cube with the third axis name = 't' and type = '6', rasimport seems to reset to the initial values "z" and "5" after updating the cube with a new slice.
Alex proposed to add a new parameter specifying registered axis names upon image import, e.g. '—axes <x:y:z>', and when data is updated names and types shouldn't be overwritten at all.
Change History (5)
comment:1 by , 12 years ago
Milestone: | 8.5 → 9.0 |
---|---|
Owner: | changed from | to
Status: | new → accepted |
comment:2 by , 12 years ago
I think this issue will be entirely obsoleted by 9.0 so it should belong either to 8.5 or be discarded entirely.
Meanwhile I have submitted a patch for 8.0-rc1 to avoid overwriting name and type upon update. This still requires manual update of the database after first insert but at least keeps existing name and type afterwards.
@Joachim: To be tested with rc2 or as soon as the patch is applied if you also build from git.
comment:4 by , 11 years ago
Cc: | added |
---|---|
Milestone: | 9.0 → 8.5.3 |
Version: | → 8.5 |
I think this should be fixed already and belongs only to 8.5 as said (9.0 uses secore for axis definition). It should be checked against 8.5.2 then closed if confirmed fixed or with release 8.5.3 if not confirmed existing.
comment:5 by , 9 years ago
Resolution: | → wontfix |
---|---|
Status: | accepted → closed |
I agree with Piero's suggestion to fix this in conjunction with the upcoming ps schema change in 9.0.