DICOM @ OFFIS

What exactly is unclear in the following paragraph (taken from the "datadict.txt" file)? Also included in the sources is a pre-created built-in data dictionary which can be used instead (dcmdata/libsrc/dcdictzz.cc). For example, the project files for the Windows platform use this file inst...

Have you read the API documentation? The DicomImage::getOutputData() method always creates MONOCHROME2 or RGB images, where the pixel values are padded to 8, 16 or 32 bits (i.e. Bits Allocated). If you need 10 Bits Stored, you should pass this value to getOutputData().

What about reading the documentation

There are, for example, findAndGetUint16(), findAndGetUint16Array(), findAndGetOFString(), findAndGetOFStringArray() ...

Then, this question is really easy to answer (by simply looking into the documentation): Acquisition Matrix has the VR "US" and findAndGetString() is not applicable to this VR - that's it. and i am getting NULL which i have set as a default. Read the API documentation: "The result var...

My question was more directed to the following details: Which DCMTK method have you used and what was the OFCondition return value?

I would first check whether this issue (if there really is one) has already been fixed with DCMTK 3.6.0.

What exactly does not work or - to be more precise - what have you tried in order to get the value of Acquisition Matrix?

If the buffer returned by getOutputData is the internal buffer, why it isn't changed? The term "Output" in the method name already suggests that it is not the so-called intermediate pixel data that is returned, it is just the resulting pixel matrix of the rendering process. Also the docum...

It seems DCMTK don't have float precisions for immediate formats No, because IMHO the described use case is not what the Pixel Data is/was meant for - I would even call this an "abuse" of the Pixel Data element. Nevertheless, you could modify the Rescale Slope/Intercept values (if needed)...

How to make Visual C++ recognize file extensions as C/C++ files (MSDN).

Maybe, it's too obvious, but since you have the complete source code: Why don't you just search for "isinf"? Then you'll also see that isinf() is only used if HAVE_ISINF is defined ...

I checked the sequence classes and found another "specialty" (or let's call it abnormality?) of the DICOM RT IODs: The same sequence attribute might be defined completely differently depending on where it is used, i.e. the attributes contained in the sequence items can be different and, th...

First of all, thank you for testing "dcmrt" and for your comments. With regard to the missing attributes: You might have realized that more than 99% of the classes (including their implementation) are generated automatically from a machine-readable version of the DICOM standard. The commen...

First of all, I would recommend that you switch to the current DCMTK release 3.6.0! Then, you usually don't want to have a different Study Instance UID for each individual worklist entry (aka scheduled procedure step) because of grouping and other use cases. However, you can e.g. use dcmodify with o...

Reading Annex K in DICOM PS 3.4 might help, especially table Table K.6-1: Patient ID shall be retrieved with Single Value Matching only (i.e. no wildcards). In addition, Accession Number is an optional Matching Key and type 2 Return Key, but it is supported by wlmscpfs as you can read in the documen...