1GDCMINFO(1)                   DICOM Manipulation.                  GDCMINFO(1)
2
3
4

NAME

6       gdcminfo - Display meta info about the input DICOM file.
7

SYNOPSIS

9       gdcminfo [options] [file-in/dir-in...]
10

DESCRIPTION

12       The gdcminfo command line program takes as input a DICOM file, or a
13       directory and process it to extract meta-information about the DICOM
14       file(s) processed.
15

PARAMETERS

17           file-in/dir-in   DICOM input filename/dirname
18

OPTIONS

20   specific options
21             -r --recursive          recursive traversal of an input directory
22             -d --check-deflated     check if file is proper deflated syntax.
23                --resources-path     Resources path.
24                --md5sum             Compute md5sum of Pixel Data attribute value.
25                --check-compression  check the encapsulated stream compression (lossless/lossy).
26
27   general options
28             -h   --help
29                    print this help text and exit
30
31             -v   --version
32                    print version information and exit
33
34             -V   --verbose
35                    verbose mode (warning+error).
36
37             -W   --warning
38                    warning mode, print warning information
39
40             -E   --error
41                    error mode, print error information
42
43             -D   --debug
44                    debug mode, print debug information
45
46   environment variable
47       GDCM_RESOURCES_PATH path pointing to resources files (Part3.xml, ...)
48

SIMPLE USAGE

50   gdcmData
51       Using data from gdcmData:
52
53           $ gdcminfo gdcmData/012345.002.050.dcm
54
55           MediaStorage is 1.2.840.10008.5.1.4.1.1.4 [MR Image Storage]
56           NumberOfDimensions: 2
57           Dimensions: (256,256)
58           Origin: (-85,21.6,108.7)
59           Spacing: (0.664062,0.664062,1.5)
60           DirectionCosines: (1,0,0,0,0,-1)
61           Rescale Intercept/Slope: (0,1)
62           SamplesPerPixel    :1
63           BitsAllocated      :16
64           BitsStored         :16
65           HighBit            :15
66           PixelRepresentation:1
67           Orientation Label: CORONAL
68
69   Davie Clunie datasets:
70       Using data from David Clunie datasets:
71
72           $ gdcminfo BRTUM001.dcm
73
74           MediaStorage is 1.2.840.10008.5.1.4.1.1.4.1 [Enhanced MR Image Storage]
75           NumberOfDimensions: 3
76           Dimensions: (256,256,15)
77           Origin: (40,-105,105)
78           Spacing: (0.820312,0.820312,6)
79           DirectionCosines: (0,1,0,0,0,-1)
80           Rescale Intercept/Slope: (0,1)
81           SamplesPerPixel    :1
82           BitsAllocated      :16
83           BitsStored         :16
84           HighBit            :15
85           PixelRepresentation:1
86           Orientation Label: SAGITTAL
87
88   Checking the md5sum of the Pixel Data
89       After compressing a DICOM file (see gdcmconv) using a lossless
90       compression algorithm, it is fairly easy to compare the two files for
91       differences at DICOM attribute level. However one operation is slightly
92       easier to do: how to make sure the compression was actually lossless ?
93       In this case one could use the –md5sum operation.
94
95       Take an uncompressed DICOM image file:
96
97           $ gdcminfo --md5sum SIEMENS_ImageLocationUN.dcm
98
99       The tool return: 0621954acd5815e0b4f7b65fcc6506b1
100
101       Now compress this file:
102
103           $ gdcmconv --jpegls SIEMENS_ImageLocationUN.dcm lossless_compressed.dcm
104
105       and then check again the md5sum:
106
107           $ gdcminfo --md5sum lossless_compressed.dcm
108
109       The tool return: 0621954acd5815e0b4f7b65fcc6506b1
110
111   Checking if Pixel Data is lossless
112       In some environment one wish to check whether or not the DICOM file is
113       lossless. It is fairly easy to do that in most cases. Only on two
114       occasions this is not clear from the sole DICOM Attributes. When the
115       Transfer Syntax is JPEG 2000 Image Compression (1.2.840.10008.1.2.4.91)
116       and when the Transfer Syntax is JPEG-LS Lossy (Near-Lossless) Image
117       Compression (1.2.840.10008.1.2.4.81).
118
119       In this case, the only solution is to open the Pixel Data element, read
120       the specific JPEG header and check whether or not the JPEG
121       transformation was lossless or not:
122
123           $ gdcminfo --check-compression gdcmData/MAROTECH_CT_JP2Lossy.dcm
124
125       The tool returns: “Encapsulated Stream was found to be: lossy”
126
127       Pay attention that this tool also checks the Image Lossy Compression
128       attribute (0028,2110). This means --check-compression will also returns
129       a value of lossy if a predecessor was found to be lossy compressed.
130

CHECKING IMAGE AS IF MOSAIC

132       Dump the image as if MOSAIC. If the input is really MOSAIC image, then
133       print the information of the true underlying MOSAIC volume.
134
135           $ gdcminfo --mosaic siemens_mosaic.dcm
136

SEE ALSO

138       gdcmdump(1), gdcmraw(1), gdcmconv(1)
139

AUTHOR

141       Mathieu Malaterre
142           Main developer
143

145       Copyright © 2006, 2011 Mathieu Malaterre
146
147
148
149GDCM 2.8.4                        08/14/2018                       GDCMINFO(1)
Impressum