[Insight-users] GDCMImageIO vs. DicomImageIO when reading HeaderEntry 6000|3000

[Mathieu Malaterre]

I believe this is due to a 'feature' in itk::GDCMImageIO, see documentation:

 *           -  Some very long (>0xfff) binary fields are not loaded
(typically 0029|0010),
 *              you need to explicitely set the maximum length of
elements to load to be bigger
 *              (see Get/SetMaxSizeLoadEntry)

Let us know if this fixes your issue.

Thanks,

On Fri, Aug 7, 2009 at 11:03 AM, Robert Haase<robert_haase at gmx.de> wrote:
> Dear ITK Users,
>
> I'm trying to read out DICOM-Header-Entries to draw Overlay-Objects above
> CT Images. When I use GDCMImageIO the MetaDataDictionary does not contain
> entry 6000|3000 (Overlay Data). When I use DicomImageIO the
> MetaDataDictionary contains my entry of interest but it displays an ugly
> error message telling me, I should use GDCMImageIO.
>
> Is there a possibility to read out 6000|3000 using GDCMImageIO? Or is
> there another way to get the Overlay data?
>
> Thanks a lot in advance,
> Robert
>
> --
> GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
> _____________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ITK FAQ at: http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-users
>



-- 
Mathieu
http://mathieumalaterre.com