• Planar Configuration ((0028,0006)) - Usage with uncompressed images

    From kuldiprindani@gmail.com@21:1/5 to All on Thu Sep 23 09:22:00 2021
    We have a question regarding usage of tag PC (0028,0006) = 1 when images are uncompressed.

    from practical standpoint usefulness of this tag comes when compressing with RLE on multiple plane images otherwise it seems more of a bad data and extra cost during creation and display for compression other than RLE.

    while reading standard (section 8.2) it is correctly referenced to use with RLE on multi plane images (YBR & RGB) for other compression technique it is referenced as "0" but nothing specific is mention about it's usage on uncompressed images (ELE/EBE/ILE)
    .

    http://dicom.nema.org/medical/Dicom/2017c/output/chtml/part05/sect_8.2.2.html

    Can someone please add comment regarding there experience with uncompressed images with PC = 1 and insight into standard if I missed.

    and should a uncompressed image with PC=1 be treated as bad data or it is complaint per standard.

    Thanks,
    Kuldip

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From David Gobbi@21:1/5 to All on Thu Sep 23 11:16:57 2021
    Hi Kuldip, DICOM 2017c had mistakes in Table 8.2.2-1. For comparison, see the same table for 2021c:
    http://dicom.nema.org/medical/Dicom/2021c/output/chtml/part05/sect_8.2.2.html

    The up-to-date table correctly states that PlanarConfiguration can be either 0 or 1 for RLE.

    Because of the way that RLE breaks the Composite Pixel Code into byte-sized pieces for the segments (as described in Appendix G), it does not require the image to be planar.

    PlanarConfiguration can also be either 0 or 1 for uncompressed RGB/YBR images, there is nothing in the standard that says it
    isn't allowed. So planar, uncompressed data is compliant with the standard and software should accept it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From David Gobbi@21:1/5 to All on Thu Sep 23 12:08:30 2021
    Short addendum: I found the CP that changed Table 8.2.2.1, it was CP-1843 from 2019.

    After reading this CP, I must amend my statement above that "planar uncompressed data is compliant", since CP-1843 makes it clear that there are IODs that require PlanarConfiguration=0 for RGB: in particular, Enhanced Color MR, SC, WSI. But if not
    constrained by the IOD, PlanarConfiguration can be either 0 or 1 for uncompressed images.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From kuldiprindani@gmail.com@21:1/5 to david...@gmail.com on Fri Sep 24 06:34:47 2021
    On Thursday, September 23, 2021 at 2:08:32 PM UTC-5, david...@gmail.com wrote:
    Short addendum: I found the CP that changed Table 8.2.2.1, it was CP-1843 from 2019.

    After reading this CP, I must amend my statement above that "planar uncompressed data is compliant", since CP-1843 makes it clear that there are IODs that require PlanarConfiguration=0 for RGB: in particular, Enhanced Color MR, SC, WSI. But if not
    constrained by the IOD, PlanarConfiguration can be either 0 or 1 for uncompressed images.

    Thanks David for reply and reference to CP. It is helpful & clarifies confusion for us.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)