Tag Archives: Geolocation

Geolocation on Twitter is Huge

A theme I keep reiterating in presentations is that everything we encounter in daily life has a geographic component.   Tying this geographic component into the technology we use is the key to real transformation in how we consume data in daily life.   Being able to filter and analyze data geographically is the key.  In this vein, I’m quite excited about yesterday’s launch of geolocation on the Twitter API.

Let’s dream for a second.

Let’s imagine being able to collect a realtime feed of what is going on in a particular location through a network of distributed listening nodes.   Let’s imagine being able to process this feed and analyze what is happening in real time.

Maybe we know about a tsunami 10 minutes earlier from villagers that experienced its power.   Maybe we know there was a spike in chatter about a shooting at a military base 3 minutes sooner.   Maybe we can market to consumers better based on how they react to a billboard in Times Square.

I see this dream becoming reality quite soon.   Twitter with geolocation is essentially a network of  distributed listening nodes for geographic data.    I don’t think we can really predict all the novel ways this is going to be used.

Have an idea for Twitter and geographic analysis?  We’d love to hear it:  info@azavea.com

The Dawn of Background iPhone Geolocation

Maybe AT&T and Loopt are reading our blog?   It would be nice to imagine, but either way I’m glad of the news that Loopt and AT&T are working together to support background updating of geolocation from iPhones.

The concept of a continuously published stream of locations for a user is immensely powerful.  Imagine if the iPhone would publish updated geo-location which was shared with applications that the user granted access.    Loopt could let me know that my friend is nearby without me having to open the application to update my location.

I held off writing this post in the hopes of being part of the trial, but unfortunately haven’t been able to use the service first hand.

I can understand charging for the availability of this data, but the charge shouldn’t be associated with only one service — Loopt.   How about a standardized feed of my iPhone’s location that requires authorization to use, AT&T?   Then, I could share this feed with whatever services I wanted.  Now that I would pay for.