Hi djordje,
“origin” is defined by users and if this input is empty the default value is {0;0;0} whilst " originPt" is the “origin” projected onto surface. This is because the component generates terrain models from points which are placed in the right place by using elevation values.
Probably, I should move the terrain at the same level of the “origin” input.
However I think the outputs are correct for the analysis component.
At the moment the concept is this:
Best
Antonello
Hi Antonello,
Thank you for the reply and the visual explanation.
I think it could be beneficial if you would keep your “_basePoint” (or maybe even “baseOrigin") input instead of “origin”.
In this way there will be no confusion between the input and output points. At the moment, “origin” input and “originPt” output of “Terrain Generator” component represent two completely different points. While "origin” input and “originPt” output of the “Terrain Generator 2” component are the same points.
I think we should also rename the output “originPt” to “origin”. I would do the same with “Terrain Generator 2” component.
Sorry if this looks like a nitpicking. It’s just in my opinion we should at least make both “Terrain Generator” components acting similar, at least when it comes to them being the predecessor components for other ones (like “Terrain Analysis”).
I would like to hear your thoughts.
djordje,
You are right and your idea sounds good. “basePoint” as input and “origin” as output.
I should see what happens if I add the code lines that put the terrain at the origin like LB terrain generator 2.
Best
Antonello
Thank you Antonello.
I was not complaining that the “basePoint” needs to be on the terrain. I perfectly understand the concept of raising the points from the base (where the tiles are) upwards.
I just suggested that a point input name (regardless if it lies on a terrain surface/mesh or not) should probably not have a very similar name to the output which lies on the terrain surface/mesh.
So I am ok with “Terrain Generator” component keeping the “basePoint” input to lie on the same plane where the “tiles” are.
Ok, I will change the name output of the “Terrain Generator 2” component from “originPt” to “origin” and I will edit the hover text of each of “Terrain Analysis” component’s required inputs, that they can use both “Terrain Generator” and “Terrain Generator 2” data.
Thank you once again for the permission, and sorry for being a bit too picky on this.
Ok! thanks a lot, djordje!
Is it correct to use a workflow for the visibility analysis like this?
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!
Hi djordje,
thanks for the updates. Now the analysis component works fine.
I have also found a way to project textures onto terrain models.
That’s a very useful feature Antonello!!
Keep up the great work!
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
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.
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!!
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
Can you share the file?
Although didn’t make any changes in the example file but still, if you want to have a look.
On a side note it works on my personal laptop.
example_LB_terrain_generator.gh (371 KB)
Same error. So it has something to do with how the internet security they have at my workplace deals with the way component collects data.
I changed a boolean in the py which generates the error statement. It generates this error then -
Saket,
Judging from the error message and the fact that it is working on your personal laptop but not a work laptop, I would guess that the error has something to do with a company firewall or antivirus software. If you could find a way to disable this or add an exception, my guess is that it should work.
-Chris
Thanks for the input Chris,
I will get in touch with IT and see what they can do about it.
btw add an exception to …? Rhino?
This might not be the case with you Saket but using a faster internet connection can also make “Please enable internet connection” go away. Posting this for other people who might face this error.
