Thanks. Am I correctly understanding that the near parameter uses the location of the users profile and will not use the new geolocation api lat/long data?
On Sep 20, 9:37 pm, John Kalucki <jkalu...@gmail.com> wrote: > It is very unlikely that we would offer a publicly available method on > the streaming API that returned all geotagged statuses. It is much > more likely that we'll offer a parameter to the /1/statuses/filter > method that would be subject to the same limitations as the track > keyword. Such a feature is unscheduled. I wouldn't guess as to when > we'll get to such an implementation. > > In the mean time, the Search API offers the near: parameter. > > -John Kaluckihttp://twitter.com/jkalucki > Services, Twitter Inc. > > On Sep 20, 7:22 pm, "tom.mancino" <tom.manc...@gmail.com> wrote: > > > > > I want to filter the firehouse to a subset of tweets that will have > > valid geodata (lat/long). > > > On Sep 20, 7:54 pm, Raffi Krikorian <ra...@twitter.com> wrote: > > > > hi tom. > > > what are you exactly asking? you can look at any of the timeline methods > > > -- > > > wherever there will be <status> object, there will be geo information if > > > there is geo information available. > > > > does that help? > > > > On Sun, Sep 20, 2009 at 8:38 AM, tom.mancino <tom.manc...@gmail.com> > > > wrote: > > > > > Something like statuses/geolocation that returns public statuses with > > > > geolocation data? Thanks..... > > > > -- > > > Raffi Krikorian > > > Twitter Platform Teamhttp://twitter.com/raffi
