On Sun, Jan 31, 2016 at 07:42:26PM +0100, Karsten Hilbert wrote: > > The Implementation Version Name in the meta information header > > says "OFFIS_DCMTK_360", but dcmtk doesn't make this kind > > of error, as far as I know, so Karsten, it would be good > > to know what system actually encoded this bad DICOM file. > > That doesn't matter because: > > - initially, GinkgoCADx (and hence GDCM ?) reads the file > just fine from local storage (say, CD-ROM) > - it then sends the file to a PACS > - it then retrieves the file from the same PACS > - it then does not read the very same file anymore
And, may I add, this behaviour happens with DICOM files from various (commercial) sources. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
