I have a bunch of line pairs where each individual line has been assigned a UUID and is stored in a list: UUID_PARTS{} with indices 0 and 1.
Also have some aggregates of three which contain the same lines as the pairs, plus an additional line. They also have the same list attribute, where the indices are 0, 1, 2.
The pairs and trios of lines are currently separated, but could be combined if needed.
Have tried both list-based feature merger and regular feature merger on UUID_PARTS{0} or UUID_PARTS{1} with various settings, but no luck. My goal is for this to be flexible enough so it does not matter what index the matching UUIDs are and also handle aggregates with more than three parts, if possible. Any ideas?
Thanks,
@larue

This is a wall that changes width and shares a common boundary. I split the longest line and create separate bounding boxes which are used to generate Wall Family info for Revit. The problem is that my process (using FuzzyParallelLineFinder) creates line pairs that need to be filtered out before the bounding box stage.
I also tried the ListBasedMerger (without Concatenator), but I am unclear on how it should be configured. Was hoping to just compare Requestor and Supplier lists and merge when it came upon a feature that matched the UUID pair with the trio. Any ideas?
I think I figured it out. I first changed the aggregator to generate lists of the original UUIDs, then exploded the supplier side UUID list only, using the requestor as the main list by which to "merge" Not sure how universal this is, but it is working for me so far. I am using LastBasedFeatureMerger as a filter and sending only unused suppliers on their way.