1stl2dcm(1) OFFIS DCMTK stl2dcm(1)
2
6 stl2dcm - Encapsulate STL file into DICOM file format
7
10 stl2dcm [options] stlfile-in dcmfile-out
11
13 The stl2dcm utility reads a STL file (stlfile-in), converts it to a
14 DICOM Encapsulated STL Storage SOP instance and stores the converted
15 data to an output file (dcmfile-out).
16
18 stlfile-in STL input filename to be encapsulated
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 DICOM document options
50 document title:
51 +t --title [t]itle: string (default: empty)
53 document title
54 +cn --concept-name [CSD] [CV] [CM]: string (default: empty)
56 coded representation of document title defined by coding
57 scheme designator CSD, code value CV and code meaning CM
58 patient data:
60 +pn --patient-name [n]ame: string
62 patient's name in DICOM PN syntax
63 +pi --patient-id [i]d: string
65 patient identifier
66 +pb --patient-birthdate [d]ate: string (YYYYMMDD)
68 patient's birth date
69 +ps --patient-sex [s]ex: string (M, F or O)
71 patient's sex
72 study and series:
74 +sg --generate
76 generate new study and series UIDs (default)
77 +st --study-from [f]ilename: string
79 read patient/study data from DICOM file
80 +se --series-from [f]ilename: string
82 read patient/study/series data from DICOM file
83 instance number:
85 +i1 --instance-one
87 use instance number 1 (default, not with +se)
88 +ii --instance-inc
90 increment instance number (only with +se)
91 +is --instance-set [i]nstance number: integer
93 use instance number i
94 burned-in annotation:
96 +an --annotation-yes
98 document contains patient identifying data (default)
99 -an --annotation-no
101 document does not contain patient identifying data
102 enhanced general equipment:
104 +mn --manufacturer [n]ame: string
106 manufacturer's name
107 +mm --manufacturer-model [n]ame: string
109 manufacturer's model name
110 +ds --device-serial [n]umber: string
112 device serial number
113 +sv --software-versions [v]ersions: string
115 software versions
116 3d model measurement units:
118 +mu --measurement-units [CSD] [CV] [CM]: string
120 measurement units with coding scheme designator CSD,
121 code value CV and code meaning CM (default: UCUM, um, um)
122 processing options
124 other processing options:
125 -k --key [k]ey: gggg,eeee="str", path or dictionary name="str"
127 add further attribute
128 output options
130 output file format:
131 +F --write-file
133 write file format (default)
134 -F --write-dataset
136 write data set without file meta information
137 group length encoding:
139 +g= --group-length-recalc
141 recalculate group lengths if present (default)
142 +g --group-length-create
144 always write with group length elements
145 -g --group-length-remove
147 always write without group length elements
148 length encoding in sequences and items:
150 +e --length-explicit
152 write with explicit lengths (default)
153 -e --length-undefined
155 write with undefined lengths
156 data set trailing padding (not with --write-dataset):
158 -p --padding-off
160 no padding (implicit if --write-dataset)
161 +p --padding-create [f]ile-pad [i]tem-pad: integer
163 align file on multiple of f bytes
164 and items on multiple of i bytes
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 behavior 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 one 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 stl2dcm utility uses the following exit codes when terminating.
211 This enables the user to check for the reason why the application
212 terminated.
213 general
215 EXITCODE_NO_ERROR 0
216 EXITCODE_COMMANDLINE_SYNTAX_ERROR 1
217 EXITCODE_MEMORY_EXHAUSTED 4
218 input file errors
220 EXITCODE_CANNOT_READ_INPUT_FILE 20
221 EXITCODE_NO_INPUT_FILES 21
222 EXITCODE_INVALID_INPUT_FILE 22
223 output file errors
225 EXITCODE_CANNOT_WRITE_OUTPUT_FILE 40
226
228 The stl2dcm utility will attempt to load DICOM data dictionaries
229 specified in the DCMDICTPATH environment variable. By default, i.e. if
230 the DCMDICTPATH environment variable is not set, the file
231 <datadir>/dicom.dic will be loaded unless the dictionary is built into
232 the application (default for Windows).
233 The default behavior should be preferred and the DCMDICTPATH
235 environment variable only used when alternative data dictionaries are
236 required. The DCMDICTPATH environment variable has the same format as
237 the Unix shell PATH variable in that a colon (':') separates entries.
238 On Windows systems, a semicolon (';') is used as a separator. The data
239 dictionary code will attempt to load each file specified in the
240 DCMDICTPATH environment variable. It is an error if no data dictionary
241 can be loaded.
242
244 Copyright (C) 2018 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
245 Germany.
246Version 3.6.4 Thu Nov 29 2018 stl2dcm(1)