Images

Data conversion conventions in ImageViz

Open Inventor supports some data types that are not supported in ImageViz and vice versa. More...

Classes
class	SoFileDataAdapter
	Image data adapter for data in a file. More...
class	SoImageDataAdapter
	Abstract base class for all ImageViz image data adapter classes. More...
class	SoMemoryDataAdapter
	Image data adapter for in memory data. More...
class	SoProxyDataAdapter
	Proxy image data adapter for in memory data. More...
class	SoVolumeReaderAdapter
	Image data adapter for an SoVolumeReader. More...
class	SoVRImageDataReader
	Reads volume from an SoImageDataAdapter. More...
class	SbChannelList
	List of channel to extract. More...
class	SbImageDataAccessor
	Class used to retrieve data from an SoImageDataAdapter. More...
class	SbImageDataAdapterHelper
	Helper class for SoImageDataAdapter. More...
class	SbImageDataType
	Basic class representing multi channel DataType. More...
class	SbImageDataVoxel
	Utility class used to safely access channels of a buffer. More...

Detailed Description

Data conversion conventions in ImageViz

Open Inventor supports some data types that are not supported in ImageViz and vice versa.

For example, Open Inventor supports 32-bit unsigned integer values, but ImageViz does not. Likewise, ImageViz supports label types, which is an unknown notion in Open Inventor.

Given the diversity of types, the following rules are used to allow type conversions when the data are accessed by the application or by an engine.

1. Values outside the destination range are clamped.
2. For binary type, values equal to 0 are set to INACTIVE and those are different from 0 are set to ACTIVE.
3. For color types, transparency is not supported by ImageViz and must be removed.
4. For floating point types to integer types conversion, the floating point value is truncated. Example: 1.8f becomes 1.
5. Double precision floating point type is not supported by ImageViz. It must be casted to simple precision floating point type with the suitable loss of precision.
6. Conversion from signed to unsigned types and other downcasts respect rule #1.

The conversion conventions are mentioned here because no warning is issued when data is converted. This is necessary to avoid an avalanche of warning messages.