1stl2dcm(1)                        OFFIS DCMTK                       stl2dcm(1)
2
3
4

NAME

6       stl2dcm - Encapsulate STL file into DICOM file format
7
8

SYNOPSIS

10       stl2dcm [options] stlfile-in dcmfile-out
11

DESCRIPTION

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

PARAMETERS

18       stlfile-in   STL input filename to be encapsulated
19
20       dcmfile-out  DICOM output filename
21

OPTIONS

23   general options
24         -h   --help
25                print this help text and exit
26
27              --version
28                print version information and exit
29
30              --arguments
31                print expanded command line arguments
32
33         -q   --quiet
34                quiet mode, print no warnings and errors
35
36         -v   --verbose
37                verbose mode, print processing details
38
39         -d   --debug
40                debug mode, print debug information
41
42         -ll  --log-level  [l]evel: string constant
43                (fatal, error, warn, info, debug, trace)
44                use level l for the logger
45
46         -lc  --log-config  [f]ilename: string
47                use config file f for the logger
48
49   DICOM document options
50       document title:
51
52         +t   --title  [t]itle: string (default: empty)
53                document title
54
55         +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
59       patient data:
60
61         +pn  --patient-name  [n]ame: string
62                patient's name in DICOM PN syntax
63
64         +pi  --patient-id  [i]d: string
65                patient identifier
66
67         +pb  --patient-birthdate  [d]ate: string (YYYYMMDD)
68                patient's birth date
69
70         +ps  --patient-sex  [s]ex: string (M, F or O)
71                patient's sex
72
73       study and series:
74
75         +sg  --generate
76                generate new study and series UIDs (default)
77
78         +st  --study-from  [f]ilename: string
79                read patient/study data from DICOM file
80
81         +se  --series-from  [f]ilename: string
82                read patient/study/series data from DICOM file
83
84       instance number:
85
86         +i1  --instance-one
87                use instance number 1 (default, not with +se)
88
89         +ii  --instance-inc
90                increment instance number (only with +se)
91
92         +is  --instance-set [i]nstance number: integer
93                use instance number i
94
95       burned-in annotation:
96
97         +an  --annotation-yes
98                document contains patient identifying data (default)
99
100         -an  --annotation-no
101                document does not contain patient identifying data
102
103       enhanced general equipment:
104
105         +mn  --manufacturer  [n]ame: string
106                manufacturer's name
107
108         +mm  --manufacturer-model  [n]ame: string
109                manufacturer's model name
110
111         +ds  --device-serial  [n]umber: string
112                device serial number
113
114         +sv  --software-versions  [v]ersions: string
115                software versions
116
117       3d model measurement units:
118
119         +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
123   processing options
124       other processing options:
125
126         -k   --key  [k]ey: gggg,eeee="str", path or dictionary name="str"
127                add further attribute
128
129   output options
130       output file format:
131
132         +F   --write-file
133                write file format (default)
134
135         -F   --write-dataset
136                write data set without file meta information
137
138       group length encoding:
139
140         +g=  --group-length-recalc
141                recalculate group lengths if present (default)
142
143         +g   --group-length-create
144                always write with group length elements
145
146         -g   --group-length-remove
147                always write without group length elements
148
149       length encoding in sequences and items:
150
151         +e   --length-explicit
152                write with explicit lengths (default)
153
154         -e   --length-undefined
155                write with undefined lengths
156
157       data set trailing padding (not with --write-dataset):
158
159         -p   --padding-off
160                no padding (implicit if --write-dataset)
161
162         +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

NOTES

167   Attribute Sources
168       The  application  may  be  fed  with  some additional input for filling
169       mandatory (and optional) attributes in the new DICOM file like patient,
170       study and series information:
171
172       • The  --key  option can be used to add further attributes to the DICOM
173         output file.
174       • It is also possible to specify sequences, items and nested attributes
175         using the --key option. In these cases, a special 'path' notation has
176         to be used. Details on  this  path  notation  can  be  found  in  the
177         documentation of dcmodify.
178       • The --key option can be present more than once.
179       • The value part (after the '=') may be absent causing the attribute to
180         be set with zero length.
181       • Please be advised that the --key option is applied at the  very  end,
182         just  before  saving  the  DICOM  file, so there is no value checking
183         whatsoever.

