Good! I'm glad!
On Feb 26, 2010, at 7:47 AM, Tim <timbric...@gmail.com> wrote:
Raffi,
Yeah, our weather tweets are again plotting with the geo tags.
Here are the geo tags from my latest exciting weather tweet:
<georss:point>31.8504 -106.6412</georss:point>
Thanks for looking into it. Keep up the good word. Looking forward
to the new geo stuff coming from twitter. Have a great day.
Tim
On Feb 25, 7:01 pm, Raffi Krikorian <ra...@twitter.com> wrote:
hi tim.
can you try again please? after doing a few things, i then ran a
search for
a user who i know geotags, and it now seems to work?
[ra...@tw-mbp13-raffi ~]$ *curl "http://search.twitter.com/search.atom?q=renonelab
"*
<?xml version="1.0" encoding="UTF-8"?>
...
<entry>
...
<title>RT @edtheplumber Help! My wife rescued this pup! Going
to the vet
tomorrow to get a clean bill of health. Free to (cont)http://tl.gd/bpomi
</title>
...
* <twitter:geo>*
*<georss:point>30.4001 -91.0497</georss:point>*
* </twitter:geo>*
<twitter:source><a href="http://www.stone.com/
Twittelator"
rel="nofollow">Twittelator</a></twitter:source>
<twitter:lang>en</twitter:lang>
...
</entry>
....
On Thu, Feb 25, 2010 at 4:58 PM, Raffi Krikorian
<ra...@twitter.com> wrote:
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
--
Raffi Krikorian
Twitter Platform Teamhttp://twitter.com/raffi
