ok - this is a major bummer, but thanks for confirming. we'll start to investigate and potentially put together a fix.
On Thu, Feb 25, 2010 at 12:44 PM, Tim <timbric...@gmail.com> wrote: > Ed and Raffi, > > We use the #wxreport tag. And we had been using the follow atom > search to query twitter about once every five minutes - > > http://search.twitter.com/search.atom?q=%23wxreport&rpp=100 > > My last tweet sent from my droid should have been geocoded. > > user:timbrice17 > time:Thu, 25 Feb 2010 16:23:18 +0000 > text:#wxreport lots of clouds. > geo:null > > I have geocoding turning on both my phone and my twitter page. > > Tim > > > On Feb 25, 1:10 pm, Raffi Krikorian <ra...@twitter.com> wrote: > > hi tim. > > > > do you have an example of a tweet that you think should have geodata that > is > > not showing up with geodata on search? > > > > if one exists, i believe, that's a bug and we'll look into it. > > > > On Thu, Feb 25, 2010 at 8:36 AM, Tim <timbric...@gmail.com> wrote: > > > I'm working on the National Weather Service's Twitter Storm Report > > > Project. We are pulling tweets with our search hash tag and plotting > > > them on a map. We had been using an atom search to get the geocoded > > > lat lon pairs, but about three days ago all the tweets started coming > > > in with geo=null. It appears the same for the json calls. So what > > > has changed and what is the best way to get the location information > > > from the geotagged tweets. Thanks for your help. > > > > > Tim > > > Forecaster NWS - El Paso > > > > -- > > Raffi Krikorian > > Twitter Platform Teamhttp://twitter.com/raffi > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
