Clarify 1.2.840.113619.5.2 [Implicit VR Big Endian DLX (G.E Private)] support

[malaterre]

I have not been able to find the documentation (ie. some kind of DICOM Conformance Statement) for dicomParser, so please forgive me if I missed something.

In any case would be it possible to clarify support for 1.2.840.113619.5.2 [Implicit VR Big Endian DLX (G.E Private)]. Right now it return "Status: Error - dicomParser.parseDicom: missing required meta header attribute 0002,0010 (file of size 13.503 MB )" or "Status: Error - dicomParser:parseDicomDataSetExplicit: buffer overrun (file of size 13.503 MB )" if you patch the Meta Header to be Explicit, which is quite counter-intuitive.

For reference:

• https://sourceforge.net/p/gdcm/gdcmdata/ci/master/tree/GE_DLX-8-MONO2-PrivateSyntax.dcm

Use $ gdcmconv -C GE_DLX-8-MONO2-PrivateSyntax.dcm P10.dcm to test both scenario.

[chafey]

The intended design of this library is to be strictly DICOM Standard compliant out of the box but allow some non standard behaviors through opt-in flags (off by default). I don't know anything about this private ge transfer syntax and did not design for it.

[neandrake]

Commenting just for the record with some info about this private GE transfer syntax in case anyone comes across this looking for more info. This transfer syntax appears to have all dicom elements using Little Endian with exception of PixelData which uses Big Endian 🤷 . Using Implicit VR Little Endian should parse through the dicom elements properly but the bytes in PixelData value should be interpreted using Big Endian.