Way to use list of layers in Human..

I've had very good luck using human to deploy blocks. What I'm wondering is if there is any conceivable way to deploy a list of layer names (blocks) that correspond with the list of geometries.

For example, deploying a single block on multiple points works well for me. The data for the points is from a shapefile, and the information regarding elevation and angle comes from a coresponding table:

What I am wishing for is to be able to use an equal length list of layer names such that the correct block is mapped on each corresponding box. What's pictured below was a test of this thought, but it deployed 235 blocks on each of the 235 boxes, not the correct block on each point--this is a subset of a larger data set.

The script is for deploying telephone poles in an urban scene--we have geolocated data for each pole and its equipment [E.G., light, transformer, etc.). The obvious workaround is to deploy the script for groups of poles, but I would probably look at using a python script instead at that point, because for some purposes we will have tables that change (E.G., different scenarios). The tables and geodata comes out of R, and can be in any form required.

Curious if I'm understanding this limitation correctly, and if there is any conceivable way to do what I'm trying to do. I've attached a GH file with internalized data coresponding to the above as well as a simplified version of the pole file with the appropriate layers.

I'm new to grasshopper, and this is my first post here, so appologies if I'm missing something obvious. Thanks in advance,

Peter

Attachments:

Pole_Question.gh, 22 KB
Simplified_Pole.3dm, 4.6 MB

Replies to This Discussion

Permalink Reply by Peter Stempel on March 17, 2016 at 12:59pm

I've created a python script that does the essential functions of inserting and orienting the block selected from a list corresponding to the points--which is the logical solution, however, I'd still be interested in the answer regarding human if anyone has a thought.

Permalink Reply by Andrew Heumann on March 20, 2016 at 12:31pm

You appear to be using a very old version of Human. I have deprecated the "Objects by layer" component in favor of the "Dynamic pipeline" - which can accept lists of layers. See the attached file for an updated version of what you're trying to do (and be sure to download the latest version of human from food4rhino before opening it.)

Permalink Reply by Peter Stempel on March 22, 2016 at 9:47am

Thanks Andrew,

This is great.

Permalink Reply by Peter Stempel on April 4, 2016 at 4:19pm

Andrew, I think I understand the Human side of it...in regards of replacing Box2Box, I was looking at the boxmapping feature (as opposed to the morph) for my purposes. As it turns out, I had two problems--one fixed by using dynamic pipeline, the other resulting from box2box--hence 55k instances. You mentioned somewhere in the comments regarding Human about this feature being replaced by another native feature in Rhino--were you referring to morph?

Permalink Reply by Andrew Heumann on April 4, 2016 at 7:52pm

Hi Peter - no; not box morph. There is a native component (I think it's in fact called "box mapping") that does exactly what box2box used to do. It should live under the transform tab.

Permalink Reply by Peter Stempel on April 4, 2016 at 8:37pm

Ok, that's what I meant by "boxmapping", thanks for confirming. And thanks for the plug in... getting use of many other aspects...

RSS