Visualization Hall of Fame
Stay organized with collections
Save and categorize content based on your preferences.
This page is here to show you what's possible with the Interactive Chart API. This page is not for demonstrating new types of visualizations, but for showing interesting ways of using visualizations posted in our gallery.
Battlefield Reenactment
A demonstration of animating a motion chart to reflect physical location over time. And a guaranteed technique for vanquishing a horde of orcs and trolls.
By TheViz@google.com
Singapore Train Disruptions
A bubblechart
timeline of train service disruptions in Singapore. This chart retrieves
data from a Google spreadsheet via a SQL query and uses five sliders
to control which data are displayed. Original version
here.
By FAILRAIL.sg
(failrailsg.appspot.com)
I Want to Submit a Visualization!
We're looking for interesting visualizations from you! If you have a
visualization that demonstrates an interesting feature or data, a nice
design, or uses the API in a way that's new or exciting, send it to us!
If we like it, we'll post it to this page.
To submit a chart, send mail to
TheViz@google.com with
the following information:
- The full code for your visualization,
- Your name, as you want it to appear on the web site,
- A link to your site or an email address, if you'd like to include it,
and
- A description of the visualization: that is, what it shows, and why
it's special.
Note that by submitting a visualization you allow us to publish and modify
it (for size, appearance, or maybe because we know of a neat trick to
simplify the URL). Happy coding!
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-07-10 UTC.
[null,null,["Last updated 2024-07-10 UTC."],[],[],null,["# Visualization Hall of Fame\n\nThis page is here to show you what's possible with the Interactive Chart API. This page is not for demonstrating new types of visualizations, but for showing interesting ways of using visualizations posted in our [gallery](/chart/interactive/docs/gallery). \n[Want to submit a visualization to the gallery?](#submit_a_chart)\n\n*** ** * ** ***\n\nBattlefield Reenactment\n-----------------------\n\nA demonstration of animating a [motion chart](/chart/interactive/docs/gallery/motionchart) to reflect physical location over time. And a guaranteed technique for vanquishing a horde of orcs and trolls.\n\n**By [TheViz@google.com](mailto:TheViz@google.com)** \n\nSingapore Train Disruptions\n---------------------------\n\nA [bubblechart](/chart/interactive/docs/gallery/bubblechart)\ntimeline of train service disruptions in Singapore. This chart retrieves\ndata from a Google spreadsheet via a SQL query and uses five sliders\nto control which data are displayed. Original version\n[here](http://failrailsg.appspot.com/major-disruptions.html).\n\n**By FAILRAIL.sg**\n([failrailsg.appspot.com](http://failrailsg.appspot.com)) \nBuses deployed Staff deployed Commuters affected Delay hours Fine amount (dollars) \n87 300 127,000 19 1,000,000 \n15 0 1 1 0\n\nI Want to Submit a Visualization!\n---------------------------------\n\nWe're looking for interesting visualizations from you! If you have a\nvisualization that demonstrates an interesting feature or data, a nice\ndesign, or uses the API in a way that's new or exciting, send it to us!\nIf we like it, we'll post it to this page.\n\nTo submit a chart, send mail to\n[TheViz@google.com](mailto:TheViz@google.com) with\nthe following information: \n\n- The full code for your visualization,\n- Your name, as you want it to appear on the web site, \n- A link to your site or an email address, if you'd like to include it, and\n- A description of the visualization: that is, what it shows, and why it's special.\n\nNote that by submitting a visualization you allow us to publish and modify\nit (for size, appearance, or maybe because we know of a neat trick to\nsimplify the URL). Happy coding!"]]