i try to sort lines which are not entirely in one plane, so either polycurve or Group Curves node of archilab cannot be used, any insight?
if you should have any kind of help with these kind of information, you should share what you try and dataset…it will totally be impossible to help from there what you show and give us, just a good advice
But like almost? Maybe pull them on the same plane or isn’t that an option?
this is just simple case, basically they are combination of horizontal lines and vertical lines and sometimes sloped lines, in fact, i saw someone had solution before in this forum but i cannot dig it out, just wonder if there is anything like 3D polycurve?
@ning.zhouHNQLJ then share these curves as rvt and we can probably,help dont think the community build that sittuation up again, then you will have better luck…good luck
thanks sovitek, you are great help in this forum and very appreciated! uploaded RVT w/ curves FYI
lines.rvt (444 KB)
yeah thats the way 
lets hope someone take a look at that, i dont have time right now, maybe later, but now you at least have have a change for something help:) great
PolyCurve.ByGroupedCurves perhaps?
you could try play with something here, for shatter you could get one in ampersand package or try build your own as something here…
thanks all, mostly work well for sovitek’s solution, for instance, not work if some lines are relatively short and gaps between lines are big.
PolyCurve.ByGroupedCurves only works if those lines are joined already.
looks like Springs node LineLoop.Merge works well (only for IronPython2, not CPython3).
The later Dynamo versions should have a ‘join tolerance’ on it which should allow closing those gaps without the ‘extend’ aspect.
That said if some curves are ‘short’ you might have other issues to deal with. It may be more consistent to include the joints and fixtures in the selection, derive the L shapes therefrom based on the connector locations, and use those to close the sequence.
1 Like
thanks jacob, quick testing results in list of polycurves → one polycurve per curve, not sorted
Which build of Revit are you in?
2024
1 Like
So I still think you want to revise this workflow - the root selection (or creation) of the curves could (should) include the connectors as well.
Here is the OOTB workflow I was noting using the ByGroupedCurves method:
Note that as you have gaps exceeding the shorted line segment you’re getting pretty significant gaps - this is why I think you want to revist the initial generation method be it ‘routing’ or ‘from a selected system’.
Your alternative is to find a curve in the set and interate to find the ‘closest’ to one end or the other that is within yoru desired tolerance, and build the connection from there. It’s doable, but it’s slow and ugly.
1 Like