Proposals:Writing DICOM from non-DICOM: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
No edit summary |
|||
| Line 3: | Line 3: | ||
= The Problem = | = The Problem = | ||
If we take a 3D image in ITK and pass it to the ImageSeriesWriter and set the ImageIO to be the GDCMImageIO class, the series | How to take a 3D image (not from DICOM) and write it as a series of DICOM files. | ||
= The current options = | |||
== Multi-Frame DICOM == | |||
If the image is passed to an ImageFileWriter and a GDCMImageIO is connected to it, then the image will be writen as a single DICOM file with a multi-frame content. | |||
== ImageSeriesWriter == | |||
If we take a 3D image in ITK and pass it to the ImageSeriesWriter and set the ImageIO to be the GDCMImageIO class, then the series will be written but they will all have the same DICOM header, and the third component of the origin and spacing will not be correct. | |||
= The Way it should behave = | = The Way it should behave = | ||
= Proposed solution= | = Proposed solution= | ||
Revision as of 00:43, 21 March 2006
The Problem
How to take a 3D image (not from DICOM) and write it as a series of DICOM files.
The current options
Multi-Frame DICOM
If the image is passed to an ImageFileWriter and a GDCMImageIO is connected to it, then the image will be writen as a single DICOM file with a multi-frame content.
ImageSeriesWriter
If we take a 3D image in ITK and pass it to the ImageSeriesWriter and set the ImageIO to be the GDCMImageIO class, then the series will be written but they will all have the same DICOM header, and the third component of the origin and spacing will not be correct.
