Daniel,
The search index only cover <7 days worth of content, and a tweet from July
17th is older than 7 days. This has nothing to do with your geocode and is
an issue with the depth of the index.
Geo is not the only signal used for location and you may also have place ids
other sources.
Jonathan
On Tue, Aug 10, 2010 at 5:26 AM, Daniel wrote:
> Hi!
>
> This is the thirth time I post this problem and no body may help me.
> This is a very important problem than only occurs in some countries of
> South America as Chile, Argentina, Peru.
>
> This is a clear problem related to the geocode query...
>
> I'm trying to make a search query with GEOCODE params but this is not
> working propperly.
>
> I created this geolocalizated tweet with echofon:
>
> http://twitter.com/DanielAtik/status/18794641441
>
> As you may see here is the lat, lon of this tweet:
>
> http://maps.google.com/maps?q=-33.437790,-70.635895
>
> But if I make a search with search API this tweet does not appears as
> you can see:
>
> http://search.twitter.com/search.json?geocode=-33.437790,-70.635895,2km
>
> or for delimeted more:
>
> http://search.twitter.com/search.json?geocode=-33.437790,-70.635895,2...
>
> As you may see at returned JSON, the tweets has not GEO values. Is
> there anything wrong?? Any help may be appreciated ;)
>
>
> Daniel
>
