4 ms·
We use the Google Charts API - it's free and very good. But I haven't seen many others comment about it. Is there a problem with using that?
by rexreed 16y ago
We use the Google Charts API - it's free and very good. But I haven't seen many others comment about it. Is there a problem with using that?
- gregable 16y agoLinky: http://code.google.com/apis/chart/ http://code.google.com/apis/chart/
- martingordon 16y agoThe only problem I've run into is an issue with URLs being too long when trying to chart large amounts of data.
- rexreed 16y agoGoogle Visualizations API is also very good and (I think) avoids the problem of sending data to Google, and if locally cached, shouldn't require access to Google servers. That said, if you're running an online app, you should have access to the Google Servers, especially if you're already using their copy of jQuery for performance reasons.
- mprovost 16y agoMost of the visualizations don't send any data to Google. It tells you on the bottom of the page for each chart type under Data Policy, eg http://code.google.com/apis/visualization/documentation/gallery/annotatedtimeline.html#Data_Policy http://code.google.com/apis/visualization/documentation/gall...
- patangay 16y agoI think the main problem with the google charts API is just that, it's not a library that is self contained. You need access to google's servers. Second, if you have sensitive data, you rather not send it to google.