A simple example demonstrating how Coördinator could be used to intersperse relevant, non-data-driven elements into a data story. The runner and Olympic logo are comprised of the circles representing relevant athletes.
Olympic data from: https://www.teamusa.org/road-to-rio-2016/team-usa/athletes
Runner icon by Christian Brunner: https://thenounproject.com/chbrunne/
Olympic logo: https://commons.wikimedia.org/wiki/File:United_States_Olympic_Committee_logo_2.svg
| <!DOCTYPE html> | |
| <meta charset="utf-8"> | |
| <style> | |
| </style> | |
| <div id='marquee'> | |
| </div> | |
| <script src="https://d3js.org/d3.v4.min.js"></script> | |
| <script> |
Snowman image via: https://thenounproject.com/marvdrock/
| license: mit | |
| height: 620 | |
| border: no |
| height: 800 |
| with | |
| dau as ( | |
| -- This part of the query can be pretty much anything. | |
| -- The only requirement is that it have three columns: | |
| -- dt, user_id, inc_amt | |
| -- Where dt is a date and user_id is some unique identifier for a user. | |
| -- Each dt-user_id pair should be unique in this table. | |
| -- inc_amt represents the amount of value that this user created on dt. | |
| -- The most common case is | |
| -- inc_amt = incremental revenue from the user on dt |
