Documentation for XCEDE2 - xcede-2.0-core.xsd - Complex Type binaryDataDimension_t

# Documentation for XCEDE2

### Complex Type: binaryDataDimension_t

#### [Table of contents]

Super-types: | None
Sub-types: | mappedBinaryDataDimension_t (by extension)

Name | binaryDataDimension_t
Used by (from the same schema document) | Complex Type dimensionedBinaryDataResource_t
Abstract | no
Documentation | This element stores information about one of the N dimensions in the data record. Multiple instances of this element are ordered from fastest-moving to slowest-moving. These elements provide information to describe the size (in data elements) of the N-dimensional bounding box for the data, and in some cases to describe the mapping of indexes within this bounding box to 'real-world' coordinates.

XML Instance Representation
<...
label=" xs:string [0..1]

'This is a label for the dimension. The first three spatial dimensions (or however many exist) must be labeled, in order, \'x\', \'y\', and \'z\'. The first temporal dimension must be labeled \'t\'.'

"
splitRank=" xs:string [0..1]

'If this attribute exists, this dimension is a \"split\" dimension, and this dimension must be \"merged\" with one or more other dimensions (with the same label) before presenting the data to the application. This is useful, for example, if the data is stored in Siemens\' Mosaic DICOM format, where slices of a 3-D volume are arranged to look like they are tiled onto a square 2-D area. In this case, what would normally be called the \'z\' dimension has two forks, one that occurs before the \'y\' dimension (the first row in the data covers the first row of several slices), and one that occurs after the \'y\' dimension. If, as in this case, there are two or more dimensions that should be merged into one, both component dimensions should have the label \'z\', but have splitRank attributes \"1\" and \"2\", which specifies the order in which all \'split\' dimensions of the same label will be merged. After merging, the resultant \'z\' dimension element should contain the same children of the highest-ranked split \'z\' dimension, except for the \'size\' element, which will be the product of the sizes of all \'z\' split dimensions. The position of the resultant dimension should be the position of the highest-ranked \'z\' split dimension. The data itself should also be reordered to reflect the new dimension structure.'

"
outputSelect=" xs:string [0..1]

'In the same way that the \'splitRank\' attribute allows you to specify dimensions that should be merged before presenting the data to an application, this attribute specifies a data filter along this dimension. If this attribute exists, it should contain a whitespace-separated list of indices (indexed starting at 0). Only data points along this dimension that occur in the index list should be presented to the application. Likewise, the \'size\' of the dimension, after selection, should be updated to reflect the new size of this dimension (which should be the number of indices in the content of this attribute).'

">
<size> xs:int </size> [1]

'The number of elements in the data along one traversal of this dimension.'

</...>
Diagram
Schema Component Representation
<xs:complexType name="binaryDataDimension_t">
<xs:sequence>
<xs:element name="size" type=" xs:int "/>
</xs:sequence>
<xs:attribute name="label" type=" xs:string "/>
<xs:attribute name="splitRank" type=" xs:string "/>
<xs:attribute name="outputSelect" type=" xs:string "/>
</xs:complexType>