LB terrain generator

Hi All,

During these days I have written a new component called LB terrain generator.
I have studied a bit GEO components of gHowl and Google's API.
And I read that there are some limitations when you use Google's API, especially if you'd like to achieve a great quantity of data without overloading Google's servers.

I used a way to request data without overloading Google's servers by using a tiling method. Obviously, this component respects the limit of 2500 requests per day.

This is how the component works:

1) set one point and its coordinates

2) generate surfaces by using isotrim component (Basically, each sub-surface is a request)

3) set the number of division of each surface and the resolution of Google static maps

4) run, move points and generate surfaces with surface from points

5) apply textures to the surfaces

In the image below another small example:

I was thinking that this should be useful for wind simulation with Butterfly, maybe.

Best

Antonello

Replies are closed for this discussion.

Replies to This Discussion

Permalink Reply by Antonello Di Nunzio on October 4, 2016 at 5:45pm

Ok! thanks a lot, djordje!

Is it correct to use a workflow for the visibility analysis like this?

Permalink Reply by djordje on October 6, 2016 at 3:00am

Hi Antonello,

Not really. Initially I've planned to use only the _origin point and its elevation (the central point from the "Terrain Generator 2" component) for visibility analysis. So basically the visibility would always be calculated starting from that point (that's the photo on the left, below).

But you have just discovered a new way of choosing a custom point! Thank you for that! (that's the photo on the right):

By the way, the Visibility legend coloring scheme in "Terrain analysis" component had a bug, which is visible on the last photo you attached. I waited for us to settle the origins input/output name before fixing it. The newest version of Terrain analysis has it fixed. I also added text to _terrain, _origin, and _elevation docstrings suggesting the usage of "Terrain Generator" component data as well.

Also, try setting the "refine" input to "True". It will increase the quality of the final analysedTerrain mesh.

Once again, thank you Antonello for the useful support and collaboration!

Permalink Reply by Antonello Di Nunzio on October 6, 2016 at 5:05am

Hi djordje,

thanks for the updates. Now the analysis component works fine.

I have also found a way to project textures onto terrain models.

Permalink Reply by djordje on October 6, 2016 at 9:10am

That's a very useful feature Antonello!!
Keep up the great work!

Permalink Reply by Aymeric Delmas on October 7, 2016 at 2:44am

Hello Antonello and Djordje,

First thank you very much for your two super useful components!

I used to have the same workflow as Djordje's component using opentopography data but written with "ugly" "basic" Grasshopper and PythonGh script. So I am super happy to have this new TerrainGenerator2 component added to Ladybug suite ! :)

However, following the install instructions and checking for the opentopography.org availability, the component does not seem to manage to download the data... (see picture attached).
Djordje, do you have any idea about what I can I do or check to fix this?

Other question, just to be sure, regarding the "origin_", is it the central point that you to get out of the output mesh/surface? And does it need to be the point at the actual point elevation or does it need to be the point projected on the ground floor (as I do in my definition)?

Thanks again for your work,

Cheers

Attachments:

Screenshot 2016-10-07 11.53.57.png, 268 KB

Permalink Reply by djordje on October 7, 2016 at 4:26am

Hi Aymeric,

Thank you for the kind words.

I opened a new topic in here, to answer your questions.

Best regards to lovely Réunion.

Permalink Reply by Saket Sarupria on January 23, 2017 at 7:06pm

Firstly many thanks for this extremely useful component.

I tried to run the script on my work pc, it shows an error. It works on my personal laptop though. Any suggestions/comments what I can change to make it work.
Thanks!!

Permalink Reply by Devang Chauhan on January 23, 2017 at 11:31pm

Hi Saket,

There's an update to the component you're using. Can you please update the same? The update date is Jan 12 2017. I hit this error once and re-running the solver solved it.

-Devang

Permalink Reply by Saket Sarupria on January 24, 2017 at 12:42am

Hi Devang,

Gives the same error unfortunately.