Mercurial > hg > orthanc-book
changeset 657:566f0af3e4ed
dicom-sr
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Wed, 28 Apr 2021 18:02:04 +0200 |
parents | 55a93745e874 |
children | f7f90282ea1e |
files | Sphinx/source/faq/supported-images.rst |
diffstat | 1 files changed, 14 insertions(+), 7 deletions(-) [+] |
line wrap: on
line diff
--- a/Sphinx/source/faq/supported-images.rst Wed Apr 28 16:16:33 2021 +0200 +++ b/Sphinx/source/faq/supported-images.rst Wed Apr 28 18:02:04 2021 +0200 @@ -10,13 +10,19 @@ <configuration>` can be set to `true` if interfacing with modalities that are producing non-standard SOP classes. -Orthanc Explorer can **display the raw DICOM tags** of any such DICOM -file (including notably DICOM-SR structured reports). +Orthanc Explorer can also **display the raw DICOM tags** of any such +DICOM file. -However, the core engine of Orthanc is not able to **render all of the -DICOM files as PNG images**. An image that Orthanc cannot decode is -displayed as "Unsupported" by clicking on the "Preview" buttons of -Orthanc Explorer. Currently, the core engine of Orthanc can decode: +For instance, **DICOM-SR and DICOM-RT** instances are supported by +Orthanc, i.e. such file can be received/stored/retransmitted with +Orthanc. However, if you need to analyze/create such files, you will +have to resort on another specialized tool. + +As far as pixel data is concerned, the core engine of Orthanc is **not +able to render all of the DICOM instances as PNG images**. An image +that Orthanc cannot decode is displayed as "Unsupported" by clicking +on the "Preview" buttons of Orthanc Explorer. Currently, the core +engine of Orthanc can decode: * uncompressed (raw) DICOM files, * JPEG DICOM files, and @@ -25,7 +31,8 @@ The supported photometric interpretations are: * RGB, -* Grayscale2. +* Grayscale2, +* YUV if dealing with JPEG derivatives. The Orthanc core supports from 8bpp to 16bpp depth, with integer values. Multiframe (notably cine), uncompressed DICOM instances can