1dcmconv(1) OFFIS DCMTK dcmconv(1)
2
6 dcmconv - Convert DICOM file encoding
7
9 dcmconv [options] dcmfile-in dcmfile-out
10
12 The dcmconv utility reads a DICOM file (dcmfile-in), performs an
13 encoding conversion and writes the converted data to an output file
14 (dcmfile-out).
15
17 dcmfile-in DICOM input filename to be converted
18 dcmfile-out DICOM output filename to write to
20
22 general options
23 -h --help
24 print this help text and exit
25 --version
27 print version information and exit
28 --arguments
30 print expanded command line arguments
31 -q --quiet
33 quiet mode, print no warnings and errors
34 -v --verbose
36 verbose mode, print processing details
37 -d --debug
39 debug mode, print debug information
40 -l --log-level [l]evel: string constant
42 (fatal, error, warn, info, debug, trace)
43 use level l for the logger
44 -l --log-config [f]ilename: string
46 use config file f for the logger
47 input options
49 input file format:
50 +f --read-file
52 read file format or data set (default)
53 +fo --read-file-only
55 read file format only
56 -f --read-dataset
58 read data set without file meta information
59 input transfer syntax:
61 -t= --read-xfer-auto
63 use TS recognition (default)
64 -td --read-xfer-detect
66 ignore TS specified in the file meta header
67 -te --read-xfer-little
69 read with explicit VR little endian TS
70 -tb --read-xfer-big
72 read with explicit VR big endian TS
73 -ti --read-xfer-implicit
75 read with implicit VR little endian TS
76 parsing of file meta information:
78 +ml --use-meta-length
80 use file meta information group length (default)
81 -ml --ignore-meta-length
83 ignore file meta information group length
84 parsing of odd-length attributes:
86 +ao --accept-odd-length
88 accept odd length attributes (default)
89 +ae --assume-even-length
91 assume real length is one byte larger
92 handling of non-standard VR:
94 +vr --treat-as-unknown
96 treat non-standard VR as unknown (default)
97 -vr --assume-implicit
99 try to read with implicit VR little endian TS
100 handling of undefined length UN elements:
102 +ui --enable-cp246
104 read undefined len UN as implicit VR (default)
105 -ui --disable-cp246
107 read undefined len UN as explicit VR
108 handling of defined length UN elements:
110 -uc --retain-un
112 retain elements as UN (default)
113 +uc --convert-un
115 convert to real VR if known
116 handling of private max-length elements (implicit VR):
118 -sq --maxlength-dict
120 read as defined in dictionary (default)
121 +sq --maxlength-seq
123 read as sequence with undefined length
124 general handling of parser errors:
126 +Ep --ignore-parse-errors
128 try to recover from parse errors
129 -Ep --handle-parse-errors
131 handle parse errors and stop parsing (default)
132 other parsing options:
134 +st --stop-after-elem [t]ag: "gggg,eeee" or dictionary name
136 stop parsing after element specified by t
137 automatic data correction:
139 +dc --enable-correction
141 enable automatic data correction (default)
142 -dc --disable-correction
144 disable automatic data correction
145 bitstream format of deflated input:
147 +bd --bitstream-deflated
149 expect deflated bitstream (default)
150 +bz --bitstream-zlib
152 expect deflated zlib bitstream
153 output options
155 output file format:
156 +F --write-file
158 write file format (default)
159 +Fm --write-new-meta-info
161 write file format with new meta information
162 -F --write-dataset
164 write data set without file meta information
165 output transfer syntax:
167 +t= --write-xfer-same
169 write with same TS as input (default)
170 +te --write-xfer-little
172 write with explicit VR little endian TS
173 +tb --write-xfer-big
175 write with explicit VR big endian TS
176 +ti --write-xfer-implicit
178 write with implicit VR little endian TS
179 +td --write-xfer-deflated
181 write with deflated explicit VR little endian TS
182 post-1993 value representations:
184 +u --enable-new-vr
186 enable support for new VRs (UN/UT) (default)
187 -u --disable-new-vr
189 disable support for new VRs, convert to OB
190 group length encoding:
192 +g= --group-length-recalc
194 recalculate group lengths if present (default)
195 +g --group-length-create
197 always write with group length elements
198 -g --group-length-remove
200 always write without group length elements
201 length encoding in sequences and items:
203 +e --length-explicit
205 write with explicit lengths (default)
206 -e --length-undefined
208 write with undefined lengths
209 +eo --write-oversized
211 write oversized explicit length sequences
212 and items with undefined length (default)
213 -eo --abort-oversized
215 abort on oversized explicit sequences/items
216 data set trailing padding (not with --write-dataset):
218 -p= --padding-retain
220 do not change padding (default if not --write-dataset)
221 -p --padding-off
223 no padding (implicit if --write-dataset)
224 +p --padding-create [f]ile-pad [i]tem-pad: integer
226 align file on multiple of f bytes
227 and items on multiple of i bytes
228 deflate compression level (only with --write-xfer-deflated):
230 +cl --compression-level [l]evel: integer (default: 6)
232 0=uncompressed, 1=fastest, 9=best compression
233 other output options:
235 -ig --no-invalid-groups
237 don't write elements with invalid group number
238
240 The level of logging output of the various command line tools and
241 underlying libraries can be specified by the user. By default, only
242 errors and warnings are written to the standard error stream. Using
243 option --verbose also informational messages like processing details
244 are reported. Option --debug can be used to get more details on the
245 internal activity, e.g. for debugging purposes. Other logging levels
246 can be selected using option --log-level. In --quiet mode only fatal
247 errors are reported. In such very severe error events, the application
248 will usually terminate. For more details on the different logging
249 levels, see documentation of module 'oflog'.
250 In case the logging output should be written to file (optionally with
252 logfile rotation), to syslog (Unix) or the event log (Windows) option
253 --log-config can be used. This configuration file also allows for
254 directing only certain messages to a particular output stream and for
255 filtering certain messages based on the module or application where
256 they are generated. An example configuration file is provided in
257 <etcdir>/logger.cfg).
258
260 All command line tools use the following notation for parameters:
261 square brackets enclose optional values (0-1), three trailing dots
262 indicate that multiple values are allowed (1-n), a combination of both
263 means 0 to n values.
264 Command line options are distinguished from parameters by a leading '+'
266 or '-' sign, respectively. Usually, order and position of command line
267 options are arbitrary (i.e. they can appear anywhere). However, if
268 options are mutually exclusive the rightmost appearance is used. This
269 behaviour conforms to the standard evaluation rules of common Unix
270 shells.
271 In addition, one or more command files can be specified using an '@'
273 sign as a prefix to the filename (e.g. @command.txt). Such a command
274 argument is replaced by the content of the corresponding text file
275 (multiple whitespaces are treated as a single separator unless they
276 appear between two quotation marks) prior to any further evaluation.
277 Please note that a command file cannot contain another command file.
278 This simple but effective approach allows to summarize common
279 combinations of options/parameters and avoids longish and confusing
280 command lines (an example is provided in file <datadir>/dumppat.txt).
281
283 The dcmconv utility will attempt to load DICOM data dictionaries
284 specified in the DCMDICTPATH environment variable. By default, i.e. if
285 the DCMDICTPATH environment variable is not set, the file
286 <datadir>/dicom.dic will be loaded unless the dictionary is built into
287 the application (default for Windows).
288 The default behaviour should be preferred and the DCMDICTPATH
290 environment variable only used when alternative data dictionaries are
291 required. The DCMDICTPATH environment variable has the same format as
292 the Unix shell PATH variable in that a colon (':') separates entries.
293 On Windows systems, a semicolon (';') is used as a separator. The data
294 dictionary code will attempt to load each file specified in the
295 DCMDICTPATH environment variable. It is an error if no data dictionary
296 can be loaded.
297
299 dcmdump(1)
300
302 Copyright (C) 1994-2010 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
303 Germany.
304Version 3.6.0 6 Jan 2011 dcmconv(1)