This is really a problem for us at http://streamd.in We're getting this error pretty much anytime the user moves around in the map or searches for something. If the 2500km limit has changed it will be good to know what the new way looks like. It seems to me like a broken api when the devs don't know if a call it's going to succeed or fail based on some internal decisions that is not exposed in the documentation. At this point we don't know what the fallback strategy should be for these errors. Perhaps try multiple times until it works and have the user waiting? It does not feel right to get this kind of error and have to provide a code workaround that degrades user experience and ends up sending more request to your servers
2010/5/24 Nick <nick.fritzkow...@gmail.com>: > The issue is more than that, basically anything near:Australia is > being blocked because the radius of australia is above the (i think) > 1349km radius that has been forced. > > So no terms that are near:Australia are working because of the fact > that Australia is larger than your radius limits. > > On May 25, 6:43 am, Taylor Singletary <taylorsinglet...@twitter.com> > wrote: >> Hi Nick, >> >> For scalability reasons, the search API will reject queries that are too >> computationally expensive/complex to service reasonably. You may need to >> refine the radius for that query to work. We're actively tweaking this >> algorithm, and I'll make sure the search team gets the feedback that a query >> like "coffee near:australia" is being determined too complex. >> >> Taylor Singletary >> Developer Advocate, Twitterhttp://twitter.com/episod >> >> On Sun, May 23, 2010 at 10:53 PM, Nick <nick.fritzkow...@gmail.com> wrote: >> > The search term is anything that says: near:Australia ie "coffee >> > near:australia" It seems that since near:australia is a radius larger >> > than 1300km 880mi it is failing because twitter seems to have put in >> > some limitations for the radius. >> >> > On May 24, 3:32 pm, Cameron Kaiser <spec...@floodgap.com> wrote: >> > > > I keep getting the message: Sorry, your query is too complex. Please >> > > > reduce complexity and try again. >> >> > > > Is there a way around this? >> >> > > Post your query, perhaps? >> >> > > In general, no. You might have to combine two less complicated searches >> > into >> > > a single set on your end rather than expecting the Search API to do it. >> >> > > -- >> > > ------------------------------------ personal: >> >http://www.cameronkaiser.com/-- >> > > Cameron Kaiser * Floodgap Systems *www.floodgap.com* >> > ckai...@floodgap.com >> > > -- Backup not found. Abort, Retry, Vomit, Panic, Write Resume File? >> > ----------- > -- Raul Raja
