Some more explanations about PMS oddities :

[gdcmData.git] / MR_Philips_Intera_No_PrivateSequenceImplicitVR.README.txt

diff --git a/MR_Philips_Intera_No_PrivateSequenceImplicitVR.README.txt b/MR_Philips_Intera_No_PrivateSequenceImplicitVR.README.txt
index cd0b3a869fb032384b4a61adfec5d82fe417d28c..8e493a2e3fd3a090a03596819852abef9bf72304 100644 (file)
--- a/MR_Philips_Intera_No_PrivateSequenceImplicitVR.README.txt
+++ b/MR_Philips_Intera_No_PrivateSequenceImplicitVR.README.txt
@@ -4,4 +4,9 @@ No more trouble, nowhere !
 Private Sequences are 'Implicit VR', (and their length is *not* 0xffffffff)
 Readers cannot know it's a Sequence; they just read it as a long value.
 If we take into account Phillips Intera 'shadow dictionnary', same problem as
-for MR_Philips_Intera_Broken.dcm occurs again.
+for MR_Philips_Intera_Broken.dcm occurs again, *for 2 reasons* :
+
+endianess is swapped inside  Private Sequence 2001|105f,
+The TS was Implicit VR; it becomes EXPLICIT VR ! 
+
+gdcm heuristics is broken :-(