Hi, I am working on a 3d model based on people’s vitality in a certain space, what I want to do is to use people’s vitality as the heat map and then extrude the points on the map according to the level of the vitality, which means the central red part would be the highest one, and the blue part would be the lowest one, and the final shape will be made by several triangles. I wonder if there is any plug-ins in grasshopper can do this, and how? Thank you many times!!!
I have done a manual example of what I want it to be in the following photo image|180x500
1.You have a DataTree of co-planar points where points are at [0] and some value at [1]. Or alternatively 2 Lists (points/doubles) matching 1:1.
2. You want to do a triangulation on points (easy: classic Delauney) yielding a mesh.
3. Then you want to “distort” each mesh vertex by adding a Z that corresponds to the value associated with the vertex.
Hi! Thank you for your reply.
Actually I don’t have a precise data of the “heat map”, cause it’s based on which part I want it to be the most active one after I designed it, so I just draw the map manually for now. I think the 2nd and 3rd points you raised are basically what I want to do. I wonder if there is any tool to yield this kind of map without a specific data? If the answer is no, then let’s say I can do these “heat map” manually, but are there any tools to extrude the height according to the map?
NOTE: Gh does business via some custom data structure called DataTree. The vast majority of users they don’t actually understand what this thing is. The bad news are that without some knowledge on that matter even this very simple script (native components only) it could be rather difficult to understand (especially the part with indices).
Thank you so much!
Maybe I didn’t explain my question very well so that caused your confusion, but thank you anyway cause I think this is basically what I want.
No harm done. The problem with pros … is … that … well … they become like @% robots (0/1 and the likes) and therefor require very explicit problem description.
Anyway … added some visual indication (what goes where)
