Unexpected 400 errors using venues/search and the browse intent

[Νικόλας Τουμπέλης]

Hi, 

I've been using the new venue browse intent functionality quite extensively using both the sw/ne and the radius approaches. I've been getting several unexpected 400 errors, that my geographic area is too big, e.g.:

PATH: venues/search

PARAMETERS: {

    intent = browse;

    ll = "40.659221,22.947004";

    "oauth_token" = xxxxxxx;

    radius = 421;

    v = 20111030;

}

META:{

    code = 400;

    errorDetail = "Your geographic boundary is too big. Please search a smaller area.";

    errorType = "param_error";

}

I might make, say, five of these calls in nearby areas, and get one error in between.

Thanks,

--

Nick Toumpelis

iOS Software Engineer

Thessaloniki, Greece

email: nickto...@gmail.com

twitter: nicktoumpelis

[Akshay Patil]

Is it consistently with radius, or with both approaches? Can you post the full URL of your request (oauth_token hidden)?

~ak
--
Akshay Patil / Foursquare Platform Evangelist
@akdotcom / @foursquareapi

2011/10/30 Νικόλας Τουμπέλης <nickto...@gmail.com>

--
To post to this group, send email to foursqu...@googlegroups.com
 
http://groups.google.com/group/foursquare-api

[Νικόλας Τουμπέλης]

Hi Akshay,

https:/api.foursquare.com/v2/venues/search?intent=browse&v=20111031&ll=42.350298%2C-71.041385&oauth_token=xxxxxx&radius=178

https:/api.foursquare.com/v2/venues/search?intent=browse&v=20111031&ll=0.000005%2C-0.000005&oauth_token=xxxxxx&radius=121

https:/api.foursquare.com/v2/venues/search?intent=browse&v=20111031&ll=37.937056%2C23.946751&oauth_token=xxxxxx&radius=190

https:/api.foursquare.com/v2/venues/search?intent=browse&v=20111031&ll=38.253094%2C20.647076&oauth_token=xxxxxx&radius=189

These happen on and off but way too often. I also encountered those using the sw/ne approach.

Thanks,

Nick

[Νικόλας Τουμπέλης]

Hi Akshay,

I'm still seeing this happen. Am I doing something wrong?

Thank you,

Nick

On 31 Οκτ 2011, at 11:56 μ.μ., Akshay Patil wrote:

[Akshay Patil]

Hi Νικόλας,

We had an issue where venues were indexed without their parent categories. 
We're currently backfilling the index with this information -- it should be 
completed over the next day or two. Sorry about this! 

~ak
--
Akshay Patil / Foursquare Platform Evangelist
@akdotcom / @foursquareapi

2011/11/2 Νικόλας Τουμπέλης <nickto...@gmail.com>

[Νικόλας Τουμπέλης]

Thanks!

[Engin Kurutepe]

Hi Akshay,

I keep encountering these errors as well. I only tried it with the range parameter around 1000m to do a local search around our users. It usually works but when it fails it fails on retries as well and also with different queries. 

One example query is:

 https://api.foursquare.com/v2/venues/search?client_id=xxxxxx&client_secret=xxxx&ll=52.485852,13.438730&radius=1000&intent=browse&v=20111101&limit=10&query=ba

I am doing something wrong? 

Cheers,

E.

[Akshay Patil]

Can you e-mail a...@foursquare.com with more details? Namely: specific queries and the venues that should be returned but aren't?

~ak
--
Akshay Patil / Foursquare Platform Evangelist
@akdotcom / @foursquareapi

[Engin Kurutepe]

Hi Akshay,

It seems to be working for now. I'll contact api@foursquare directly if it starts happening again.

Thanks for the tip.

Cheers,

Engin.

[Fehmi Can Saglam]

Hi Akshay,

I am facing the same problem with this query:

https://api.foursquare.com/v2/venues/search?intent=browse&radius=2000&oauth_token=***&ll=xx,yy

The query works most of the time but it sometimes fail and return "Your geographic boundary is too big. Please search a smaller area."

What else information do you need?

[Akshay Patil]

Thanks for the reports -- we're investigating this bug and think we've (hopefully) found the culprit issue.

~ak
--
Akshay Patil / Foursquare Platform Evangelist
@akdotcom / @foursquareapi

--

[Akshay Patil]

This issue should now be fixed

~ak
--
Akshay Patil / Foursquare Platform Evangelist
@akdotcom / @foursquareapi

[Engin Kurutepe]

Hi Akshay,

It seems to be working great. Thanks a lot!

Cheers,

E.