Main Panel¶
The main panel contains a "Default Settings" tab. This tab contains the default object specifications that pitch in if they are not explicitly specified in the respective object type tabs.

genre | FileMain |
author | Axel Newe |
package | Community/General |
dll | MLPDF |
definition | MLPDF.def |
see also | WEMSaveAsU3D, ComposeWEMDescriptionForU3D |
keywords | PDF, U3D, WEM, XMarker, Fiber |
This module creates Universal 3D (U3D) files that can be imported into Portable Document Format (PDF) files for creating 3D annotations.
Connect the inputs with the point set data (XMarkerList or ColoredMarkerList), the line set data (XMarkerList or ColoredMarkerList plus IndexPairList) and the mesh data (WEMs), specify the output (see "Details") and the file name and click the "Save" button.
The module creates U3D files as defined in Standard ECMA-363 (Universal 3D File Format), 4th edition (June 2007).
The following U3D elements can be added:
The geometry data is fed in via the input connectors. However, since input data can be reused for multiple output models, the output models must be specified. This happens in the three tabs "Point Clouds", "Line Sets" and "Meshes". The general output geometry specification is the same for all three model types, but some details vary.
Common Specification
The general specification follows an XML-like principle. A new object specification is started with a single tag and the specification parameters are embraced with opening and closing tags.
The common tags are:
These common tags are available for all object types. However, some object types do not evaluate all tags (e.g., a Point Cloud does not evaluate the <Color> tag). This is because the same specifications can also be used for other (non-U3D) export formats. In addition, future versions of the U3D standard might support the respective settings.
Colors are specified using triples (RGB) or quadrupels (RGBA) of floating point numbers bewteen 0 and 1.
Point Cloud Specification
A new point cloud is started by the <PointSet> tag. A closing tag is not necessary
The geometry data is taken from the inPointPositions input field, which accepts XMarkerLists or ColoredMarkerLists. Use the <PositionTypes> tag to filter which positions (Type ID numbers) of the input list shall be used. If no <PositionTypes> tag is specified, all positions are used. Multiple position types may be separated by commas.
Line Set Specification
A new line set is started by the <LineSet> tag. A closing tag is not necessary
The geometry data is taken from the inLinePositions input field (XMarkerList or ColoredMarkerList) and the inLineConnections input field (IndexPairList). Use the <PositionTypes> tag to filter which positions (Type ID numbers) of the input positions list shall be used. If no <PositionTypes> tag is specified, all positions are used. Use the <ConnectionTypes> tag to filter which connections/edges (Type ID numbers) of the input connections list shall be used. If no <ConnectionTypes> tag is specified, all connections are used. Instead of specifying Type ID numbers, the <ConnectionTypes> tag may also contain the simple keyword. In this case, the connections are generated automatically by simply connecting each position with the next in the list. Multiple position types and connection types may be separated by commas.
Mesh Specification
A new mesh is started by the <Mesh> tag. A closing tag is not necessary
The geometry data is taken from the inWEM input field, which accepts a WEM. Use the <WEMLabel> tag to filter which WEM (selected by its Label) of the input WEM shall be used.
Meta Data
U3D allows for inclusion of meta data. Since meta data is no geometry data, it is specified purely via the UI.
A new meta data entry is started by the <MetaData> tag. A closing tag is not necessary.
Each meta data entry needs a key and a value. These are specified using the
tags.
There is a simple mode available, which creates default 3D models from the input data. If you only connect input geometry data (e.g. a WEM or a positions list) and activate the respective "Enable Simple Mode" checkbox, all geometry data is automatically converted into 3D objects using default settings. In case of WEMs, the WEM description is also parsed. You can use the ComposeWEMDescriptionForU3D module to create suitable WEM descriptions.
You can use a FiberSetToXMarker module to connect a fiber set to the inLinePositions input.
Have a look at the example network which demonstrates all features.
This module requires the MLBaseListExtensions.
The main panel contains a "Default Settings" tab. This tab contains the default object specifications that pitch in if they are not explicitly specified in the respective object type tabs.
For your convenience, the module has a built-in specification generator. You can use it to specify 3D object settings using standard MeVisLab fields. Use the "Add" button to add the currently displayed specification to the respective specifications in the main module.
Contains the point cloud positions geometry data. Allowed: XMarkerList and ColoredMarkerList.
Values:
Title | Name |
---|---|
Point Cloud | SPECTYPE_POINTCLOUD |
Line Set | SPECTYPE_LINESET |
Mesh | SPECTYPE_MESH |
Meta Data | SPECTYPE_METADATA |
Values:
Title | Name |
---|---|
Not Visible | VISIBILITY_NOTVISIBLE |
Front Visible | SPECTYPE_FRONTVISIBLE |
Back Visible | SPECTYPE_BACKVISIBLE |
Front & Back Visible | SPECTYPE_FRONTANDBACKVISIBLE |