Search API returning (very) sparse geocode results

[isaach]

Thanks for the reports, everyone. We’re looking into some issues with geo-related searches; stay tuned.

[robert_lowe]

Has there been any progress made on this?

[isaach]

Yes. But I expect it’ll be at least a few days before we get a fix out. Thanks for whatever patience you can muster in the meantime.

[boibucom]

Same issue here, its around 1 week now with geocode function not working. could it be related somehow to the new Twitter search capabilities announced 1 week ago ?

[Yunxi1987]

The problem still exist. When will this be fixed?

[andypiper]

As @isaach mentioned just 2 days ago, we are aware of the issue and working to resolve it, but it may be a few days. We apologise for the disruption to your applications, and appreciate your patience. We’re hopeful that we can get a fix deployed soon, but some things take time

[isaach]

Hi all, an update on this issue: there are in fact two separate aspects at work

1. Low search coverage of explicitly-geotagged tweets; and
2. Lack of fallback to profile location for geo searches

Yesterday we deployed a fix for (1) and you should see improvement already in the API. We’re working on a fix for (2) as well; I don’t yet have a timeline but will keep you posted.

[lampos]

Have you managed to develop any timeline for issue (2)?

[andypiper]

No news to share on this at present, but we are aware and continue to work on it.

[judotens]

this issue still exist

[andypiper]

As we said, we have resolved part of the issue, but the fallback to profile location for geo searches has not yet been finalised.

This is part of a significant set of changes on the search backend, so it may take some time for the second part of the issue to be resolved. Unfortunately we need to set an expectation of weeks rather than days before a full solution is likely to be in place.

We are very sorry for the inconvenience this is causing. This is obviously a very frustrating situation for you all in our developer community, but there’s only a limited rate at which we can get this particular issue finalised as there are more parts in motion than may be apparent.

Thank you so much for your patience and understanding!

[RobinMeisel]

Thanks for the work you are doing to rectify the issue, however in the interim our Twitter Ads campaigns for targeted audiences is suffering as we are unable to geolocate individuals to include in the campaigns. Is there an alternate source of twitter data to obtain geo-located searches?

[azrael]

Thanks to @isaach for the head’s up on this thread (started my own thread a couple of weeks ago). It’s been about three weeks. Thanks for working hard on this guys And would love it if it were back up by Christmas

[markzohar]

Are you certain that issue #1 has been fixed? We’re still seeing very low search coverage for explicitly geo-tagged tweets where we used to receive a significantly larger data set before. Any further updates would be most appreciated. Thanks!

[lampos]

+1

[mykopon1]

I must to confirm that the problem in issue 1 is not fixed, please hurry up, my startup is going to crumble.

[SKHardcastle]

My results are still sparse as well. This issue is not fixed. Can you please provide an ETA?

[isaach]

Correct, the issue is not fixed. Results will continue to be sparser than before until we’re able to restore the “fallback to profile location” functionality. We’re working on that but don’t have a firm timeline; however, I’m not expecting a fix in 2014.

Internally we’re tracking this issue as PREL-11171.

If folks are noticing tweets which are geotagged and should be returned in search, but are not, please provide details: the search query being used and links to tweets which should be in the results but aren’t.

[lmudge]

We are still observing this bug where the search API does not fall back to profile location when tweets are not geocoded. Are their any updates on when this might be fixed? Are there any geographical limits to this bug? We are in Australia.

[isaach]

Engineers are working on it, but I’ve no update on ETA. There aren’t geographical limitations.