data organization excel into grasshopper / linking to points on map

Hi all,

I am working on a data visualization project that deals with sound levels and frequency analysis at 40 different reporting locations. I've been using the TT Toolbox components to read data in from excel. In order to attribute the correct data to each reporting location, I've been using the sort points components, then reorganizing my external spreadsheet to match this order. As this is a work-in-progress, and more data continues to be added incrementally, this system is definitely less than ideal. It seems like there must be a way to "tag" my different reporting sites in excel, then refer to this as a way to re-arrange the data in gh so that it can be paired with the correct map point (without having to shuffle around the data in the excel sheet), but so far, I've had no luck. I'm wondering if there is a way to nest groups of, say, five columns together, within a structure that will let me arrange them by the number tag for the site. I'm attaching a few screenshots (in this particular example, circles of different sizes are displayed showing decibel levels at different sites). Any suggestions? Thanks!

Attachments:

Replies to This Discussion

Permalink Reply by Peter Stempel on March 16, 2016 at 8:40pm

Rather than tagging the points, you could try to export their coordinates as a CSV using export selected. Assuming they are indeed points you should get coordinates:

http://docs.mcneel.com/rhino/5/help/en-us/fileio/points_file_txt_ex...

Alternately, a rhinoscript:

http://developer.rhino3d.com/samples/rhinoscript/exportpointstoexcel/

You could then build one database that includes all of your readings and the points themselves. The values for x and y can be fed from TT Toolbox to the construct point component such that the point is made in GH from your database. This way as you add readings you can simply reload the csv. Everything including your points will update. If you add more locations you would simply append another set of exported points to the master database.

I'd also suggest you construct your table row wise so that you don't have gaps and null values--column headings would be ID, X, Y, Z, IB1, OB1, IB2, OB2, ........ IBn, OBn (how a GIS attribute table is arranged). This way you can append additional columns as you add readings. You can add averages, etc. at the end. This way your GH work will stay in sync simply. You could also do things like using min or max functions to show the max in every location, etc., again appending a column.

Permalink Reply by Jane Smith on March 18, 2016 at 6:12pm