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:
- set one point and its coordinates
- generate surfaces by using isotrim component (Basically, each sub-surface is a request)
- set the number of division of each surface and the resolution of Google static maps
- run, move points and generate surfaces with surface from points
- 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.