> if you are only looking for tweets > that use the geotagging API, then do some post processing to find a > tweet with a populated geo field.
The only way to do this right now is to hammer the search API, because tweets with a populated geo field are needles in a haystack. I've done this for a 500-mile radius centered in San Francisco only to find a tweet or two every several minutes. Geo tweets are so few at this point (I'm guessing on the order of one in a thousand) that they could be thrown into their own in-memory index on a low-end box. Tagging them with a custom field (e.g. geo_data_present:true/false) in the regular search index should be easy. Of course it means regenerating indexes, testing, etc. Understandably this is not a priority for the search team as they must be swamped with more urgent issues, but it would be nice. Diego
