1dcmcrle(1) OFFIS DCMTK dcmcrle(1)
2
6 dcmcrle - Encode DICOM file to RLE transfer syntax
7
9 dcmcrle [options] dcmfile-in dcmfile-out
10
12 The dcmcrle utility reads an uncompressed DICOM image (dcmfile-in),
13 performs RLE compression (i.e. conversion to an encapsulated DICOM
14 transfer syntax) and writes the converted image to an output file
15 (dcmfile-out).
16
18 dcmfile-in DICOM input filename to be converted
19 dcmfile-out DICOM output filename
21
23 general options
24 -h --help
25 print this help text and exit
26 --version
28 print version information and exit
29 --arguments
31 print expanded command line arguments
32 -q --quiet
34 quiet mode, print no warnings and errors
35 -v --verbose
37 verbose mode, print processing details
38 -d --debug
40 debug mode, print debug information
41 -ll --log-level [l]evel: string constant
43 (fatal, error, warn, info, debug, trace)
44 use level l for the logger
45 -lc --log-config [f]ilename: string
47 use config file f for the logger
48 input options
50 input file format:
51 +f --read-file
53 read file format or data set (default)
54 +fo --read-file-only
56 read file format only
57 -f --read-dataset
59 read data set without file meta information
60 input transfer syntax:
62 -t= --read-xfer-auto
64 use TS recognition (default)
65 -td --read-xfer-detect
67 ignore TS specified in the file meta header
68 -te --read-xfer-little
70 read with explicit VR little endian TS
71 -tb --read-xfer-big
73 read with explicit VR big endian TS
74 -ti --read-xfer-implicit
76 read with implicit VR little endian TS
77 encapsulated pixel data encoding options
79 pixel data fragmentation:
80 +ff --fragment-per-frame
82 encode each frame as one fragment (default)
83 +fs --fragment-size [s]ize: integer
85 limit fragment size to s kbytes (non-standard)
86 basic offset table encoding:
88 +ot --offset-table-create
90 create offset table (default)
91 -ot --offset-table-empty
93 leave offset table empty
94 SOP Class UID:
96 +cd --class-default
98 keep SOP Class UID (default)
99 +cs --class-sc
101 convert to Secondary Capture Image (implies --uid-always)
102 SOP Instance UID:
104 +un --uid-never
105 never assign new UID (default)
106 +ua --uid-always
108 always assign new UID
109 output options
111 post-1993 value representations:
112 +u --enable-new-vr
114 enable support for new VRs (UN/UT) (default)
115 -u --disable-new-vr
117 disable support for new VRs, convert to OB
118 group length encoding:
120 +g= --group-length-recalc
122 recalculate group lengths if present (default)
123 +g --group-length-create
125 always write with group length elements
126 -g --group-length-remove
128 always write without group length elements
129 length encoding in sequences and items:
131 +e --length-explicit
133 write with explicit lengths (default)
134 -e --length-undefined
136 write with undefined lengths
137 data set trailing padding:
139 -p= --padding-retain
141 do not change padding (default)
142 -p --padding-off
144 no padding
145 +p --padding-create [f]ile-pad [i]tem-pad: integer
147 align file on multiple of f bytes
148 and items on multiple of i bytes
149
151 dcmcrle supports the following transfer syntaxes for input (dcmfile-
152 in):
153 LittleEndianImplicitTransferSyntax 1.2.840.10008.1.2
155 LittleEndianExplicitTransferSyntax 1.2.840.10008.1.2.1
156 DeflatedExplicitVRLittleEndianTransferSyntax 1.2.840.10008.1.2.1.99 (*)
157 BigEndianExplicitTransferSyntax 1.2.840.10008.1.2.2
158 (*) if compiled with zlib support enabled
160 dcmcrle supports the following transfer syntaxes for output (dcmfile-
162 out):
163 RLELosslessTransferSyntax 1.2.840.10008.1.2.5
165
167 The level of logging output of the various command line tools and
168 underlying libraries can be specified by the user. By default, only
169 errors and warnings are written to the standard error stream. Using
170 option --verbose also informational messages like processing details
171 are reported. Option --debug can be used to get more details on the
172 internal activity, e.g. for debugging purposes. Other logging levels
173 can be selected using option --log-level. In --quiet mode only fatal
174 errors are reported. In such very severe error events, the application
175 will usually terminate. For more details on the different logging
176 levels, see documentation of module 'oflog'.
177 In case the logging output should be written to file (optionally with
179 logfile rotation), to syslog (Unix) or the event log (Windows) option
180 --log-config can be used. This configuration file also allows for
181 directing only certain messages to a particular output stream and for
182 filtering certain messages based on the module or application where
183 they are generated. An example configuration file is provided in
184 <etcdir>/logger.cfg).
185
187 All command line tools use the following notation for parameters:
188 square brackets enclose optional values (0-1), three trailing dots
189 indicate that multiple values are allowed (1-n), a combination of both
190 means 0 to n values.
191 Command line options are distinguished from parameters by a leading '+'
193 or '-' sign, respectively. Usually, order and position of command line
194 options are arbitrary (i.e. they can appear anywhere). However, if
195 options are mutually exclusive the rightmost appearance is used. This
196 behaviour conforms to the standard evaluation rules of common Unix
197 shells.
198 In addition, one or more command files can be specified using an '@'
200 sign as a prefix to the filename (e.g. @command.txt). Such a command
201 argument is replaced by the content of the corresponding text file
202 (multiple whitespaces are treated as a single separator unless they
203 appear between two quotation marks) prior to any further evaluation.
204 Please note that a command file cannot contain another command file.
205 This simple but effective approach allows to summarize common
206 combinations of options/parameters and avoids longish and confusing
207 command lines (an example is provided in file <datadir>/dumppat.txt).
208
210 The dcmcrle utility will attempt to load DICOM data dictionaries
211 specified in the DCMDICTPATH environment variable. By default, i.e. if
212 the DCMDICTPATH environment variable is not set, the file
213 <datadir>/dicom.dic will be loaded unless the dictionary is built into
214 the application (default for Windows).
215 The default behaviour should be preferred and the DCMDICTPATH
217 environment variable only used when alternative data dictionaries are
218 required. The DCMDICTPATH environment variable has the same format as
219 the Unix shell PATH variable in that a colon (':') separates entries.
220 On Windows systems, a semicolon (';') is used as a separator. The data
221 dictionary code will attempt to load each file specified in the
222 DCMDICTPATH environment variable. It is an error if no data dictionary
223 can be loaded.
224
226 dcmdrle(1)
227
229 Copyright (C) 2002-2010 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
230 Germany.
231Version 3.6.0 6 Jan 2011 dcmcrle(1)