Re: dicom support

[Judd Storrs]

Resending because the attachments were too large and bounced.

2010/5/3 Judd Storrs <address@hidden>:
> On Mon, May 3, 2010 at 4:15 AM, Andy Buckle <address@hidden> wrote:
>> I wanted to avoid having to parse dictionary files. Though, as we will
>> need to do the lookup both ways, and don't want spaces and apostrophes
>> in the names, we may have to. GDCM seems to use something more complex
>> than just a single file for its dictionary.
>
> Since the gdcm developers intend to add keywords and keyword lookup in
> the future, we can just use a simple workaround for now.
>
> I made a simple bi-directional lookup table based on the dicom3tools
> dictionary as a bootstrap. This excludes the keywords that have
> multiple ids such as the overlays ((60xx,0100)  OverlayBitsAllocated).
> M does have these in its dictionary. I'll have to poke around and see
> how M handles these cases. Maybe it returns these as cell arrays or
> something. I don't think I have any DICOM files with these sorts of
> elements so I'll have to hunt a bit.
>
> When keywords become available within gdcm it should be
> straightforward to update that part.
>
>
> --judd
>

test.cxx
Description: Text Data

dicom3.h.gz
Description: GNU Zip compressed data