|
Demos
Various Simple Demos to Illustrate the use of GeoAPI.com
To show off some of the cool stuff that can be done with the GeoAPI, we have pulled together a few quick demos. These demos were pulled together very fast (i.e. a day or work or less for each, so full disclaimers apply). Demo 1: Location Check-InsA number of social location broadcast apps have launched in the last year. The GeoAPI makes it easy to build a similar application. In this demo, you can chose a lat/long on a map by clicking on the map (or, similarly, an iphone or android device can pass a lat/long in a related fashion). In reply to the coordinates the API returns a set of businesses which a user can click on to "check in" and then annotate with a comment. These comments get published into the writable part of the API which is then accessed by the user to see what comments people posted in the area while checking in. This means anyone can now much more easily write either (a) a location broadcast app or (b) an augmented reality app, where e.g. a pot of gold could be stored by a user at Starbucks, and this location annotation could be stored as a layer in our system via the API. Key point This is an all javascript demo from the developer perspective. We are not only reading locations from the API, but also literally writing information onto the GeoAPI servers to the unique virtual overlay or layer each API key comes with. This is a unique aspect of this API - the ability to write your own virtual overlay of the world (or at least the parts of the world we currently support) How to try it out:
Source Code: http://code.google.com/p/geo-api/source/browse/#svn/trunk/demos/checkin-stream
Demo 2: Annotation of Twitter Streams with LocationsSome tweets are annotated with locations in the form of lat/lons. The coordinates of these tweets are not converted into locations, so it is hard for the user to tell where the user tweeted from without doing a search. In this demo, we take a live stream of tweets and do location lookups based on the associated coordinates. We then annotate nearby (rather then exact) locations in real time and display the result. So you can see that someone tweeted from "Near Dolores Park / Mission District / San Francisco" instead of "37.7600, -122.4270". This is a cool way to get "real location" context for real time information. How to try it out:
How to use it on your iPhone: If you go to the demo using an iPhone (you can also use: http://bit.ly/46pls2), we will pull lat/lon from the phone and use that to show a nearby Tweet. Caveats: Given that a single person built this demo in a few hours there are some caveats:
Source Code: http://code.google.com/p/geo-api/source/browse/#svn/trunk/demos/twitter-nearby
Demo 3: Greasemonkey Script for TwitterShout out to Zboogs! Part 1: Convert Place Names Into Canonical Locations We think it would be cool for there to be a "bit.ly for locations" or "hash tags for locations". To this end we wrote a greasemonkey script that converts "::POI-name" into a linked URL for a point of interest near to where the user is. We demo this as a Greasemonkey script for Twitter with the assumption that you, the user, are close to Ritual Roaster in San Francisco. i.e. if you write "::ritual" or "::other-place-near-ritual" we will automatically convert "::ritual" to a link for "ritual roasters" and will take "::other-place-near-ritual" and resolve it to whatever likely business or point of interest that is. (In this proof of concept demo we actually resolve to the closest POI or business that matches the string, so right now there is nothing to resolve ambiguities) Part 2: Convert Coordinates into Points of Interest The Greasemonkey script converts a lat/lons on Twitter to "real location". So the coordinates "37.7600, -122.4270" get converted to the neighborhood the Tweet is from e.g. "Mission District / San Francisco". The cool thing about this is if you are running greasemonkey you can actually see this location annotation occur in real time to your Twitter stream. So this is a way for any Twitter user to see where all the people they are following are tweeting from. How to try it out:
Source Code: http://code.google.com/p/geo-api/source/browse/#svn/trunk/demos/twitter-greasemonkey
Demo 4: Media Layers: Tweets and Flickr Photos by NeighborhoodThis demo highlights the new media layers we have added to the GeoAPI. We make it easy for you to see the Tweets, Flickr photos, and other media associated with any polygon stored in our system (e.g. neighborhood, city, parks, etc.) . In this demo you can restrict a tweet stream by neighborhood polygons. This allows you to view e.g. all the Tweets in the Mission District, or Flickr photos from SOMA, in San Francisco. Tweets: Only a subset of Tweets currently have lat/lon coordinates. We map these coordinates to neighborhoods, and only show Tweets that fall within a given neighborhood boundary. We automatically refresh the screen every 30 seconds. Flickr Photos: We look at Flickr photos published in the last few DAYS with lat/lon coordinates. We map these coordinates to neighborhoods, and only show photos that fall within a given neighborhood boundary. Sometimes the photos are scarce since we only display photos from a handful of days. How to try it out:
Demo 5: What's Near Me?We wrote a JavaScript app for mobile devices to let you see businesses nearby by category. The app automatically grabs your location from iPhone and lets you chose nearest bars, restaurants, parking lots and more. This highlights the value of the attribute function of the GeoAPI which allows developers to query the API based on category of business (e.g. thai restaurants) and other attributes. How to try it out:
Source Code: http://code.google.com/p/geo-api/source/browse/trunk#trunk/demos/wnm |
I love this! I hope it works! Good luck with this.