Issue with Point at Intersection Node and Point By Direction and Distance from Origine Node

Question

Hi, 
 I have 2 separate issues. 
 
 Issue 1: (Node: "Point - AtIntersection) 
 
 (Refer the image below) I am trying to find an intersection point between white vertical lines and the green dotted line. As can be seen in the image below, white vertical lines are projected on green lines. I am expecting a single point at each intersection between white lines and green line, which I am getting apart from a few locations, where I am getting some random points on green lines. Can anyone explain why these points are generated where there is no intersection point there!

Issue 2: (Node: "Point - ByDirectionAndDistanceFromOrigin) 
 (Refer Image Below) I am trying to place a point using Point bydirectionanddistancefromorigin node where I am inputting the distance manually and using Y Direction from a CS. I am getting (red) points correctly at most of the location apart from where the alignment line changing curve. For some reason at few locations, I am getting offset points in a rendom direction even though I have provided Y direction from the corresponding CS. Please note: CS Placement is by spacing along the curve and spacing is coming from an excel sheet.

Please let me know if you need more information. 
 
 Regards, 
 
 Jaimin Patel

Sandeep Punewar · Accepted Answer

Thanks Jaimin, I figured it out as a regression where intersection points are not generated on mitered non-planar polyline, I filed defect for this issue.

Mueller · Answer

Hi Jaimin, 
 In Update 5 you can clean up the intersection issue by implementing two changes: 
 (1) change the Length of the node line_Reference so it is long enough to intersect with all the PolyLine nodes with which it needs to intersect. For example, set the Length to 60. 
 (2) on node point_Reference_Pile_TOP_DT switch off the input property TreatLinesAsInfinite. 
 This eliminates issue 1. 
 When you generate the Point.ByDirectionAndDistanceFromOrigin nodes you are leveraging replication. However, your inputs are not well-aligned lists. For example, on point_offset_DT_SET9 the Origin input is a subset point_Reference_Pile_TOP_DT.Sublist(190, 83). The direction, though, is not a corresponding subset. It uses all CS_Piles_Placement.YDirection sub-nodes. When using (CS_Piles_Placement.Sublist(190, 83)).YDirection instead, then the direction is aligned the way you correctly seem to expect: 
 Before: 
 
 After: 
 
 This would need to be applied to all the point_offset_DT_xxxx nodes: 
 Before: 
 
 After: 
 
 The alert about elements outside of the Solids Working Area is important because it indicates that some modeling operations may not be able to be completed accurately, and it means that drawing generation may not succeed in unifying building components as users would expect. For that, modeling objects need to be within the Solids (Working) Area. The best way to avoid this challenge is by using geo-coordination to align the modeling area with the center of the design file (near its origin at 0, 0, 0). Within computational design (GenerativeComponents) one could insert the inverse transform as a CoordinateSystem using the negative X and Y values from a datum in the reference. Again, better would be to follow the recommended geo-coordination workflow. 
 Please let me know whether the changes suggested above are successful. 
 Best success, 
 Volker

Marc Thomas · Answer

For further information and background about the Solids Working Area please refer to Series Index - Setting Up in the Real World .

Issue with Point at Intersection Node and Point By Direction and Distance from Origine Node

Issue 1: (Node: "Point - AtIntersection)

Issue 2: (Node: "Point - ByDirectionAndDistanceFromOrigin)

Top Replies