Fusion: when to use the Intersect Vector Sets operator
The Intersect Vector Sets operator is like the Fuse Vector Sets operator with an additional step used to retain data that is coincident in the specified fuse space.
Both operators use a fuse space which is determined by user-specified axes which are defined before the fusion process. The resulting dataset is the intersection of the source datasets in these axes and only retains a single instance of any coincident vertices (multiple vertices that are perfectly coincident in the specified fuse space).
The extra step performed by Intersect Vector Sets places new vertices in the source datasets but retains any overlap that occurred on the axes of the fusion operation. So given this information, when should you and when shouldn't you use it?
- You should use it for draping tracks onto a surface. Most tracks frequently intersect themselves and therefore need the extra source dataset intersection step.
- You should use it whenever one of the input datasets overlaps itself in the defined fuse space, which occurs most commonly when the source vertices have been linked on axes other than the fuse space axes. For example, a track line is created by linking successive points together based on time rather than on a spatial attribute.
- It has no benefit for fusion of multiple topography/bathymetry data sets, since they do not overlap themselves spatially.
An in-depth article on the Intersect Vector Sets operator has been posted on our forum. If you have any questions about fusion and/or intersection then you can post them to the forum while you're there!
On the forum you will also find a downloadable example dataflow that contains an example of an intersection operation. Download it and try it for yourself!
More general information about fusion/intersect operator is available on these pages in the Eonfusion Manual:
