that is currently unsupported -- right now you will get both. you
could, once receiving the search results, filter on the values in the
<geo> tag that is returned in the search API.
How does this interact with the search mechanism, if at all? i.e. when
I do a near search, I *don't* want tweets that come from people who's
profile sets them near that place, but instead only for *tweets*
marked as near that place.
As you may have seen on the Twitter blog , geotagging is now
available for all users and developers throughout Twitter's APIs.
Specific geotagging methods have been added and existing formats
expanded to accommodate this rich new information.
To get started developing with this API and sending geotweets,
Geotweets now carry the geotag whenever available and whenever they
appear in our REST, Search, and Streaming APIs.
Remember, geotagging is disabled by default on users' accounts.
Encourage your users to enable it by sending them to their settings
page . From that page, a user can turn this feature on by
the "Enable geotagging" checkbox. Alternatively, we're also
a mobile optimized geotagging settings page  that you can send
too as well. As a developer, you can determine whether a user has
enabled geotagging by calling the users/show method  or in any
other <user> element returned by the REST API where a user object
shows up -- just look for the geo_enabled flag.
For more hints on how to use geotagging, check out our Geotagging
Practices page  where we have UX mock-ups, hints on how to best
support user privacy, and more.
We're really excited about this feature! And more is coming.
Go get lost. We'll send help.
Twitter Platform Team
ra...@twitter.com | @raffi