LB Terrain Generator | index out of range + unable to create image

ladybug

#1

hi guys,

First, what to do when I get the follow error message : something went wrong during the request of images, ( I tried many times without success )

Also Do you know why I’m running a lot into this error message : index out of range. ? (And for apparently no reason… for instance, i run it, it work correctly. Then I change a parameter and it says the error message. So I go back to last settings… and it says the same error message… but it was working 5 min ago…

1.0_GH_script_site-modeling_CC.gh (386.1 KB)


#2

Hi @CharlesCollin,

the component retrieves data from Google API Elevation. I have checked the component and basically the error is because some requests failed, this create a gap. Without all elevations data the component cannot create the final surface / mesh.

I have written a new component for Rhino 6, I release it soon.
The principle is that every user who want to use the component need to add a “API KEY”.
You have 2.500 requests per day for free calculated as the sum of client-side and server-side queries. Obviously, if you have a huge model it will be probably that you need additional requests not for free.
Besides, you can check your quota using the console provided by google:


Here is an example (e.g. Pulo di Altamura [Italy]) made with this new clean method:

Regards,
Antonello


#3

Thanks alot @AntonelloDiNunzio !

I have couple questions :

  1. So I assume until you release this new version of Terrain generator, their is no way around the issues I face ?

  2. In the new component you will release will there be an output for satelite images that could further be mapped onto the topography with human plugin ? I didn’t see it in the screenshot you posted here :open_mouth: (I’m a little scared! that was my favorite feature of terrain generator !!)

  3. Also I red about Google elevation API, and from what I saw, the topography resolution is around 30 meters grid horizontally (most of data coming from STRM) (Am I mistaking?). But the mesh out of your component seems way more accurate. Is it only interpolation points between main references points? I’m asking because Heron plugin is almost doing the same thing, but getting its data from Argis REST services (don’t fully understand) and topography resolution is about 20-30m. So which one is the most accurate ?

  4. Regarding Google API new platform that will be release the 11 June 2018, API key won’t be free anymore. How’s Terrain generator will work (pricing, resolution, etc)?

Finally thank you very much to you and all other contributors for the awesome work :wink: ! Its definitely helping our architect workflow outhere ! I truly appreciate.

Best,
Charles C…