The future of maps & storytelling

The future of maps & storytelling

35f4d000a88cdbcf6392dfb206ebd5e2?s=128

Andrew W Hill

October 20, 2014
Tweet

Transcript

  1. THE FUTURE OF MAPS & STORYTELLING @ANDREWXHILL

  2. who am i?

  3. BIOLOGIST

  4. None
  5. DEVELOPER

  6. None
  7. None
  8. MAPPER

  9. None
  10. None
  11. BUILDING TOOLS TO HELP PEOPLE UNDERSTAND AND COMMUNICATE INSIGHTS FROM

    DATA
  12. USING DATA VISUALIZATION TO COMMUNICATE

  13. LOOK DATA!

  14. you Your team your boss The amount that people can

    understand your work with data
  15. None
  16. MAPS ARE INCREDIBLE TOOLS FOR COMMUNICATING COMPLEX DATA

  17. http://bit.ly/livingcities

  18. BUT WHY MAPS?

  19. THE CURIOUS POWER OF THE MAP

  20. None
  21. None
  22. None
  23. None
  24. None
  25. HOME POOL

  26. Guided by salient features

  27. None
  28. None
  29. Distance

  30. Scale

  31. Cardinality

  32. Directionality

  33. Geometry

  34. Symbology

  35. None
  36. http://bit.ly/ZaqMZY

  37. None
  38. None
  39. None
  40. EVERYBODY LETS GIVE THE POWER OF MAPS TO

  41. None
  42. None
  43. http://lat.ms/1u1tzNr

  44. None
  45. http://bit.ly/1EVwboO

  46. http://bit.ly/islamstate

  47. http://bit.ly/1ts3TPQ

  48. DOING CRAZY THINGS THAT WEREN’T DONE BEFORE

  49. AN EXAMPLE

  50. None
  51. None
  52. None
  53. source: bing

  54. WITH  hgrid              AS  (SELECT

     Cdb_rectanglegrid(Cdb_xyz_extent(8,  12,  5),                                    Cdb_xyz_resolution(5)  *  4,                                                          Cdb_xyz_resolution(5)  *  4)  AS  cell)     SELECT  x,                  y,                  Array_agg(c)  vals,                  Array_agg(d)  dates     FROM      (SELECT  St_xmax(hgrid.cell)                                                                                        x,                                  St_ymax(hgrid.cell)                                                                                        y,                                  Count(i.cartodb_id)                                                                                        c,                                  Floor((  Date_part('epoch',  built)  -­‐  -­‐10418716800  )  /  32837875)  d                    FROM      hgrid,                                  us_po_offices  i                    WHERE    St_intersects(i.the_geom_webmercator,  hgrid.cell)                    GROUP    BY  hgrid.cell,                                        Floor((  Date_part('epoch',  built)  -­‐  -­‐10418716800  )  /  32837875)                  )  f     GROUP    BY  x,                        y
  55. None
  56. None
  57. None
  58. None
  59. None
  60. None
  61. None
  62. credit: @javisantana http://bit.ly/enriquerollo

  63. None
  64. http://bit.ly/downeymap

  65. http://bit.ly/downeymap

  66. http://bit.ly/gdeltmap

  67. WE THINK WE’RE ONTO SOMETHING

  68. SOME NEAT FEATURES OF CARTODB

  69. Data support

  70. Live data, import API, and remote sync

  71. Privacy, sharing, collaboration

  72. Privacy, sharing, collaboration

  73. Easy integration

  74. Easy integration

  75. SQL API

  76. Dynamic

  77. None
  78. OUR TAKE ON THE FUTURE OF MAPS

  79. THE FUTURE IS NOT STATIC

  80. http://bit.ly/1wAs0Zy

  81. YOU CAN NOW TELL A DIFFERENT STORY TO EVERY VIEWER…

  82. IT’S A DANGEROUS POWER FOR ONLY ONE PERSON TO HOLD

  83. None
  84. None
  85. None
  86. WE CAN’T BUILD IT ALONE

  87. “The future of geo isn’t a single app with hundreds

    buttons. The future of geo is hundreds apps with a single button.” @jatorre
  88. None
  89. None
  90. WANT TO GET INVOLVED?

  91. http://blog.cartodb.com/

  92. http://academy.cartodb.com/

  93. None
  94. None
  95. We are hiring!!! http://www.cartodb.com/jobs

  96. Thank you! @andrewxhill andrew@cartodb.com