Terrain surface maker

Hey everyone,

I've been using the terrain surface maker from livecomponents ( http://livecomponents-ny.com/2010/04/29/2_3-terrain-surface-maker/ ) for a while but recently updated to GH 0.9.0014 to load Rabbit, and now the definition broke down. Somewhere between the new graft tree tool and the new PCX (curve/plane intersection) it breaks down. I also edited the definition to run in both X (curve degree = 1) and Y (curve degree = 3) direction to solve issues with crazy bezier curves.

I'm sure there is a very simple solution, or maybe a better tool for creating a surface from contour lines? I've looked into rhinoterrain and I don't think it's the tool for me, I simply won't have the need for it enough. I suppose I could use Revit and export the geometry, but I'm just frustrated this doesn't work in Grasshopper anymore... Google doesn't have the detail I need either.

Here's a link to my model I'm trying to make work.

https://www.dropbox.com/sh/d8nmhs6um1lwlzn/WOoZAGBAgQ

Any assistance is greatly appreciated. As a student, this definition has been very helpful with making detailed site models with a CNC router and I'd like to be able to help other people out again.

Attachments:

map_loft_SPM01.ghx, 311 KB

Replies to This Discussion

Permalink Reply by Yoann Mescam (Systemiq) on October 9, 2012 at 10:37am

It looks like the PCX has troubles with big numbers, try setting unit to kilometers and scale model 0.001 in rhino.

Or do BCX with very large surfaces on your frames.

Or/and move all curves to the origin.

Permalink Reply by Ryan on October 9, 2012 at 10:48am

You ROCK!

I'll have a look in a bit, just heading to afternoon class.

Thank you SO much for having a look, I really appreciate it.

Permalink Reply by Ryan on October 9, 2012 at 5:39pm

Looks great, your method works to map the intersections but I'm just missing that one component you're using (X[x.y]R) part that seems to be telling whether to run along x or y axis? Forgive my beginner knowledge...

Permalink Reply by Yoann Mescam (Systemiq) on October 9, 2012 at 6:55pm

This component is just the new Expression component, given the point P, typing P.x returns the x coordinate. You can use the usual Decompose (pComp) component too.

I just used it because it looks nicer and more compact. I also used pShift instead of PathMapper. Other than that it is the same definition.

Permalink Reply by Ryan on October 9, 2012 at 7:00pm

Awesome! Thanks again for the help.

Sometimes I wish I had the time to really dig into GH, but am quickly reminded that I just don't have the mind for it. I'm glad there is such a strong community of users willing to help though because GH is really an amazing program.

Thanks again,

Permalink Reply by Benjamin Baliti on October 17, 2012 at 9:04pm

Hi Systemig,

Sorry to jump on the bandwagon, but I'm having pretty much exactly the same problem as Ryan. I am a complete beginner with grasshopper and at this stage only really copying other peoples' definitions.

As such I tried all of your tips, and even tried recreating the changes you made, but with no luck. It seems that there is a problem/bug with the curve plane intersection, having read about similar issues elsewhere.

Is there any way at all you could help me? I would hugely appreciate it.

In the rhino file I made a simplified set of contours just to test the definition, but I included both.

Attachments: