Currently saving images as VTI does not work correctly.
Origin and directions are not correctly stored. (Always 0,0,0 and Identity).
Reason is that the mitk::Image::GetVtkImageData() method drops the information in the returning vtkImage.
Bug would be fixed if T5050 is fixed.
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Wontfix | None | T19092 Saving as VTI results in incorrect image origin and directions | ||
| Wontfix | None | T5050 Bug in mitk::Image::GetVtkImageData(), Origin is wrong | ||
| Wontfix | None | T18658 Ensure that the vtk origin is considered everywhere | ||
| Wontfix | None | T24071 Revisit 2-d image rendering | ||
| Wontfix | None | T17812 SlicedGeometry3D initialisation fix for non-image geometries | ||
| Resolved | kislinsk | T20204 Provide public getter for reference geometry of sliced geometries | ||
| Resolved | kislinsk | T20217 Equality checks when setting data storage for renderers | ||
| Resolved | kislinsk | T20218 DataStorage::ComputeBoundingBox3D creates geometry with incorrect origin and bounding box | ||
| Wontfix | kislinsk | T24080 Write visual debugging utilitiy for inspecting geometries |
Hi there! 🙂
This task was auto-closed according to our Task Lifecycle Management.
Please follow this link for more information and don't forget that you are encouraged to reasonable re-open tasks to revive them. 🚑
Best wishes,
The MITK devs