DICOM @ OFFIS

Did you already try with the --invent option?

The Attributes that dcmmkdir lists as missing are of Type 1 in a DICOMDIR.

By the way, the options "+xy +xs +xx" in your call of dcmqrscp are mutually exclusive and the last one wins (see documentation).

Another follow-up question: What is the purpose of these options that you use to call dcmsend, i.e. in this combination: "+r --scan-directories IMAGES\*.dcm"?

If I am reading this correctly JPEG Baseline is not offered in the presentation context negotiation. In fact, it is proposed by dcmsend, but not accepted by dcmqrscp (by default). What specifically should I do to enable the SCP to accept JPEG Baseline? You could either start dcmqrscp with option --...

If the name of the patient you want to query is encoded in GB 18030, you need to specify this character set (i.e. "GB18030") in the Specific Character Set (0008,0005) Attribute. If the name is encoded in UTF-8, you need to specify "ISO_IR 192". However, if the SCP does not support matching names in ...

I cannot obtain correct patient information by specifying (00080005) as either ISO_IR 192 or GB18030 The Specific Character Set (0008,0005) Attribute in your Query just specifies the character encoding of your query. The SCP is free to send C-FIND response datasets with a different character encodi...

dataset ->convertCharacterSet ("ISO-IR 192", "GB18030") This call should return an error, since "ISO-IR 192" is no Defined Term in DICOM (in contrast to "ISO_IR 192") and conversion to "GB18030" is not yet implemented in the DCMTK (in contrast to conversion from this character set). 1. Why ISO_ IR ...

What is the value of the CMake option "DCMTK_ENABLE_CHARSET_CONVERSION"?

PS: Your referenced images are currently not shown.

also please explain why the file limit is 4GB and not more. is there any way to bypass this? The Pixel Data (7fe0,0010) Data Element has a Length Field of 32-bit, so the maximum size of uncompressed pixel data is (usually) limited to about 4.2 GB. Only recently, CP-2083 introduced a new Transfer Sy...

Specifying the Specific Character Set (0008,0005) in your query is not needed since your query does not contain any non-ASCII characters. In order to make sure that it is not a display problem on your side (Windows command shell or terminal?), you should write the received C-FIND Response Data Sets ...

By default, the DicomImage class only supports monochrome DICOM images. In order to register support for color images (such as yours), you need to include the header file "dcmtk/dcmimage/diregist.h" into your source code and recompile.

The DICOM image is JPEG2000 compressed. As I wrote in my previous posting, the public DCMTK cannot decompress such images. You need e.g. the DCMJP2K extension for doing this.

First of all, you should make sure that the DICOM data dictionary file "dicom.dic" is loaded. Since the file is apparently not located in the default path (/usr/share/libdcmtk12/dicom.dic) you need to specify the location of the file with the environment variable DCMDICTPATH. See documentation for d...

dump2dcm expects two parameters, so the ">" is probably causing the problem. (I mean, in addition to the "write access" issue Michael mentioned in his posting.)

This is a global flag, so it has a global scope. It is, therefore, sufficient so set it to "OFTrue" once, e.g. at program start.

You did not pass the parameters to the constructor as Marco suggested: DicomImage* dicomImage = new DicomImage(dicomFilePath); See this Howto: Access multi-frame images without loading complete pixel data . However, please note that the public DCMTK does not support decompressing JPEG2000-compressed...