Geocode: Still getting very sparse results

[matthewkoehler]

As reported in several threads about a month ago, searching by by geocode returns either no coordinates, or very few tweets with coordinates

See:

Geo: null in all search api results

I made a small app which fetches users' geolocation data and displays recent tweets within 100 miles of radius. The query is something like this: https://api.twitter.com/1.1/search/tweets.json?q=&geocode=lat,long,100mi&result_type=recent&count=100 App link: https://recent-tweets.herokuapp.com/ Previously I was getting results close to 100, but now the count has dropped drastically to around just 2-3 results. I tried changing result_type=recent to popular, and even then the results were same. …

GEO search returning very few results

Starting late in the evening on April 21st, I noticed that we that search requests with a geocode parameter are now typically returning around 1 or 2 geo-tagged results results (and 98 or 99 results without Geo information) when 100 were requested, and where there is well over geo results 100 available. Previously they would return close to the full 100 (with just the odd deleted ones removed I imagine). This means now that if you search back in time now by paginating, you hit a zero resu…

Example search:
/1.1/search/tweets.json?geocode=33.70,-84.35,1000mi&result_type=recent&count=100

Is this:
a) A new feature?

b) A bug?

c) Planned to be working like it used?

d) The way it’s going to be from now on?

Thanks,