Data + Visualization Toronto Meetup 4: The Google Maps API

711 views

Published on

Trimmed version of slides shown at the Data + Visualization Toronto Meetup Group's Fourth Meetup. Contains information about the Google Maps API, and Google Geocoding API.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
711
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Data + Visualization Toronto Meetup 4: The Google Maps API

  1. 1. Raining Cats and Dogs DVTO 4: The Google Maps API
  2. 2. http://www.toronto.ca/fire/cadinfo/livecad.htm
  3. 3. Slides Removed • • • See http://www.torontofirecalls.com for app http://www.toronto.ca/fire/cadinfo/livecad.htm http://www.toronto.ca/fire/cadinfo/livecad.xml
  4. 4. Designs and Compromises • “First make it possible. Then make it beautiful. Then make it fast.” -Nathan Marz
  5. 5. Make it Possible • Node JS and Redis, because programming • Revert to Rails and Postgres, because spaghetti
  6. 6. Every 5 Minutes do X 1. Custom Rake Task w/ Heroku Scheduler 2. Clockwork and Delayed Job (OMG $$$) 3. Clockwork and Delayed Job with Workless 4. Switch to WebFaction 5. Bare Cron 6. Cron by Whenever Gem
  7. 7. Slide Removed • http://mapicons.nicolasmollet.com/
  8. 8. Make it Fast(er) • NewRelic development agent -> Profiled • Event retrieval on click? Not scalable • Optimized AR Queries • InfoWindow Generation/Retrieval to AJAX
  9. 9. Part 4 Google Geocoding and Maps API’s
  10. 10. Google Geocoding API • http://maps.googleapis.com/maps/api/geocode/j son?address=1600+Amphitheatre+Parkway, +Mountain+View,+CA&sensor=true • JSON or XML, HTTP or HTTPS • 2,500 requests per 24 hour period. • Also a rate limit, so sleep during bulk geocodes
  11. 11. Reverse Geocoding • Have location, need address. • http://maps.googleapis.com/maps/api/geocode/j son?latlng=40.714224,-73.961452&sensor=true
  12. 12. Slide Removed • https://github.com/alexreisner/geocoder
  13. 13. Geocode Happy 1. Realistic use case? 2. Have a strategy. 3. Check the TOS.
  14. 14. Markers on a Map
  15. 15. Step 1
  16. 16. Step 2
  17. 17. Step 3
  18. 18. Step 4
  19. 19. Step 5
  20. 20. Slide Removed • See https://github.com/apneadiving/Google-Maps-for-Rails
  21. 21. Bonus Resources • CartoDB and Torque • Google Maps Mania Blog
  22. 22. Slide Removed • See thedirt.co
  23. 23. Slide Removed • See padmapper.com
  24. 24. Slide Removed • http://lifewatch.inbo.be/blog/posts/trackingeric.html
  25. 25. Matt Holtom matt@codeandiron.com @mattholtomTO Code & Iron codeandiron.com @codeandiron

×