Maps NodeRepresentation's vertexKey
to attachments (if available)
There is no guarantee for a vertexKey
to be part of this map.
Bend drawings in HTML format
Each HTML file is self-contained, i.e. no external resources need to be hosted for a file to be viewable via a browser.
This requires the respective feature to be available for the active license.
There is no guarantee for a vertexKey
to be part of this map.
Maps NodeRepresentation's vertexKey
to DXF-file-content (if available)
Note: Depending on a NodeRepresentation's underlying WorkStepType
the DXF file content may vary.
For NodeRepresentations of type sheetCutting
the map contains a DXF file defining the sheet cutting contour.
For NodeRepresentations of type sheetBending
the map contains a DXF file defining both the sheet contour and bend-lines.
There is no guarantee for a vertexKey
to be part of this map.
Compressed counterpart to dxfs
Each DXF file content is compressed via zlib / Deflate.
There is no guarantee for a vertexKey
to be part of this map.
Maps NodeRepresentation's vertexKey
to GEO-file-content (if available)
There is no guarantee for a vertexKey
to be part of this map.
Compressed counterpart to geos
Each GEO file content is compressed via zlib / Deflate.
There is no guarantee for a vertexKey
to be part of this map.
Maps NodeRepresentation's vertexKey
to STEP-file-content (if available)
Note: Each STEP can be considered a sub-set of the input-STEP file.
There is no guarantee for a vertexKey
to be part of this map.
Compressed counterpart to inputSteps
There is no guarantee for a vertexKey
to be part of this map.
Maps NodeRepresentation's vertexKey
to STEP-file-content (if available)
Note: Each STEP is generated based on computations in WSi4.
There is no guarantee for a vertexKey
to be part of this map.
Compressed counterpart to outputSteps
Each STEP file content is compressed via zlib / Deflate.
There is no guarantee for a vertexKey
to be part of this map.
Maps NodeRepresentation's vertexKey
to PNG-file-content (if available)
There is no guarantee for a vertexKey
to be part of this map.
Maps a set of NodeRepresentation's vertexKey
s to WSi4-file-content
Currently, sub graphs are created for all undirected connected components of the graph.
Example (1): Two Sub-graphs will be created: - [v0, v1, v2, v3, v4, v5, v6, v7] - [v8, v9]
.--> v0 ---> v1 --.
/ \
v2 ---> v3 ---> v4 -----> v5 ---> v6
\ /
`--> v7 ----------'
v8 ---> v9
Example (2): One sub-graph will be created: - [v0, v1, v2, v3, v4, v5, v6, v7]
.--> v0 ---> v1
/
v2 ---> v3 ---> v4 -----> v5 ---> v6
\ /
`--> v7 ----------'
Maps NodeRepresentation's vertexKey
to SVG-file-content (if available)
Note: Depending on a NodeRepresentation's underlying WorkStepType
the SVG file content may vary.
There is no guarantee for a vertexKey
to be part of this map.
Compressed counterpart to svgs
Each SVG file content is compressed via zlib / Deflate.
There is no guarantee for a vertexKey
to be part of this map.
Generated using TypeDoc
Node resources
Note: Depending on the type of a node various resources are exported.
Resource entries are accessible via NodeRepresentation's
vertexKey
.