1. Summary of problem description

1.1. Actual behavior

mitk::Image::Initialize(vtkImageData* vtkimagedata) always initializes the origin as (0,0,0) independent of the actual value of the origin of the vtkImageData.

1.2. Expected behavior

mitk::Image::Initialize(vtkImageData* vtkimagedata) should initialize the origin to (0,0,0) the origin of the mitk::Image according to the origin of the vtkImageData.

2. Cause of the bug

Missing initialization of the origin of the slicedGeometry.

3. Proposed solution

Do the initialization of the origin of the slicedGeometry. See patch attached to bug.

4. Affected classes

mitkImage.cpp

5. How will the bugfix get tested?

Additional test code in mitkImageTest.cpp. See patch attached to bug.