code-for-dc-edu
code-for-dc-edu copied to clipboard
HarlanH
pull data from API rather than local file
This might be a good option, in our case: http://jlord.github.io/sheetsee.js/ (plus a Node.js server) Or this, from a local company: http://delray.io/
sheetsee.js looks really cool! didn't know about it. now i've got to play with it :)
have we looked at something like cartodb? http://developers.cartodb.com/ can be used as a mySQL database, with api methods already. or, it does support mapping using leaflet. so, our transition might be quite easy. just a thought.
We hadn't considered CartoDB, but perhaps we should. On the other hand, if we can have a more lightweight platform, based on JSON APIs, that might be easier to maintain in some other ways. Dunno.
Let us know how sheetsee.js looks in practice!
On Fri, Sep 20, 2013 at 2:42 AM, Chienyi Cheri Hung < [email protected]> wrote:
sheetsee.js looks really cool! didn't know about it. now i've got to play with it :)
have we looked at something like cartodb? http://developers.cartodb.com/ can be used as a mySQL database, with api methods already. or, it does support mapping using leaflet. so, our transition might be quite easy. just a thought.
— Reply to this email directly or view it on GitHubhttps://github.com/HarlanH/code-for-dc-edu/issues/11#issuecomment-24792572 .
I played with sheetsee.js a bit this weekend, just the client-side of things though. I didn't look into its node.js implementation. so here's my 2 cents:
Out of the box, it's really a plug-and-play graphing script to make simpler graphics. While it's pretty cool, I don't think it''ll be all that useful for us. It's intended to make graphing easier and quicker. But it doesn't seem to be that great of a solution as our data grows since it does have that emphasis on graphing. We may be better off choosing a solution that just focuses on our data management and access. IMHO.
oh, relying on google doc does have its downside - the total row limit to a single table :( I had a lot of trouble once with a huge data set that I thought I could use google doc to manage. Had to eventually move it to fusion table (slightly larger table size limit) but then I had to rewrite a bunch of code. not. fun. :(.
Thanks, that is super valuable! Maybe the best architecture is to have a server-side system that pulls from multiple remote APIs (or Open Data DC or elsewhere), caches, and merges the results into a coherent API. I wonder what the right way to do that is?
On Mon, Sep 23, 2013 at 6:41 PM, Chienyi Cheri Hung < [email protected]> wrote:
I played with sheetsee.js a bit this weekend, just the client-side of things though. I didn't look into its node.js implementation. so here's my 2 cents:
Out of the box, it's really a plug-and-play graphing script to make simpler graphics. While it's pretty cool, I don't think it''ll be all that useful for us. It's intended to make graphing easier and quicker. But it doesn't seem to be that great of a solution as our data grows since it does have that emphasis on graphing. We may be better off choosing a solution that just focuses on our data management and access. IMHO.
oh, relying on google doc does have its downside - the total row limit to a single table :( I had a lot of trouble once with a huge data set that I thought I could use google doc to manage. Had to eventually move it to fusion table (slightly larger table size limit) but then I had to rewrite a bunch of code. not. fun. :(.
— Reply to this email directly or view it on GitHubhttps://github.com/HarlanH/code-for-dc-edu/issues/11#issuecomment-24961408 .