Search with geocode param is very confusing. Can somebody clarify several points in the docs?

[Fhoenix_Rubicon]

Okay, first, my main question. I get that geocode uses user profile location as a fallback. What I want is to create a GeoRSS only with tweets that have exact lat/long of the place of the tweet. So is there a way to distinguish tweets which provide the place of the tweet from the ones that use location fallback? And is there a way to distinguish tweets that use a generic location as the place of the tweet from the ones that disclose exact coordinates?
I see georss:point in the rss and I don’t know how much I can trust them. Hope I can, because approximated coordinates would break my feed completely.

Second, some observations based on reading the docs.

http://search.twitter.com/api/ tells you that "geocode: returns tweets by users located within a given radius of the given latitude/longitude, where the user’s location is taken from their Twitter profile"
https://dev.twitter.com/docs/using-search Adds that geocode “Attempt to find Tweets which have a place or lat/long within the queried geocode”.
Which is good, but if you only read the first link, you get the wrong idea.

Finding that twitter provides GeoRSS is actually semi-hard. GeoRSS almost does not get mentioned and http://search.twitter.com/search.rss does not include GeoRSS elements (of course http://search.twitter.com/search.atom does, but I found it the hard way). I think some publicity for this feature wouldn’t be bad.

[rno]

Hey Fhoenix,

If the tweet is geotagged, the google:location RSS element will be prefixed with GeoAPI. This is easier to detect in atom format as you’ll get an extra georss:point element. If the element is present, the Tweet is geotagged. Otherwise, it’s a fallback to the tweet author’s location (as defined in its profile).

Hope that helps!

[Fhoenix_Rubicon]

Yes, thank you, this helps a lot.
But to be precise, what exactly does “tweet is geotagged” mean? What happens if the twitter client chooses to disclose location of the tweet (for example London), but not lat/long? Will I get a georss:point with London’s center (this would be bad for my feed btw, but might be useful to somebody’s else)? Or will georss:point be missing?

[thomasreggi]

I am having a simular issue I am trying to take a place id such as “a27ab3073b0ee274” which is to a starbucks and retrieve the tweets (json) with this geotag such as https://twitter.com/#!/places/a27ab3073b0ee274. Can anyone help?

[niall]