Grasshopper

algorithmic modeling for Rhino

I have moved the file location and therefore path definition numerous times and it is still not working. I am thinking maybe elk cant handle mountainous terrain?

I need this yesterday. Please help!

Views: 989

Replies to This Discussion

I have the same problem, trying torepresent a path.. which is the criteria to move the Lo and La?

The latitude and longitude are too large and don't even include the range covered in the HGT file. The file's only contain 1°x1° squares, so if you need to create something that spans as much space as you're showing you would need to stitch together multiple topo's.  Plus a topo of that size would likely be very slow performing.  Assuming SRTM3 is the file type being used, the range shown in your domains is going to be close to 100 million points.

I've made the topo model for Shantou, China, so it must be working.

Attachments:

what does the error message say on the sTopo module?  

Too little too late, but the problem with the original post is probably the Longitude domain and an incorrect HGT file.  HGT files are 1°x1° tiles, named according to the lower left corner.  So the HGT file loaded goes from 32° to 33° latitude, and -111° to -110° longitude.  

To get the topo specified by the latitude/longitude, you actually need N32W112.  Then the longitude domain should be from -111.167 to -111.117.  Western longitudes are negative, and eastern longitudes are positive.

RSS

About

Translate

Search

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service