Search API returning (very) sparse geocode results

[bamba416]

Thanks for the reply Andy. Please don’t take what I’m about to say personally

A year…a year… an entire year after incessant asking, pleading, and basically begging for anything concrete we are FINALLY informed it’s a won’t fix. I would have been really bumbed if this were the answer in 11/14 but this is 11/15! We had a real business back in 2014. We’ve now wasted an entire year hoping the problem would be resolved.

I left another whiny comment on this thread more than six months ago complaining how poor the dev outreach was. Unfortunately I think we can now conclude the problem extends well beyond outreach. The 12 month “turn around” for just an answer is totally irresponsible. At the absolute bare minimum, at least have the decency to remove the geocoding support from the documentation!

Again, (Andy) thanks again for trying to keep the community informed. I’ll mention again my rant is not directed at you or anyone in particular. It’s for my own catharsis as much as the hope that other Twitter associates might also be following these threads

[LukeInTH]

Thanks for the update Andy. I think what makes it hard to swallow is that geo searches work just fine on the twitter website search. Please update the docs to say this feature has been removed from the public search api and now only available as paid API.

[ePirat]

Wow, I am flabbergasted that it actually took over a year just to announce that this is expected to not work properly anymore and it’s unlikely to restore that functionality. Thanks for nothing…

And saying that it’s so hard to implement, while it works much better on the Twitter Web Search or the paid Gnip feature is somewhat hard to believe.

(Please don’t take that personally @andypiper, as it’s not your fault what Twitter does…)

[aymanstein]

So what is the alternative to using the geocode?
I need to search for tweets originating from a certain area/country using the Search API (not Streaming). Is this even possible now with the current state of the API?

[andypiper]

Yes, you are free to use the lat/lon coordinates, but only a very small percentage of Tweets (~1-2%) are tagged by their users with location.

[Carlos3285]

Is this working again?

[andypiper]

As I mentioned above - it works, but don’t expect a large volume of results with precise geotagged coordinates.

Yes, you are free to use the lat/lon coordinates, but only a very small percentage of Tweets (~1-2%) are tagged by their users with location.

[Carlos3285]

I mean that i’m getting results without location.

[nsdesign]

Me too!!! It’s only bloody working again!!!