[bsgeyer]

You sir deserve all the beers! Thanks!

For anyone following along or stumbling onto this, after following the instructions above, you must make sure to set the Identifier for your new library to ‘TAGS’, which you upload in the second step 3. Without doing this (or changing most instances of ‘TAGS’ in the script attached to the spreadsheet to whatever the new identifier is), your spreadsheet will not know where to look for the appropriate functions to run.

I should say, I now have an up-and-running TAGS v.6.0 spreadsheet, but I’ve also implemented these changes on an older v.5.1 because of a change Google made to their spreadsheets before you created v6.0, which was preventing my project from importing the published spreadsheet (for more info on that particular issue, see http://stackoverflow.com/questions/20364662/access-control-allow-origin-error-on-google-drive-web-site). This doesn’t bode well for the future of my project…

Again, thanks for all your help, Mr. Hawksey!

• This reply was modified 8 years, 9 months ago by bsgeyer. Reason: clarity

[bsgeyer]

Thanks for the response.

The relevant portion of the code is altered in a few different places. I added a params.geocode with a radius and altered a middle section of the getTweets function with an additional boolean to more specifically filter out tweets not desired and with alterations to the geo coordinates portion of that function (so that it spits out latitude and longitude separately). I also deleted the user input portion of the deleteDuplicates (near the bottom of that function’s code related to the variable resp).

I wouldn’t mind switching to v6, but it is really important to me that these three alterations survive in some form because I’m using the sheet as a way to publish an up-to-the-minute .csv file for a mapping project (http://kenya-tweet.matrix.msu.edu – fair warning: awful color scheme ahead).

[Author]

Posts