Road from Centerline Script - closed curves and Region Union problem

[rguo2017]

Hello,
I made this Road from Centerline script last year but had some problems…

1. This script is not working for closed curves. Trying to solve it, the script easily gets big and reduces efficiency. Since this is dealing with complex road networks. Every computation power counts. Any idea how to realize this effectively?

2. The Region Union component takes a lot of computation time…Any thoughts on working around it to significantly reduce the calculation time would be very much appreciated.
   

   

3. Maybe there is a completely different and better logic/structure to script this. I am all ears.

Please notes:
This script is made in Rhino 7 and needs at least Human and Elefront to run.

Thank you,
Rui
Road_auto_intersect_by_layer 1.00.gh (28.6 KB)

[René_Corella]

@rguo2017

This script is made in Rhino 7 and needs at least Human and Elefront to run.

Can you internalize stuff after your ‘trim tree’ component so you can get help without us having to install Human and Elefront?

*You’re also using Pufferfish, LunchBox, etc.

[René_Corella]

@René_Corella

Can you internalize stuff after your ‘trim tree’ component

JK, 'seems you’d have to internalize data prior to the pufferfish offset lol

Or, of course, wait for help from other plug-in enthusiasts

[rguo2017]

Thank you, René! I forgot to do that… I simplified the script and internalized the data. All the components are grasshopper-native components now.
Road_auto_intersect_by_layer 1.00 troubleshooting.gh (30.3 KB)

[Joseph_Oster]

@rguo2017

All the components are grasshopper-native components now.

Except for Pufferfish. I worked around that (purple group) but the circles engulf everything, the roads inside disappear.

Road_auto_intersect_2024Feb8a.gh (38.7 KB)

[René_Corella]

@Joseph:

[Joseph_Oster]

Yeah? I can see the problem, don’t know the solution?

Look further in the code to see how RUnion fails.

[René_Corella]

@Joseph_Oster

don’t know the solution?

Same

One approximate solution:
Road_auto_intersect_2024Feb8a (2).gh (31.8 KB)

Faster than RUnion but sacrifices resolution a bit - mesh quality can be bumped up, though - the fillets might be a bit shorter…

*Another one would be to extrude all roads as solids, boolean-union them (slow), get their intersection with the ground plane…BUT, when you do that, the solid union produces unwanted edges where solids unify - we can clean them up but the booleans will still be slow, so no bueno.

[Brian_Washburn]

If speed isn’t the top priority, Solid Union may be slow, but if you Merge Faces, you can avoid discretizing the curves.

[René_Corella]

awesome! Forgot about *FMerge

@Brian_Washburn

If speed isn’t the top priority,

LoL - 1.2 s … I love how anything above milliseconds is slow in gh world

[Joseph_Oster]

I resorted to SUnion too. Looks OK?

Road_auto_intersect_2024Feb8b.gh (27.4 KB)

[René_Corella]

@Brian_Washburn A {failed} attempt to beat you lol:

[Joseph_Oster]

@Brian_Washburn

If speed isn’t the top priority, Solid Union may be slow, but if you Merge Faces, you can avoid discretizing the curves.

No code?

[Brian_Washburn]

Apologies, code below:

Road_auto_intersect_by_layer 1.00 troubleshooting_BW.gh (32.9 KB)

[René_Corella]

@Brian_Washburn, I know it’s short/simple but your file doesn’t have your solution!

p.s.: still trying to beat your 1.2 s without solid unions nor meshing (discretizing the curves) like I did above:

[René_Corella]

@René_Corella

p.s.: still trying to beat your 1.2 s

lol so close but I quit for now - still discretized but just as shortcut to skip SUnion and RUnion…the actual ‘smooth’ curves were kept and shattered.

Road_auto_intersect_2024Feb8a (4).gh (43.8 KB)

@inno I think I invoked you

[inno]

if you are happy to end up with all Polylines, and are also happy to use Clipper2 plugin… here is another possibility (Clipper2 is so fast that the bottleneck becomes the Fillet component lol)

all closed curves, a single whole region

Road_auto_intersect_by_layer_inno.gh (25.3 KB)

@René_Corella you saw me typing

[Brian_Washburn]

@René_Corella It should be in there at the end, but it grabs the curve offsets from the Pufferfish add-in. This one does it all with native components.
Road_auto_intersect_by_layer_BW-Native.gh (19.8 KB)

This one does the faster mesh thing with all native components, but then cleans up the polylines so fillet works properly.
Road_auto_intersect_by_layer_BW-Native Mesh.gh (25.1 KB)

-Brian

[rguo2017]

Oh Wow! Thank you ALL for the input! This is a lot! I will try your approaches and let you know the results.

[Martin_Diviš]

Funny enough your amazing scripts work on NURB curves but for some reason give errors on simple ellipse but that is never used anyway IRL…

I was wondering whether it would be possible to keep some information about which curve degree would be filleted with which other so there could be a similar hierarchy to hose fillets.

Say I want the major-major, major-medium, and major-small would have x units of fillet for high-speed turns, the middle-middle, and middle-small would have y units of fillet, while small-small would have z units fillet.

I just sat down to the computer so I don’t have any progress myself yet. Will post if I get something.

EDIT. For now I resolved to classic attractors script but on larger geometries it might not be the best option and also in some cases the fillet point is closer to the small roads (extreme angles) so its not 100%.