Oh ... wait ... when you do a search *with* a geocode parameter, you
get user locations and geocodes if the tweet is geotagged. If you do a
search *without* a geocode parameter, you don't get either. Is it
supposed to give those even without the geocode parameter? Is that a
bug? I thought it was a feature!
M. Edward (Ed) Borasky
"A mathematician is a device for turning coffee into theorems." ~ Paul Erdos
Quoting davidloew <davidl...@gmail.com>:
I'm seeing the same thing. I do a status list and I get all of the
tweets and they contain location lat longs. I do a search with json
for geocode= and the tweets have geo=null in them. have a look at
On Feb 25, 12:10 pm, Raffi Krikorian <ra...@twitter.com> wrote:
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.
> Forecaster NWS - El Paso
Twitter Platform Teamhttp://twitter.com/raffi