April 21, 2010
Single purpose API
Sorry, No followers
Last August was when Twitter first announced it would offer geocoded tweets. With it, user locations are tied to their updates. That feature was rolled out in November. Two months later comes word that it's getting very little use. TheNextWeb reports that less than one-fourth of one percent of all tweets are geo-tagged. For every 430 messages that pass through Twitter, only one has a location--very, very few. Why? Read on for a few potential ideas.
Planning a trip, whether just down the road or into the next city, normally revolves around the distance of the desired location. It's common practice to search for the distance between two points on a map, then take a rough guess as to how long it will actually take to get there. But we all know that distance isn't the only factor to consider. What about mode of transport, peak traffic hours or alternate routes? All these can dramatically affect how long it actually takes to get to your destination. This post will discuss how iGeolise's Travel Time and the Travel Time API changes the way people search and the results that are produced.