LOGGING

185       The level of logging output of  the  various  command  line  tools  and
186       underlying  libraries  can  be  specified by the user. By default, only
187       errors and warnings are written to the  standard  error  stream.  Using
188       option  --verbose  also  informational messages like processing details
189       are reported. Option --debug can be used to get  more  details  on  the
190       internal  activity,  e.g.  for debugging purposes. Other logging levels
191       can be selected using option --log-level. In --quiet  mode  only  fatal
192       errors  are reported. In such very severe error events, the application
193       will usually terminate. For  more  details  on  the  different  logging
194       levels, see documentation of module 'oflog'.
195       In  case  the logging output should be written to file (optionally with
196       logfile rotation), to syslog (Unix) or the event log  (Windows)  option
197       --log-config  can  be  used.  This  configuration  file also allows for
198       directing only certain messages to a particular output stream  and  for
199       filtering  certain  messages  based  on the module or application where
200       they are generated.  An  example  configuration  file  is  provided  in
201       <etcdir>/logger.cfg.

COMMAND LINE

203       All  command  line  tools  use  the  following notation for parameters:
204       square brackets enclose optional  values  (0-1),  three  trailing  dots
205       indicate  that multiple values are allowed (1-n), a combination of both
206       means 0 to n values.
207       Command line options are distinguished from parameters by a leading '+'
208       or  '-' sign, respectively. Usually, order and position of command line
209       options are arbitrary (i.e. they  can  appear  anywhere).  However,  if
210       options  are  mutually exclusive the rightmost appearance is used. This
211       behavior conforms to the  standard  evaluation  rules  of  common  Unix
212       shells.
213       In  addition,  one  or more command files can be specified using an '@'
214       sign as a prefix to the filename (e.g. @command.txt).  Such  a  command
215       argument  is  replaced  by  the  content of the corresponding text file
216       (multiple whitespaces are treated as a  single  separator  unless  they
217       appear  between  two  quotation marks) prior to any further evaluation.
218       Please note that a command file cannot contain  another  command  file.
219       This  simple  but  effective  approach  allows  one to summarize common
220       combinations of options/parameters and  avoids  longish  and  confusing
221       command lines (an example is provided in file <datadir>/dumppat.txt).

EXIT CODES

223       The  stl2dcm  utility  uses  the following exit codes when terminating.
224       This enables the user to check  for  the  reason  why  the  application
225       terminated.
226   general
227       EXITCODE_NO_ERROR                 0
228       EXITCODE_COMMANDLINE_SYNTAX_ERROR 1
229       EXITCODE_MEMORY_EXHAUSTED         4
230   input file errors
231       EXITCODE_CANNOT_READ_INPUT_FILE   20
232       EXITCODE_NO_INPUT_FILES           21
233       EXITCODE_INVALID_INPUT_FILE       22
234   output file errors
235       EXITCODE_CANNOT_WRITE_OUTPUT_FILE 40

ENVIRONMENT

237       The  stl2dcm  utility  will  attempt  to  load  DICOM data dictionaries
238       specified in the DCMDICTPATH environment variable. By default, i.e.  if
239       the   DCMDICTPATH   environment   variable   is   not   set,  the  file
240       <datadir>/dicom.dic will be loaded unless the dictionary is built  into
241       the application (default for Windows).
242       The   default   behavior   should  be  preferred  and  the  DCMDICTPATH
243       environment variable only used when alternative data  dictionaries  are
244       required.  The  DCMDICTPATH environment variable has the same format as
245       the Unix shell PATH variable in that a colon (':')  separates  entries.
246       On  Windows systems, a semicolon (';') is used as a separator. The data
247       dictionary code will  attempt  to  load  each  file  specified  in  the
248       DCMDICTPATH  environment variable. It is an error if no data dictionary
249       can be loaded.
251       Copyright (C) 2018-2022 by OFFIS e.V., Escherweg  2,  26121  Oldenburg,
252       Germany.
253
254
255
256Version 3.6.7                   Fri Apr 22 2022                     stl2dcm(1)
Impressum