Problem with reading file
Moderator: Moderator Team
Problem with reading file
Hi,
I use DCMTK open dicom file in windows .It can't find lot's of TAG .And i save the file,the size of new file larger than original file, 518KB -> 1601KB;The file is SIEMENS CT image,Manufacturer's Model Name is SOMATOM PLUS 4.I use other tools can open it and get correct tag value.
I use DCMTK open dicom file in windows .It can't find lot's of TAG .And i save the file,the size of new file larger than original file, 518KB -> 1601KB;The file is SIEMENS CT image,Manufacturer's Model Name is SOMATOM PLUS 4.I use other tools can open it and get correct tag value.
-
- ICSMED DICOM Services
- Posts: 2217
- Joined: Fri, 2004-10-29, 21:38
- Location: Oldenburg, Germany
THX,i test that file with dcmcjpeg.exe ,errors as follows:
DcmItem: Non-standard VR 'RT' encountered while parsing attribute (0008,0040), assuming 4 byte length field
DcmItem: Non-standard VR 'g' encountered while parsing attribute (0066,0066), assuming 2 byte length field
DcmItem: Non-standard VR 'f' encountered while parsing attribute (0067,0067), assuming 2 byte length field
DcmItem: Non-standard VR 'c' encountered while parsing attribute (005f,0064), assuming 2 byte length field
DcmItem: Dataset not in ascending tag order, at element (005f,0064)
DcmItem: Non-standard VR 'b' encountered while parsing attribute (0063,0067), assuming 2 byte length field
DcmItem: Dataset not in ascending tag order, at element (0063,0067)
DcmItem: Non-standard VR 'l' encountered while parsing attribute (0069,0066), assuming 2 byte length field
DcmItem: Non-standard VR 'd' encountered while parsing attribute (0062,0063), assuming 2 byte length field
DcmItem: Dataset not in ascending tag order, at element (0062,0063)
DcmItem: Non-standard VR '' encountered while parsing attribute (018d,01fe), assuming 2 byte length field
DcmItem: Non-standard VR 'k' encountered while parsing attribute (0064,0069), assuming 2 byte length field
DcmItem: Dataset not in ascending tag order, at element (0064,0069)
DcmItem: Non-standard VR 'f' encountered while parsing attribute (006a,006b), assuming 2 byte length field
DcmItem: Length of attribute (006a,006b) is odd
DcmItem: Dataset not in ascending tag order, at element (006a,006b)
DcmItem: Non-standard VR '' encountered while parsing attribute (1701,f201), assuming 2 byte length field
DcmElement: Unknown Tag & Data(1701,f201) larger (56320) that remaining bytes in file
DcmItem: Non-standard VR 'RT' encountered while parsing attribute (0008,0040), assuming 4 byte length field
DcmItem: Non-standard VR 'g' encountered while parsing attribute (0066,0066), assuming 2 byte length field
DcmItem: Non-standard VR 'f' encountered while parsing attribute (0067,0067), assuming 2 byte length field
DcmItem: Non-standard VR 'c' encountered while parsing attribute (005f,0064), assuming 2 byte length field
DcmItem: Dataset not in ascending tag order, at element (005f,0064)
DcmItem: Non-standard VR 'b' encountered while parsing attribute (0063,0067), assuming 2 byte length field
DcmItem: Dataset not in ascending tag order, at element (0063,0067)
DcmItem: Non-standard VR 'l' encountered while parsing attribute (0069,0066), assuming 2 byte length field
DcmItem: Non-standard VR 'd' encountered while parsing attribute (0062,0063), assuming 2 byte length field
DcmItem: Dataset not in ascending tag order, at element (0062,0063)
DcmItem: Non-standard VR '' encountered while parsing attribute (018d,01fe), assuming 2 byte length field
DcmItem: Non-standard VR 'k' encountered while parsing attribute (0064,0069), assuming 2 byte length field
DcmItem: Dataset not in ascending tag order, at element (0064,0069)
DcmItem: Non-standard VR 'f' encountered while parsing attribute (006a,006b), assuming 2 byte length field
DcmItem: Length of attribute (006a,006b) is odd
DcmItem: Dataset not in ascending tag order, at element (006a,006b)
DcmItem: Non-standard VR '' encountered while parsing attribute (1701,f201), assuming 2 byte length field
DcmElement: Unknown Tag & Data(1701,f201) larger (56320) that remaining bytes in file
-
- ICSMED DICOM Services
- Posts: 2217
- Joined: Fri, 2004-10-29, 21:38
- Location: Oldenburg, Germany
-
- OFFIS DICOM Team
- Posts: 1437
- Joined: Tue, 2004-11-02, 17:22
- Location: Oldenburg, Germany
- Contact:
The file is not a valid DICOM file. The problem is that in various places a Value Representation named "RT" is used - this does not exist in DICOM. When DCMTK reads an unknown VR in a DICOM file, it assumes a 4-byte length field (because there is a rule in DICOM that all "future" new VRs will use 4-byte length fields), but the "RT" attributes in the file use 2-byte length fields. While it would be possible to extend the DCMTK parser to handle this as a special case, the file is severely damaged and the problem should rather be fixed on the sender's side, since hardly any DICOM toolkit will correctly read this file.
Who is online
Users browsing this forum: Bing [Bot] and 1 guest