search uses a variety of different signals to determine whether a tweet should be placed near a specific latitude and longitude -- a geotag is just one of them. so, when querying the search API, you may receive more than just geotagged tweets. your best best is to just discard those which are not explicitly geocoded.
in addition, i'm not sure whether the search representation includes "place" objects (neighborhoods, and cities). On Fri, Apr 9, 2010 at 8:00 AM, Jigu <[email protected]> wrote: > Hi > > > I am trying to retrieve nearest tweets on iPhone. To retrieve > results I requested on "http://search.twitter.com/search.json? > geocode=38.9951%2C-76.9276%2C5mi&rpp=2" > > The problem is everything works correct, But I want each result > should return latitude, longitude so further use but every results in > JSON, property "geo" returns null. So to retrieve latitude, longitude, > what should I do. > > Thanks > Jignesh Brahmkhatri > > > -- > To unsubscribe, reply using "remove me" as the subject. > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
