Grasshopper

algorithmic modeling for Rhino

Hi there,

I was trying to build a landscape from a file containing text objects with height information and points, two text objects in my case. For each point I have the meters in one rhino text object and centimeters in the other. I thought that would be easy but I have a problem which I cannot solve. I found similar questions in the forum but none of them solved my problem.

So far I managed to to read the text objects (strings) an change them to a number with decimals by dispatching two-digit numbers from three-digit (my meters have three digits each) numbers and got my z-vector. The first problem is that I can't allocate the z-value to the right point. Grasshopper chooses any other point. How do I define which value belongs to which point? Can anybody help? Thanks!

Views: 2312

Replies to This Discussion

It would be better to understand your problem with the files

of course...

Attachments:

this gh file explains better

Attachments:

The component you're after is [Find Similar]

My plan was to place the text tag exactly on the spot where the point is in the original file and bake it. after that I wanted to read the new text file and lift the text point. that works perfectly except that the grasshopper text does not match the original rhino text. (I#m saying text, meaning the numbers of course)

what do you need the Point for then?

Edit: Sorry its getting late and my head is fuzzy use the find similar as before to move the point but use the location of the text to put the label back

These point have the right x and y coordinates.

Never mind and thank you very much! You have a totally different approach as I did before. Yours being definitely more elegant ;-) However, the Dispatch node seems to have en error, the three digit number is not always the first (meters). Since I am a rookie grasshopper I would like you to take a look at this again. So far I do not completely understand the file and so I am not sure where to change something...

Attachments:

Some weird behaviour meant I couldn't tie together the decimals with the integers.

So a different approach that should be bullet proof. As all of the text points are relatively in the same place from the actual point we can narrow down the search "area" and pick the correct one. There is also a guarantee that the 3 digit number comes first in line.

Attachments:

Better Still

Attachments:

Incredible! That looks really nice. Again a different approach, I am going to study your file because that seems to be what I originally intended to do. I just failed because of my (hopefully) current lack of knowledge concerning GH.

In the other file I checked the values and dispatched them if they are smaller than "100" to find the decimals. Seemed to work as well.

Anyway, I thank you very much!

Attachments:

RSS

About

Translate

Search

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service