KWScene/Documentation/Supported Generators/ITK/Image: Difference between revisions
From KitwarePublic
< KWScene | Documentation | Supported Generators | ITK
Jump to navigationJump to search
Line 36: | Line 36: | ||
* Create a KWScene hierarchy where FactoryBasedImageGenerator handles all relevant file formats. | * Create a KWScene hierarchy where FactoryBasedImageGenerator handles all relevant file formats. | ||
* Will have classes | * Will have classes | ||
** | ** FactoryBasedImage-KWSGenerator, which can generate either | ||
** an image of most single-file types via itk::ImageIOFactory or | ** an image of most single-file types via itk::ImageIOFactory or | ||
** an Image Series via itk::GDCMImageIO. | ** an Image Series via itk::GDCMImageIO. |
Latest revision as of 19:32, 22 April 2010
Desired Format Support
- DICOM (.dcm)
- Analyze (.hdr/.ima)
- XML (.vti)
- MetaImage (.mha)
Class Diagrams
Options
Option A
- Create a KWScene hierarchy where FactoryBasedImageGenerator handles all relevant file formats.
- Will have classes
- FactoryBasedImage-KWSGenerator, which can generate either
- an image of most single-file types via itk::ImageIOFactory or
- an Image Series via itk::GDCMImageIO.
- because of the breadth and reliability of ImageIOFactory.
- ImageNodeGenerator is the base class here, to be consistent with nomenclature in VTK.
Proposed Hierarchy