It's also worth noting that while the above example may not be pulling a place, the API call I'll be including tomorrow uses the latitude/ longitude pair pulled from the Google Maps API V3 geocoder with the same outcome.
On Dec 20, 7:22 pm, Corey Ballou <ball...@gmail.com> wrote: > Here's my non API call searches from search.twitter.com with a 5mi > range: > > keg near:"121 W Trade St, Charlotte NC" > within:5mihttp://search.twitter.com/search?q=+keg+near%3A%22121+W+Trade+St%2C+C...http://search.twitter.com/search?q=&ands=keg&phrase=&ors=¬s=&tag=&;... > > If you extend the radius to 10mi, you'll get significantly more > results. My office is in the heart of Charlotte at a major > intersection as well (Trade St and Tryon St). > > http://search.twitter.com/search?q=+keg+near%3A%22121+W+Trade+St%2C+C...http://search.twitter.com/search?q=&ands=keg&phrase=&ors=¬s=&tag=&;... > > Based on the results returned from the 10mi radius, it seems to > indicate that even though I tweeted from a Place, the tweet is being > generalized to the parent city bounding box of Charlotte, NC. It just > doesn't feel right; does it have to do with an optimization to avoid > the heavy cost of performing calculations for sorting by distance? > I'll update this post with the API call tomorrow morning when I get in > the office. I've got it tucked away in the error logs with no root > password in my keychain. > > In the meantime, any clarification or light you can shed on how you > guys are calculating proximity would be much appreciated. > > Regards, > Corey > > On Dec 20, 5:36 pm, Matt Harris <thematthar...@twitter.com> wrote: > > > Im not entirely clear on how to reconstruct the query you are trying to > > make. Can you share the full Search URL request you are making so we can > > take a look. > > > Thanks, > > @themattharris > > Developer Advocate, Twitterhttp://twitter.com/themattharris > > > On Mon, Dec 20, 2010 at 1:16 PM, Corey Ballou <ball...@gmail.com> wrote: > > > While running some tests on the search API I noticed a potential issue > > > with the search API's proximity handling when filtering by places. If > > > I specify a radius of 5 miles with a search term of "keg" and the > > > address of my office building, I would expect to retrieve a previous > > > tweet of mine: > > > > Tweet in question: > > >http://twitter.com/cballou/statuses/15770007518584832 > > > > The status update in question was created with an associated place_id > > > of my office, which properly maps to the right address. > > > > The place in question (Skookum, Charlotte, NC): > > >https://search.twitter.com/search?q=place%3A5c9b53e1da87e502 > > > > Theoretically, I should be able to search within a one mile radius > > > with the address. In this case, the only way I'm able to retrieve my > > > tweet is to bump the radius up to 10 miles. I've tested this issue > > > using both lat/lon coordinates with my application as well as using > > > your advanced search (search.twitter.com/advanced) with the full > > > address. > > > > Am I missing something here? Are you associating places to the overall > > > city and not the exact lat/lon marker of an address? When I view the > > > place directly, the marker placement is indicative of having the > > > proper lat/lon coordinates. > > > > Let me know if you need any clarification or additional details. > > > > Regards, > > > Corey > > > > -- > > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > > API updates via Twitter:http://twitter.com/twitterapi > > > Issues/Enhancements Tracker: > > >http://code.google.com/p/twitter-api/issues/list > > > Change your membership to this group: > > >http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
