Re: [Gdcm2] Which SOP Class UID to choose
Cross-platform DICOM implementation
Brought to you by:
malat
|
From: Mathieu M. <mat...@gm...> - 2017-08-23 15:57:08
|
Florent, On Tue, Aug 22, 2017 at 6:49 PM, <k3...@fr...> wrote: > Hi, > > I want to generate a new DICOM series, derived from a MR Image Storage series, with rescale intercept/slope information. I guess this is your specification (a bit broad IMHO). > Which SOP Class UID should I use? Are you looking for 100% DICOM conformance ? If so you could use CT Image Storage :) if your sole requirement is a SOP Class with Rescale Intercept/Slope. > Does it make sense that GDCM doesn't apply rescale information when SOP_CLASS_UID = 1.2.840.10008.5.1.4.1.1.7 (Secondary Capture Image Storage). uh ? GDCM does consider Rescale Intercept/Slope for legacy SC Image Storage. Just use gdcminfo to convince yourself. > I am using VV (https://www.creatis.insa-lyon.fr/rio/vv) which is using GDCM for loading DICOM series, for viewing the generated series and it seems that the rescale information is not used to get me the correct pixel values... Well, technically you are missing the important piece here. VV is using itk::GDCMImageIO. In a previous thread you mentionned some issue with it. > Thanks, Here is my 2cts, if this is a new project you should really take the time to consider the different SOP Class. In particular Parametric Map offer the closest representation of NifTi (not supported by GDCM for now). If you are looking for compatibility with legacy software then MR Image Storage may be of use, since at least Philips equipement can be convinced that Rescale Intercept/Slope makes sense. If you are looking for keeping the MR specific information, then have a look at Enhanced MR Image Storage (supported by GDCM for ITK-style volume). Cheers Ps: CT Image Storage was simply a joke... |