Thanks Chad, mostly just wanted to get something into the search indexes for
anyone else looking. :) I'd never thought of using Pipes, that is a very
neat approach, feels more elegant than requiring PHP in a lot of situations.
cheers,
Pete
On Wed, Feb 18, 2009 at 1:30 PM, Chad Etzel <jazzyc...@gmail.com> wrote:
>
> argh, hit send by mistake.. I was going to add:
>
> Your sample looks great, and I may even start using it for some other
> projects where the pipe would not be as useful. Thanks for posting
> the link, very nice.
>
> I wasn't trying to trump your example, merely posting another way to
> get around the non-"near within" sytanx availability on the API side.
>
> -Chad
>
> On Wed, Feb 18, 2009 at 4:28 PM, Chad Etzel <jazzyc...@gmail.com> wrote:
> > I use this Y! Pipe for TweetGrid to accomplish geocoding:
> >
> >
> http://pipes.yahoo.com/pipes/pipe.info?_id=27c113188a1f89baab07f2d133bc3557
> >
> > it was lovingly copied and edited from a similar pipe by @JohnDBishop
> > (with permission).
> >
> > I use this with a json callback (plus some regex matching) to
> > translate between near: within: syntax and geocoding.
> >
> > Anyone is welcome to clone/edit it for their own use.
> >
> > -Chad
> >
> > On Wed, Feb 18, 2009 at 3:17 PM, Pete Warden <searchbrow...@gmail.com>
> wrote:
> >>
> >> I needed a way for users to be able to enter readable place names and
> >> do searches restricted to the neighborhood. The search API only
> >> supports lat,long so I had to implement some geocoding to translate
> >> names into coordinates. I ended up using Yahoo's free GeoPlanet
> >> service, with 50,000 requests possible per month.
> >>
> >> Since I couldn't find any other public examples of how to do this
> >> (though I'm sure this must be in a lot of code out there) I put up my
> >> sample code:
> >>
> http://petewarden.typepad.com/searchbrowser/2009/02/how-to-emulate-near-in-the-twitter-search-api-using-geoplanet.html
> >>
> >> It's a small PHP file, and works just like the normal search API call
> >> but with an additional near argument that gets translated by the
> >> geocoding. I'd love to see some more explanation on the docs wiki of
> >> this sort of workaround for 'near', but it seems that it's only
> >> editable by Twitter employees? Facebook's more open editing policy
> >> seems to work well for them.
> >>
> >> cheers,
> >> Pete
> >>
> >
>
