Hi,
So I just started using the full archive search endpoint from v2 with an academic research status.
I know that Tweepy’s “search” endpoint allows you to specify a location (in coordinates, bounding box, or whatever), then retrieves tweets that are geotagged with that location. If no geotag, Tweepy automatically falls back to the location associated with the Twitter profile.
In v2 (using searchtweets), the only way to specify location is inside the query, which then only returns geotagged tweets (i.e. very small number of tweets). Is there a way to fall back on the profile the same way Tweepy does?
The only way I see would be to manually parse through the expansions or user fields to find the profile’s location, but that’s pretty complicated and only retrieves location after pulling the data (no guarantee the tweets would be distributed equally across locations of interest).
Any ideas are welcome. Thank you 
I don’t think it’s possible since the two APIs are different - v2 queries Search Tweets - How to build a query | Docs | Twitter Developer Platform don’t have an equivalent of geocode Standard search API | Docs | Twitter Developer Platform that falls back on profile location like that.
