Closed GoogleCodeExporter closed 9 years ago
Hi,
Sorry, but this file is corrupted. Neither "gdcmdump", nor "dcm2xml" can decode
it. Here is the output of dicom3tools:
>>>>>
# ./dicom3tools-dciodvfy ./CT000000
Error - Tags out of order - trailing garbage, wrong transfer syntax, or not
valid DICOM
Warning - Value dubious for this VR - (0x0008,0x0090) PN Referring Physician's
Name PN [0] = <CV ALBEA> - Retired Person Name form
Warning - Value dubious for this VR - (0x0008,0x1070) PN Operators' Name PN
[0] = <A.ARTILES> - Retired Person Name form
Warning - Value dubious for this VR - (0x0010,0x0010) PN Patient's Name PN [0]
= <BART-SONIA ESCRIBANO MOYA> - Retired Person Name form
Warning - Retired attribute - (0x0018,0x1141) DS Angular Position
Warning - Dicom dataset contains retired attributes
CTImage
Warning - is only permitted to be empty when actually unknown; should be absent
(not empty) if an unpaired body part, and have a value if a paired body part -
attribute <Laterality>
Warning - Attribute is not present in standard DICOM IOD - (0x0018,0x1141) DS
Angular Position
Warning - Attribute is not present in standard DICOM IOD - (0x0018,0x1143) DS
Scan Arc
Warning - Dicom dataset contains attributes not present in standard DICOM IOD -
this is a Standard Extended SOP Class
<<<<<
There is nothing we can do.
Original comment by s.jodo...@gmail.com
on 20 May 2015 at 8:42
I figured it was corrupted.
However, I thought something was wrong because this person told me he
"downloaded the ZIP from Orthanc Explorer".
If the original file was corrupted as well - how did he get it into Orthanc in
the first place? (Perhaps it was through DICOM Send instead of Explorer upload?)
I'll try to get more details from him if you think it's worth investigating.
Thanks again! :)
Original comment by eml...@yahoo.com
on 20 May 2015 at 8:55
Unfortunately, it is impossible to know what happened without having access to
the original DICOM file and without knowing the version of Orthanc that was
used. Of course, I will be happy to investigate further if this information
gets available.
Original comment by s.jodo...@gmail.com
on 20 May 2015 at 9:00
Original issue reported on code.google.com by
eml...@yahoo.com
on 20 May 2015 at 8:34Attachments: