Geocoded search queries returning subset of data

johnbarratt · 2013-03-28T21:00:32.000Z

Interesting, so there are actually no results that have been geocoded in the result set, so if you have changed providers, then they aren’t providing any functionality for search at the moment.

This has resulted in at least a 10x drop in results. Only a relatively small portion of people have either a lat/lon in their profile, or attached to their tweet. The above search I provided for the web search interface is mirroring the problem :

https://twitter.com/search/realtime?q=near%3Amelbourne&src=typd

Thanks!

matevzg · 2013-03-29T07:03:33.000Z

The following query…

(":)" OR “:))” OR “:-)” OR “: )” OR “:D” OR “=)” OR “;-)” OR “;)” OR “;))” OR “:(” OR “:-(” OR “: (” OR “;-(” OR “;(” OR “;((”) AND (geocode:“50.86594,10.30086,400km”)

…was returning approx. 25.000 results / day. Since March 27th it is returning 1.000 results / day. Other geocode based query are exhibiting the same behavior making them unusable.

StiaanMaree · 2013-03-29T11:52:00.000Z

Hi Taylor,

I’m also noticing a drop to less than 10% like everyone else, if it helps, here is another example query:

https://api.twitter.com/1.1/search/tweets.json?geocode=-31.203405%2C26.938477%2C1350km&count=100&result_type=recent&q=i’m

episod · 2013-03-29T14:48:26.000Z

Thanks, our search team has identified a bug that’s arose as part of the transition. It may take some time to resolve. I’ll update this thread when I have another update to share. Thanks everyone for the examples!

matevzg · 2013-03-29T16:14:11.000Z

Taylor thank you for your prompt investigation. Could you please give an example of a time frame this will be solved in, so we could have something credible for our customers/users?

episod · 2013-03-29T22:07:26.000Z

It looks like it won’t get resolved for about a week – hopefully quicker.

johnbarratt · 2013-03-30T00:20:48.000Z

Given it appears it may still take quite some time, is it possible for you to rollback the code to the known working geocoding, until this is properly resolved with the new setup? Particularly given this is seriously affecting so many services? Thanks!

TVBookClubbers · 2013-03-30T07:32:40.000Z

Am I right in assuming this issue explains why the ‘near this place’ filter on twitter advanced search is now only filtering about 10% of normal content? Is this problem effecting all users?

matevzg · 2013-03-30T23:09:14.000Z

Yes, as it seems it should be affecting all users.

TVBookClubbers · 2013-03-31T08:01:43.000Z

Many thanks for confirming that. I’m surprised there isn’t more internet chatter about this bug. There must be many developers/users pulling their hair out with frustration. At least the twitter people are ‘on the case’. Hope a solution is found sooner than a week!.

matevzg · 2013-03-31T09:37:21.000Z

We are seeing much more that 10:1 drops in the number of results. In some cases, we are seeing 50:1 drops. Practically no results.

Here’s a picture of such a case: http://twitter.yfrog.com/z/h621edp

episod · 2013-04-01T14:58:57.000Z

Unfortunately not, we’ll just have to wait for the fix.

johnbarratt · 2013-04-03T10:33:47.000Z

OK, Is there an updated ETA on this? This is seriously affecting our site (http://trendsmap.com/) along with a number of our clients, so would be great to at least have something more concrete to work with. Thanks!

TVBookClubbers · 2013-04-03T16:29:38.000Z

As soon as possible please!! Thanks.

joshyftw · 2013-04-05T07:44:19.000Z

Any update on ETA to fix?

matevzg · 2013-04-06T06:39:21.000Z

Taylor, can you update us on this issue? Thanks.

EmcienRuss · 2013-04-06T18:11:12.000Z

Any update on when this will be fixed?

BrianMulawka · 2013-04-08T14:49:28.000Z

Has anyone seen a fix for this? Or at least as ETA?

johnbarratt · 2013-04-09T00:09:15.000Z

+1

drmcameron · 2013-04-09T02:48:06.000Z

+1
I’ve seen some spikes in our feeds over the 5th and 6th and a 55 minute flat spot early am on 7th, but there appears to be no fix yet?