algorithmic modeling for Rhino
Hi!
I'm sorry if this has already been answered, I tried searching the forums but to no avail. I was wondering why some of the areas turn out incomplete? Sometimes it works perfectly and sometimes I get these buggy areas that ruin the entire terrain I'm trying to model. Why is this and how can I fix it? This particular area contains a mountain top sloping steeply down into a lake, if that has anything to do with things. Thanks for any input!
Tags:
Hi Amanda,
Thank you for opening the topic.
Is it possible that you attach your .gh file please?
Hi Amanda,
I generated a terrain based on the coordinates provided in your screenshot, and got the same results as you did.
The problem was with _source = 1 ("ALOS World 3D 30m").
"ALOS World 3D 30m" terrain source if the first version of its release, therefor it can contain issues like these in certain places: locations with no data (like this lake) and incorrect data on the very shores of the lake. I assume its version 2 should fix all of this issues.
Until then you can use the .gh definition attached below. It will assign a certain elevation value to all terrain points in specific range. I set this value to 315 for all points in range of -9999 to 315. If you continue having "pockets" or "holes" around the lake shore, you can try experimenting and increasing the "315" value to some larger number. Say, 320 or 330. These values are always in meters.
Let me know if this help:
And please accept my apologies for the late reply. It is always useful to attach the .gh definition as well.
Welcome to
Grasshopper
© 2024 Created by Scott Davidson. Powered by