I was not talking about charging for an application, but charging for a visualization. Let's say I have a written a visualization that is expensive to compute on the server. End users consume this visualization through the GViz API, it appears I am not allowed to charge for it. The model is similar go Google Map's API Key where they used to impose a daily quota, and then charge big site users for a larger volume of traffic.
-Ray On Thu, Jan 1, 2009 at 7:17 AM, TheViz <[email protected]> wrote: > You absolutely are allowed to use the Visualization API for both commercial > and non commercial uses (see section 6.1 of the Terms). > > Other applications of the same model you are describing (an application that > also consumes server-side resources) have already been developed over the > Visualization API with free and premium, for-pay, editions. > > What may have gotten you confused in the Terms are the provisions that do no > allow you to charge money for the API itself (charging not for your > application but for the use of the API itself, or copying/duplicating the > API and/or later charging for it). > > We look forward to seeing your application. Please share it with us and > submit to the gallery. > > On Wed, Dec 31, 2008 at 11:44 PM, Ray Cromwell <[email protected]> > wrote: >> >> On the subject of licensing, what is Google's position on creating >> commercial visualizations? The TOS seems to reject it ("royalty >> free"). We have a particular visualization that requires consumption >> of server side resources from us (not purely client-side), which means >> we end up paying for others to use the visualization. We are >> interested in a Google Maps-like tiered approach, where we grant an >> API key which allows free usage up to a quota (say, 50k invocations >> per key per day), and then charge a fee over the quota for large >> users. This appears unsupportable at the moment given the current >> licensing terms on GViz, but I could be wrong. Anyway, as a result, it >> may mean we offer a version which sits outside of GViz, and works like >> any other JS widget, which is regrettable. >> >> -Ray >> >> >> >> On Wed, Dec 31, 2008 at 5:52 AM, TheViz <[email protected]> wrote: >> > Hi Chris, >> > >> > Publishing an image on a blog or a site from a Visualization API created >> > chart for purposes such as discussing the API, showing an example of >> > what >> > can be done, etc is perfectly fine. >> > >> > Creating Visualization API charts, then turning them into static png >> > images >> > as an ongoing method for publishing visualizations on your website is >> > not >> > allowed as it constitutes use of the API in a manner different than its >> > intended use. >> > >> > Hope this helps. >> > >> > On Mon, Dec 29, 2008 at 11:29 PM, Chris Hager <[email protected]> >> > wrote: >> >> >> >> hey, >> >> >> >> i was wondering about serving snapshots of interactive charts and maps >> >> (and couldn't find it in the terms of use). Let's say I'd like to make >> >> a >> >> homepage which delivers a map like >> >> >> >> >> >> http://code.google.com/apis/visualization/documentation/gallery/intensitymap.html >> >> (or a geomap) as a single .png image... would that violate the terms of >> >> use or is that possible? >> >> >> >> best from vienna, >> >> - chris hager >> >> >> >> >> > >> > > >> > >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en -~----------~----~----~----~------~----~------~--~---
