That's perfect, thanks Raffi!
On Jul 6, 5:49 am, Raffi Krikorian <[email protected]> wrote: > hi steve. > > there are two different ways to "geotag" a tweet. there is geotagging with > an exact latitude and longitude, and then there is geotagging with a place. > > when you geotag with an exact latitude and longitude, the coordinates (and > geo) attributes will be filled. additionally, if twitter has data for that > area of the world, we will also immediately populate the place attribute > with the contextual information. it is possible that we don't have data for > that location, at which point the place attribute will be empty. > > you can also geotag with a "place" -- that's a neighborhood, a city, state, > point of interest, etc. when somebody does that, only the "place" attribute > is filled. > > take a look athttp://api.twitter.com/1/statuses/show/17536619739.xmlas > that has all the fields populated. > > hope that helps! > > > > On Mon, Jul 5, 2010 at 10:56 AM, Steve <[email protected]> wrote: > > Hi all, > > > I've done a search here for this info, and looked through the docs, > > but I can't find what I'm looking for documented anywhere. > > > What I'm after is a full sample of what data might appear in the <geo/ > > >, <coordinates/> and <place/> tags, when they're populated. At > > present I've only seen some inner <georss:point> tags, but I'm curious > > what else may appear within these. > > > I'm creating a "tweet backup" type thing, and pulling out various data > > items from the tweet to stick into SQL and analyse, and knowing what > > data might be in here would be handy. > > > Thanks! > > -- > Raffi Krikorian > Twitter Platform Teamhttp://twitter.com/raffi
