Twitter’s API Now Includes Local Trends
Jan28
by Chad Catacchio

Twitter’s new Local Trends function on Twitter.com is basically meaningless. It’s full of spam (just as the global Trending Topics is) and really isn’t all that interesting because: 1. lots of the same trends go across the limited number of places Twitter is offering right now; and 2. there is no context for the user other than millions of other people in their city or country tweeting. We held off on writing about Local Trends until today because until Tuesday only about 1% of Twitter users had Local Trends enabled (not sure if it is 100% now, but lots of people now have it enabled) and second, the API function related to Local Trends wasn’t turned on either until the last 24 hours or so. As with most things in the Twitterverse, the API is where it’s at, and now Local Trends can really get interesting.
Twitter’s API team turned on two calls – Local Trends/available and Local Trends/location. While Twitter is still apparently building out the places that they can offer trends around, this API call will allow developers to go beyond geotagging of tweets (which will discuss below) and map out trends and search parameters inside of their applications. One interesting line in the API documentation says that Local Trends are “an array of “locations” that encode the location’s WOEID and some other human-readable information such as a canonical name and country the location belongs in.” We read that as saying that Twitter is using a mix of ways to determine a user and a tweet’s location, and not just relying on lat/long. Obviously, there could be many uses for this. Read the rest of this entry »







