Generate Terrain Not Connecting to OpenTopography Server

Hello djordie,

Thanks for this amazing component. I have used it successfully on my personal PC, but on my work PC, I consistently get the server error. I followed another forum post on this issue, tried turning off all firewalls, etc, but still have the issue. I am using your 'analyse_terrain' file.

http://www.grasshopper3d.com/group/gismo/forum/topics/terrain-gener...

The error says:

downloadFile_e1: Unable to connect to the remote server
downloadFile_e2: [Errno socket error] getaddrinfo returns an empty list
This component requires topography data to be downloaded from opentopography.org as a prerequisite for creating a terrain. It has just failed to do that. Try the following two fixes:

1) Sometimes due to large number of requests, the component fails to download the topography data even if opentopography.org website and their services are up and running.
In this case, wait a couple of seconds and try reruning the component.

2) opentopography.org website could be up and running, but their terrain service (RESTful Web service) may be down (this already happened before).
Try again in a couple of hours.

If each of two mentioned advices fails, open a new topic about this issue on: www.grasshopper3d.com/group/gismo/forum.

Have you found any other ways to get around this besides shutting off the firewall?

Thanks

Nate

Replies to This Discussion

Permalink Reply by djordje on June 8, 2017 at 11:18am

Hi Nate,

I have just tried running the analyse_terrain.gh file, and it worked without any problem, which means that OpenTopography.org terrain service is working at the moment.

As you've seen in the mentioned topic, for some reason your PC is blocking the "Terrain Generator" component from downloading the terrain file.
Besides shutting all the firewalls, the mentioned topic also advises to modify the "UAC" settings, completely turn off your Antivirus and run Rhino as an administrator: Can you please also try doing those too (here are all the steps from that topic):

1) Close your Grasshopper and Rhino.
2) Restart your PC
3) When it boots up again, in your Start menu's search box type: "UAC", which will find your User Account Control Settings. Click on it, and a new window will open. Set the bar on the left to "Never notify".
4) Turn off your Windows Firewall.
5) Then turn off your custom Firewall (in case you have another one, besides standard Windows Firewall).
6) Then completely turn off your Antivirus.
7) Right-click on "Rhino 5" icon and then choose: "Run as administrator".

Permalink Reply by Nate Wooten on June 13, 2017 at 8:46am

Hello djordje,

Thanks for your quick reply. I had indeed tried those series of steps previously and have not had success. I tried them again this morning, following the steps exactly, but alas the terrain is still not downloading. I used the terrain generator moments ago on my home computer so I think OpenTopography is still working.

Any other ideas on how to trouble shoot the problem?

Much appreciation,

Nate

Permalink Reply by djordje on June 13, 2017 at 9:15am

Hi Nate,
I am sorry to hear that it didn't work.
I assume your office PC is connected to the main server. I have no knowledge of those, nor the way office networks work, and to give you any further advice it would require having some.
Maybe you can ask the person who administers the office network: what may be blocking Grasshopper's access to the internet? Maybe he knows if some port can be opened, or if maybe some privilege can be given to your PC?
I am truly sorry for not being able to help you on this issue.

In case you find the solution, I would be very grateful if you would post a solution here.
Sorry once again.

Permalink Reply by Nate Wooten on June 13, 2017 at 3:18pm

Its quite alright djordje. I've been working with our IT admin folks, but at first look we are unable to determine why it wont connect to the OpenTopo server.

Should we find a solution I will let you know.

-Nate

Permalink Reply by djordje on June 13, 2017 at 3:54pm

Hi Nate,
Check the component below. It contains the same code that Gismo is using to download the terrain data from opentopography.org.
Does it download your photo to C:/NateWootenPhoto.jpg ?
If it does, then it should download the terrain from opentopography.org as well.

Attachments:

download_test.gh, 12 KB

Permalink Reply by Nate Wooten on June 13, 2017 at 4:21pm

Hi djordje,

Thanks for sending this along. It does in fact save my photo to that location. Does this give you any indication as to why the terrain download isn't working?

Trying to decide if its a change in the network that is needed, or a change in the python script. Just not sure where to start the trouble shooting

Thanks for your continued input.

-Nate

Permalink Reply by djordje on June 13, 2017 at 5:07pm

To tell you the truth, I have no idea.
Can it be that maybe you tried to generate some terrain with a "radius_" of a couple of thousands meters? If yes, then which radius? I am wondering if they may banned you because of this?

Maybe some person from your office IT department can check which port is listened by Rhino application? Although the fact that you successfully downloaded your profile photo suggests that the issue may not be with ports.
Sorry for not being able to help you with this.

Permalink Reply by Nate Wooten on June 14, 2017 at 9:52am

I've been keeping the radius at the default 600 in my tests so I do not think this is the problem.

One quick update is that I tried bringing my personal pc (where the script works at home) to the office and it also is failing to connect to the OpenTopography Server.

However, I did notice that when I open the example 'analyze_terrain' example file on both machines, on my personal PC, it will load the Mt Vesuvius terrain example successfully. If I change the radius or location it pops up with the same server error. The same file on my work computer fails immediately upon hitting true and will not display the Vesuvius terrain. I'm wondering if this difference says something about where the problem may be?

Ill let you know if we ever find a solution.

Permalink Reply by djordje on June 14, 2017 at 10:21am

I've been keeping the radius at the default 600 in my tests so I do not think this is the problem.

Okay.

One quick update is that I tried bringing my personal pc (where the script works at home) to the office and it also is failing to connect to the OpenTopography Server.

This is a very valuable information. Before commenting further can you just answer the question related to your quote below:

However, I did notice that when I open the example 'analyze_terrain' example file on both machines, on my personal PC, it will load the Mt Vesuvius terrain example successfully. If I change the radius or location it pops up with the same server error. The same file on my work computer fails immediately upon hitting true and will not display the Vesuvius terrain. I'm wondering if this difference says something about where the problem may be?

Can you please delete your "c:/gismo/terrain_files" folder, and then try running the same example file on your personal PC which just a second ago successfully generated the terrain for the Mt Vesuvius. Of course do this by being hooked to your office internet connection, not from your home (internet connection). What kind of message do you get?

Permalink Reply by Chris Hanley on June 14, 2017 at 11:49am

Hey Nate, Hanley here.

Just back from vacation and happened to see this. It was our firewall at the studio, not a problem with the plugin. It's working now.

For anyone who is interested, the request that the terrain generator component makes to opentopography.org, happens over tcp port 9090. In our case, it was blocked, or more specifically, not explicitly open.

Permalink Reply by Nate Wooten on June 14, 2017 at 11:57am

Thanks Hanley! It is indeed working. Not sure how you got up to speed on this so quickly, but quite glad you are back from vacation...

And thanks again djordie for the great component and thorough replies!

Happy Terrain Generation everyone!

Permalink Reply by djordje on June 14, 2017 at 1:44pm

Thank you for posting the solution Chris and thank you Nate fore being patient and providing feedback!
If you have any other issues, do not hesitate to open a topic about it!
Cheers.

RSS