-
Notifications
You must be signed in to change notification settings - Fork 631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle ExplicitVR DICOM file contains invalid VR #1660
Comments
If you suggest that fo-dicom should continue reading and silently ignore the obviously wrong data, how should fo-dicom then proceed with that data? The expected behavior is not as trivial as one might expect. |
With _isExplicitVR. Some other programs handle such file keeps the wrong VR and go on. Suggest: For flexibility: |
With an ExplicitVR DICOM file.
DicomFile.Open method return partial dataset when dicom item contains invalid VR.
To Reproduce
With an ExplicitVR DICOM file.
Change one dicom item's VR to a string other than defined VRs.
For example, if the dataset contains item: 0010 21B0, the formal VR is LT, but -- is placed.
Bytes placed in file:
10 00 B0 21 2D 2D 54 00 47 30 30 30 30 ......
When item 0010 21B0 is read, DicomFileReader returns DicomReaderResult.Suspended.
Expected behavior
Continue to parse items.
Environment
Fellow Oak DICOM version: 5.1.1
OS: Windows 10
Platform: NET Framework 4.6.1
The text was updated successfully, but these errors were encountered: