Dear Community,
It would be extremely helpful if the Grasshopper Join Curves component had an “i” (Index) output alongside its “C” (Curves) output. This new output would provide the input component indices for each joined curve, structured in a data tree synchronized with the joined curves on output “C”.
Is there any chance of seeing this feature in an upcoming Grasshopper release? It would be invaluable for data-driven definitions where attributes from the original input curves need to be inherited by the resulting joined curves.
Currently, using proximity-based methods like Closest Point becomes extremely slow when dealing with large datasets (e.g., 100,000 curves).
In the meantime, could anyone share a fast workaround or script (C#/Python) that outperforms the Closest Point approach?
Thank you, Frank