Hi. Did you manage to solve your issue? I'm faced with the same thing. I need to find a reliable way to retrieve location information from a tweet (i.e. given that the vast majority of tweets do not include lon and lat values). What did you do in the end? Are you willing to share code?
On Feb 18, 7:49 pm, GeorgeMedia <georgeme...@gmail.com> wrote: > My primary reason for consuming the gardenhose is so I can gather > tweets and sort them by location on demand when I need them. I have > the tweets stored in local hourly files and I'm ready to insert them > into the MySQL DB. > > But first... I need to do some scrubbing. I'm primarily interested in > tweets that already have the lon/lat in the location field because > then I can just calculate radius locally and grab all the tweets from > a given radius. > > But I don't want to leave out the people who actually took a second > and put their real location in the Location field. I already have lon/ > lat locations for US cities in my DB and just need to grab usable > CITY, STATE combos to search on/match with what I have. > > So my questions.... > > 1) Should I just ignore/dump any tweets that have an empty LOCATION > field? Because no matter what, if the tweet is geotagged the lon/lat > will be in that field correct? And if it's not geotagged the profile > location info will be there. And if that's not available it will be > empty -- right? > > 2) What do you think would be the best regex (I'm writing in PHP) to > determine whether the field had any real location data in it? > > From what I've seen the most accurate location fields always have > CITY, STATE so I'm assuming checking for a comma is a good idea. But > what else? How is twitter handling this? To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
