Update Nov2017
UPDATE:  parse.com as now been closed and moved to parseplatform.org. I will update the content of this page an move the back-end to this platform

We’ve looked at Query Limits on parse.com and Google Visualization API data to prepare for loading the color table from Playing around with GAS color into parse.com. Now to load the data

One of the constraints of parse  is that it’s rate limited. That means that we want to minimize the writing that we do, especially with a large data set like this that might need regular batch updating. I’ve decided therefore to
This way, we’ll minimize the amount of back and forwards to parse.
Here’s what the data looks like in the data browser once loaded.

Here’s the whole application. All the components are async, so we’re heavily using promises to bring it all back together again.

Some Gotchas

I already covered the query limits. To avoid rate throttling on Writes, I waited a bit between saves, and  used Parse.Object.saveAll(), instead of object.save() to be able to batch up writes together.
Aside from being a bit fiddly because of the asynchroncity, and the few tweaks, it was all pretty straightforward. Now for the GAS/ScripDB version of loading.

For more on parse.com see Parse.com

For help and more information join our forum, follow the blog or follow me on Twitter