On Aug 20, 10:28 am, gunter zeilinger
wrote:
> On Aug 19, 11:43 am, Mathieu Malaterre
> wrote:
>
> > If anyone is interested in supporting this file:
>
> >http://forums.dcm4che.org/jiveforums...a?threadID=644
>
> > or direct link:
>
> >http://forums.dcm4che.org/jiveforums...t/download/5-6...
>
> > Amazingly dcmtk was able to parse it, without no problem.
>
> > 2cts
> > -Mathieu
>
> I guess, most DICOM implementations will able to parse the file, but
> interpreting the encapsulated pixel data as JPEG baseline stream would
> need to apply some simple heuristic (e.g. detect JPEG SOI marker).
> Fortunately, I have not (yet) seen such objects in real PACS
> installations, and I hope that the possibility to create such invalid
> DICOM objects by wrong usage of dcm4che's jpg2dcm utility will not
> induce that such objects show up in future.
Gunter,
Seriously, how could you blame your dcm4che user for that. If this
is so easy to create such invalid DICOM object, I'd rather think there
is a serious bug in how your write DICOM DataSet in jpg2dcm. Add
somewhere in your code that you cannot have encapsulated JPEG with
implicit dataset. This is much simpler than adding a "simple
heuristic" in every DICOM implementation to guess that a JPEG stream
is encapsulated within an implicit dataset.
Marco,
That is yet another example of why I think a list of valid/invalid
DICOM objects is becoming a necessity for DICOM implementors.
-Mathieu