[vtkusers] vtkDICOMImageReader does not support to read all Dicom image format

[Matias Montroull]

Ravi,

I only use VTK to do 3D renders of Dicom Series, not for MPR..

I use Fo-Dicom for Axial, Coronal and Saggital and I've built my own method
to get the bitmaps for each slice view.

I'm not sure if you can convet slice images into bitmap with VTK (it would
be nice to know how though), I haven't tried that, maybe someone else in
this group did and can help.

Regards,

Matias.

On Wed, Feb 25, 2015 at 9:56 AM, Ravi HM <Ravi.HM at lnttechservices.com>
wrote:

>  Hi Matias,
>
>
>
> I am using VTK + C# wrapper to re-slice the Dicom image into axial coronal
> or sagittal.
>
>
>
> Reader is: vtkDicomImageReader
>
> To Slice: vtkImageReSlice
>
> Viewer is: vtkImagViewr2
>
>
>
> My doubt is can I convert the slice image to bitmap.
>
>
>
> Regards,
>
> Ravi
>
>
>
>
>
> *From:* Matias Montroull [mailto:matimontg at gmail.com]
> *Sent:* Wednesday, February 25, 2015 6:01 PM
> *To:* Ravi HM; vtkusers at vtk.org
>
> *Subject:* Re: [vtkusers] vtkDICOMImageReader does not support to read
> all Dicom image format
>
>
>
> You can use command line tool to dump this type of information, eg
> gdcminfo:
>
> $ gdcminfo 012345.002.050.dcm
>
> MediaStorage is 1.2.840.10008.5.1.4.1.1.4 [MR Image Storage]
>
> TransferSyntax is 1.2.840.10008.1.2.4.70 [JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value 1]): Default Transfer Syntax for Lossless JPEG Image Compression]
>
> ...
>
>  Pay attention that for the case of JPEG 2000 and JPEG-LS the transfer
> syntax itself is not sufficient to indicate whether or not the Pixel Data
> stream has been lossy or lossless compressed. This could be important for
> your organisation as lossy compression could impact professional
> interpretation.
>
> Ref: http://gdcm.sourceforge.net/html/gdcminfo.html
>
>
>
> On Wed, Feb 25, 2015 at 8:59 AM, Ravi HM <Ravi.HM at lnttechservices.com>
> wrote:
>
>  Hi Matias,
>
>
>
> Thank you for your kind support.
>
>
>
> Regards,
>
> Ravi
>
>
>
> *From:* Matias Montroull [mailto:matimontg at gmail.com]
> *Sent:* Wednesday, February 25, 2015 5:21 PM
> *To:* Ravi HM
> *Cc:* vtkusers at vtk.org
>
> *Subject:* RE: [vtkusers] vtkDICOMImageReader does not support to read
> all Dicom image format
>
>
>
> There is a way to identify compressed images yes I will have to look. I
> use Fo-Dicom not gdcm but I know there are methods to determine when an
> image is compressed.
>
> On Feb 25, 2015 8:46 AM, "Ravi HM" <Ravi.HM at lnttechservices.com> wrote:
>
>  Hi Matias,
>
>
>
> Yep, it would be nice if this feature is added.
>
>
>
> Is there any Dicom TAG to identify uncompressed Dicom image using GDCM or
> RZDCX
>
>
>
> Regards,
>
> Ravi
>
>
>
> *From:* Matias Montroull [mailto:matimontg at gmail.com]
> *Sent:* Wednesday, February 25, 2015 4:59 PM
> *To:* Ravi HM
> *Cc:* insight-users at itk.org Users
> *Subject:* RE: [vtkusers] vtkDICOMImageReader does not support to read
> all Dicom image format
>
>
>
> Oh you are right.
> I uncompress the images before passing to VTK.
> It would be nice to add this feature in future releases of VTK.
> Matias.
>
> On Feb 25, 2015 1:44 AM, "Ravi HM" <Ravi.HM at lnttechservices.com> wrote:
>
>  Hi Matias,
>
>
>
> vtkDicomImageReader supports to read only uncompressed Dicom image.
>
>
>
> When any Dicom image is compressed (Compressed in any format)
> vtkDicomImageReader doesn’t support.
>
>
>
> Regards,
>
> Ravi
>
>
>
> *From:* Matias Montroull [mailto:matimontg at gmail.com]
> *Sent:* Tuesday, February 24, 2015 7:54 PM
> *To:* Ravi HM
> *Cc:* vtkusers at vtk.org
> *Subject:* Re: [vtkusers] vtkDICOMImageReader does not support to read
> all Dicom image format
>
>
>
> Hi Ravi, which DICOM formats / Pixel Type does not support?
>
>
>
> On Tue, Feb 24, 2015 at 2:29 AM, Ravi HM <Ravi.HM at lnttechservices.com>
> wrote:
>
>  Hi All,
>
>
>
> Why vtkDICOMImageReader does not support to read all Dicom image format.
>
>
>
> Regards,
>
> Ravi
>
>
>
> *L&T Technology Services Ltd*
>
> www.LntTechservices.com <http://www.lnttechservices.com/>
>
> This Email may contain confidential or privileged information for the
> intended recipient (s). If you are not the intended recipient, please do
> not use or disseminate the information, notify the sender and delete it
> from your system.
>
>
> _______________________________________________
> 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 VTK FAQ at:
> http://www.vtk.org/Wiki/VTK_FAQ
>
> Search the list archives at: http://markmail.org/search/?q=vtkusers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/vtkusers
>
>
>
> *L&T Technology Services Ltd*
>
> www.LntTechservices.com <http://www.lnttechservices.com/>
>
> This Email may contain confidential or privileged information for the
> intended recipient (s). If you are not the intended recipient, please do
> not use or disseminate the information, notify the sender and delete it
> from your system.
>
>  *L&T Technology Services Ltd*
>
> www.LntTechservices.com <http://www.lnttechservices.com/>
>
> This Email may contain confidential or privileged information for the
> intended recipient (s). If you are not the intended recipient, please do
> not use or disseminate the information, notify the sender and delete it
> from your system.
>
>    *L&T Technology Services Ltd*
>
> www.LntTechservices.com <http://www.lnttechservices.com/>
>
> This Email may contain confidential or privileged information for the
> intended recipient (s). If you are not the intended recipient, please do
> not use or disseminate the information, notify the sender and delete it
> from your system.
>
>
>
> *L&T Technology Services Ltd*
>
> www.LntTechservices.com <http://www.lnttechservices.com/>
>
> This Email may contain confidential or privileged information for the
> intended recipient (s). If you are not the intended recipient, please do
> not use or disseminate the information, notify the sender and delete it
> from your system.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtkusers/attachments/20150225/d4361425/attachment.html>