Hmm, I would think thrice, before I go his path again. Thought it was a clever idea to use the mixture of easy to maintain spreadsheets, the cron service and JSON to feed huge satellite images into a tiling service (zoom.it) and let Google autonomously update and serve the list of daily mosaics as JSON. I got used to daily time out messages, but waiting 1 min for a (cached!) 10 kb JSON list is far too much. However,…
Use a Google Spreadsheet as your JSON backend
51–60 of 69 posts
Re: Use a Google Spreadsheet as your JSON backend
#52Yes I have done this. Google make it particularly difficult to get the URL of the spreadsheet. And that od6? Thats if you have multiple tabs, they have random identifiers. Its almost impossible to work out what they will be. Its like they are on the web but not of the web. But it is an easy interface for unskilled users to add data to say a graph on a website, have done that for clients and they have been very happy.
The tab identifiers are actually listed in the Spreadsheets API, inside the "worksheets" feed: https://developers.google.com/google-apps/spreadsheets/#work... As a historical note, these identifiers used to be part of the URL, long ago. The newer version of the Spreadsheets frontend doesn't use them, but they're still used by the Spreadsheets API.
Re: Use a Google Spreadsheet as your JSON backend
#53Hmm, I would think thrice, before I go his path again. Thought it was a clever idea to use the mixture of easy to maintain spreadsheets, the cron service and JSON to feed huge satellite images into a tiling service (zoom.it) and let Google autonomously update and serve the list of daily mosaics as JSON. I got used to daily time out messages, but waiting 1 min for a (cached!) 10 kb JSON list is far too much. However,…
I always stick a caching proxy in front of it rather than using it directly. ( Mine is actually public but doesn't come with an SLA)...
Re: Use a Google Spreadsheet as your JSON backend
#54..FWIW, for those of you who haven't been enlightened with the power that Google Apps Script[1] offers yet, be sure to check it out: http://script.google.com . Layered on top of Spreadsheets, this pair takes prototyping to a whole new level. [1] https://developers.google.com/apps-script/
Re: Use a Google Spreadsheet as your JSON backend
#55GitHub: https://github.com/biovisualize/d3visualization
Spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AqMEGBUNwXeHdHp...
Re: Use a Google Spreadsheet as your JSON backend
#56javascript:(function(){var key=/key=[a-zA-Z0-9]+/.exec(window.location.search)[1];var url="https://spreadsheets.google.com/feeds/list/"+key+"/od6/publi...;})();
Re: Use a Google Spreadsheet as your JSON backend
#57Tabletop is a great JS library for dealing with this: https://github.com/jsoma/tabletop
Re: Use a Google Spreadsheet as your JSON backend
#58Re: Use a Google Spreadsheet as your JSON backend
#59I wrote up some notes from the experience, as Google Spreadsheets is full of quirks and some of the APIs and other means of access are very easy to break - it is very easy to create a spreadsheet that will return broken JSON, for example, in some modes, and then cannot be fixed (ever) to return unbroken JSON.
https://www.exratione.com/2013/04/some-notes-on-csv-parsing-...
Re: Use a Google Spreadsheet as your JSON backend
#60Good for prototyping, thanks. I'd be wary of using this in a live system though: relying on Google's public APIs/services is risky enough (Checkout is one example, Reader, etc) let alone an undocumented feature like this which could change/disappear suddenly. Edit: it has been pointed out that the criticism of their documented/public APIs may be unjustified. The issue here is that this particular feature is undocumen…
We've sent people off into the caching world[4] to fit it on our end, but your criticism is unfortunately spot-on.
[1] https://github.com/jsoma/tabletop
[2] https://github.com/jsoma/tabletop#okay-wait-weve-got-a-big-p...
[3] http://productforums.google.com/forum/#!category-topic/docs/...