xml2dsr [options] xmlfile-in dsrfile-out
An appropriate XML file can be created using the dsr2xml tool (option +Xn recommended to add XML namespace declaration to the root element).
xmlfile-in XML input filename to be converted (stdin: "-") dsrfile-out DICOM SR output filename
-h --help
print this help text and exit
--version
print version information and exit
-v --verbose
verbose mode, print processing details
-d --debug
debug mode, print debug information
encoding:
+Ee --template-envelope
template element encloses content items
validation:
+Vs --validate-schema
validate XML document against Schema
(not with --template-envelope)
+Vn --check-namespace
check XML namespace in document root
output file format:
+F --write-file
write file format (default)
-F --write-dataset
write data set without file meta information
output transfer syntax:
+t= --write-xfer-same
write with same TS as input (default)
+te --write-xfer-little
write with explicit VR little endian TS
+tb --write-xfer-big
write with explicit VR big endian TS
+ti --write-xfer-implicit
write with implicit VR little endian TS
+td --write-xfer-deflated
write with deflated expl. VR little endian TS
post-1993 value representations:
+u --enable-new-vr
enable support for new VRs (UN/UT) (default)
-u --disable-new-vr
disable support for new VRs, convert to OB
group length encoding:
+g= --group-length-recalc
recalculate group lengths if present (default)
+g --group-length-create
always write with group length elements
-g --group-length-remove
always write without group length elements
length encoding in sequences and items:
+e --length-explicit
write with explicit lengths (default)
-e --length-undefined
write with undefined lengths
data set trailing padding (not with --write-dataset):
-p= --padding-retain
do not change padding (default if not --write-dataset)
-p --padding-off
no padding (implicit if --write-dataset)
+p --padding-create [f]ile-pad [i]tem-pad: integer
align file on multiple of f bytes
and items on multiple of i bytes
BasicTextSR 1.2.840.10008.5.1.4.1.1.88.11 EnhancedSR 1.2.840.10008.5.1.4.1.1.88.22 ComprehensiveSR 1.2.840.10008.5.1.4.1.1.88.33 ProcedureLog 1.2.840.10008.5.1.4.1.1.88.40 MammographyCADSR 1.2.840.10008.5.1.4.1.1.88.50 KeyObjectSelectionDocument 1.2.840.10008.5.1.4.1.1.88.59 ChestCADSR 1.2.840.10008.5.1.4.1.1.88.65 XRayRadiationDoseSR 1.2.840.10008.5.1.4.1.1.88.67
Please note that currently only mandatory and some optional attributes are supported.
Command line options are distinguished from parameters by a leading '+' or '-' sign, respectively. Usually, order and position of command line options are arbitrary (i.e. they can appear anywhere). However, if options are mutually exclusive the rightmost appearance is used. This behaviour conforms to the standard evaluation rules of common Unix shells.
In addition, one or more command files can be specified using an '@' sign as a prefix to the filename (e.g. @command.txt). Such a command argument is replaced by the content of the corresponding text file (multiple whitespaces are treated as a single separator) prior to any further evaluation. Please note that a command file cannot contain another command file. This simple but effective approach allows to summarize common combinations of options/parameters and avoids longish and confusing command lines (an example is provided in file share/data/dumppat.txt).
The default behaviour should be preferred and the DCMDICTPATH environment variable only used when alternative data dictionaries are required. The DCMDICTPATH environment variable has the same format as the Unix shell PATH variable in that a colon (":") separates entries. The data dictionary code will attempt to load each file specified in the DCMDICTPATH environment variable. It is an error if no data dictionary can be loaded.