Slicer DICOM Scalar volume plugin relies on (old) GDCM: why do we not use DCMTK?

[thewtex (Matt McCormick)]

@jcfr

done before the ITK reader is instantiated

May this could be added to ITK … in that case a list of readers could be returned. @thewtex Do you think that make sense or should Slicer team proceed as described ?

I think the issue of improving ITK is an important, but a separate one. I would prefer not to wait for the ITK improvements to be developed, tested and integrated to resolve this specific issue, unless there are really good reasons.

Yes, I think it is a idea to have the DICOM image type code available in ITK without duplication, but it should not be a blocker to move forward. Could an issue please be created here:

GitHub - KitwareMedical/ITKDICOM: Better support for DICOM in ITK.

that points to the appropriate code as a reference?

The overall plan sounds good

Worth noting, @pieper did some digging the other week and found these DICOM datasets from GDCM:

Grassroots DICOM / Gdcmdata / [a0bba5]

These are a good resource for regression testing.