Bellingcat's Online Investigation Toolkit
  • About
  • Most Used
  • New Tools
  • ⚒️Categories
    • Maps & Satellites
      • Maps
      • Satellite Imagery
      • Street View
    • Geolocation
    • Image/Video
      • Reverse Image Search
      • Facial Recognition
      • Metadata
      • Misc
    • Social Media
      • Discord
      • Facebook
      • Instagram
      • LinkedIn
      • Reddit
      • Telegram
      • Tiktok
      • Twitter/X
      • Vkontakte
      • Youtube
      • Other Networks
      • Multiple Networks
      • International
    • People
    • Websites
    • Companies & Finance
    • Conflict
    • Transport
    • Environment & Wildlife
    • Archiving
    • Data Organization & Analysis
  • 📖Resources
    • Guides & Handbooks
    • Education
    • Newsletters & Toolkits
    • Stay Safe
  • More
    • All Tools
      • 4plebs
      • 527 Explorer
      • About Maps and Satellites
      • ACLED
      • AllTrails
      • Apollo Mapping
      • Apple Maps
      • Archive.today
      • Atlos
      • Auto Archiver
      • AutoStitch
      • Azure AI Video Indexer
      • Baidu Maps
      • Bellingcat OpenStreetMap Search
      • Bing Maps
      • Blackbird
      • Blender
      • Bluesky Insights
      • BskyFollowFinder/Bluesky network analyzer
      • BskyThreadReader
      • Bulletpicker.com
      • CAT UXO
      • China-related resources
      • Chronotrains
      • CITES Trade Database
      • Companies House
      • Convert Geographic Units
      • Datawrapper
      • DeHashed
      • DiscordLeaks
      • Distill.io
      • DomainTools Whois Lookup
      • Earth Explorer
      • Earth Online
      • EDGAR Suite
      • EDGAR
      • Equasis
      • Etherscan
      • EU consolidated corporate registers
      • ExifTool
      • F4Map
      • FaceCheck.ID
      • FlightAware
      • Flightradar24
      • Forensically
      • GeoHints
      • Gephi
      • Ghunt
      • Global Fishing Watch Map
      • Global Forest Watch
      • Global Monitoring System - ECOSOLVE
      • Global Suppliers Online
      • Google Earth Engine
      • Google Earth Pro
      • Google Flood Hub
      • Google Lens
      • Google Maps
      • GovMap
      • GPSJam
      • Have I Been Pwned
      • Hitta.se
      • Hoaxy
      • Hugin
      • Hunchly
      • ICANN Lookup
      • ICIJ Offshore Leaks Database
      • ImportGenius
      • ImportYeti
      • Index Database
      • Instagram Location Search
      • Instant Data Scraper
      • Intelx.io
      • InVID
      • KartaView
      • Leak-Lookup
      • License Plate Maps
      • LittleSis
      • Liveuamap
      • Logseq
      • Lumen
      • Maigret
      • Maltego Graph
      • MapChecking
      • Mapillary
      • MapSwitcher
      • MarineTraffic
      • Meta Content Library
      • MW Geofind
      • Name Variant Search
      • Namechk
      • NASA Firms
      • NASA Worldview
      • NeutrOSINT
      • North Data
      • Obsidian
      • OCCRP Aleph
      • Open Measures
      • Open Ownership
      • Open Source Munitions Portal
      • OpenCorporates
      • OpenSanctions
      • OpenSecrets
      • OrbTrack
      • Osint Tools Map
      • Overpass Turbo
      • PeakVisor
      • Picuki
      • PimEyes
      • Pinpoint
      • PixPlot
      • Planet Labs
      • QGIS
      • Quick geolocation search
      • Radar Interference Tracker
      • RAWGraphs
      • RootAbout
      • RuPEP
      • SanctionsExplorer
      • satellites.pro
      • Search by Image
      • Sentinel Hub Playground
      • ShadeMap
      • Shadow Finder
      • ShadowMap
      • Sherlock
      • Skopenow
      • SkyFi
      • Snap Map
      • Strava
      • Suncalc
      • Telegago
      • Telegram Group Joiner
      • Telegram Phone Number Checker
      • TelegramDB
      • Telemetrio
      • Telemetry
      • Telepathy
      • Tencent Maps
      • TGStat
      • The Information Laundromat
      • TinEye
      • TrueCaller
      • TruffleHog
      • Twitter Advanced Search
      • Twitter Location Search
      • Twitter Video Downloader
      • Umbra Space
      • UN Comtrade Database
      • UNOSAT Analyses
      • Uwazi
      • VesselFinder
      • Wayback Machine
      • Web Archives
      • What CMS
      • WhatsMyName
      • Who posted what?
      • Whoxy
      • Wikimapia
      • Wikipedia list of registers
      • WildEye
      • Wildlife Trade Portal
      • xIFr
      • Yandex Maps
      • Zotero
Powered by GitBook
On this page
  • URL
  • Description
  • How does it work?
  • How to use geocode location search operators
  • What problem does it solve?
  • Use cases
  • Cost
  • Level of difficulty
  • Requirements
  • Limitations
  • Ethical Considerations
  • Tool provider
  • Guide
  • Advertising Trackers

Was this helpful?

Edit on GitHub
Export as PDF
  1. More
  2. All Tools

Twitter Location Search

Discover real-time conversations and trends in any area with X's built-in location search. Search by latitude and longitude coordinates or distance for targeted local content.

Last updated 4 months ago

Was this helpful?

URL

Description

Users can discover posts from specific geographic areas by utilizing X's built-in location search tool. This feature enables targeted searches based on proximity, allowing users to find relevant content within a designated radius.

How does it work?

Understanding how location data is incorporated into the platform is key to effectively leveraging location-based searches. , users have the option to share location details on posts. The platform seems to figure out where a tweet is from by looking at a few things: (1) The location information a user provides, (2) Guessing by user profile (3) Using a user’s device location, if enabled.

Self-reported location vs. Profile location

X frequently uses these two types of location data.

  1. Manual User-Added Location: This allows users to directly add a location to posts and is displayed below the post.

  1. Profile Location: In the absence of a user-specified location, X may approximate it based on factors such as the location the user specifies on his/her account profile.

Location from the user's device

How to use geocode location search operators

On the search bar, users can use the following search operators in addition to their subject-matter keywords:

  • Use keywords like "near:[cityname]" to search within a certain area. For example, "near:Chicago" finds tweets around Chicago.

  • Combine both search operators "near:chicago within:2mi"

For more specificity, use latitude and longitude coordinates. Search using "geocode:[latitude,longitude,radius]" For example, "geocode:40.7128,-74.0060,10mi" for New York City.

What problem does it solve?

For open-source researchers, this tool helps find the signal through the noise. X's location-based search feature enables users to narrow down posts originating from specific geographic areas among a vast amount of content. This functionality facilitates the discovery of local trends, events, and conversations.

Use cases

Open-source researchers may find this tool helpful for tracking crises and events:

  • Real-time Monitoring: Pinpointing locations of protests, conflicts, or natural disasters.

  • Identifying Affected Areas: Determining regions experiencing human rights violations or humanitarian crises.

  • Corroborating Ground Reports: Verifying claims of incidents through geolocated content.

  • Spot relevant local conversations and identify possible local experts or leads in a location in question.

Cost

Level of difficulty

Requirements

  1. A user account in X/Twitter

  2. Mobile or desktop device

  3. Internet connection

Limitations

  1. Reliance on User’s Report of Data/Location Spoofing

Self-reported location affects the reliability of results in two ways primarily: (1) Incomplete data set: X relies on users to share their location, but many don't. This means location data can be incomplete. (2) Location spoofing: it is possible that users report an incorrect or misleading location. And because the location is entered manually, it can be easy to fake this information. It's essential to remember that X's location estimates aren't always accurate.

  1. Limited Historical Data

  1. Transparency

To mitigate these limitations, users should avoid location-only searches and take advantage of other search filters provided by the platform.

  1. Inability to Distinguish Between User-Reported Location and Profile Location

Based on our tests, the "near:" search operator sometimes produces irrelevant results due to the platform's limitations in accurately determining post locations. The tool sometimes struggles to differentiate between a user's profile location and actual location where a post was created. This leads results that include posts from people who simply live in the area, not necessarily those related to a specific event or topic being searched.

Ethical Considerations

  • Individual Privacy: Be mindful of individual privacy. While public tweets are accessible, avoid exposing personal information of individuals without their consent, in particular if they are not involved in any incidents of public interest.

  • Transparency: If sharing findings publicly, consider anonymizing personally identifiable information to protect individuals' privacy.

  • Data Reliability: Be aware that Twitter's location data is not always accurate. Avoid drawing definitive conclusions based solely on location data without corroboration from other sources

Tool provider

X.com, USA

Guide

See Bellingcat’s Case Study into tweets during the COVID-19 crisis in India showing the scarcity of precise geolocation data, requiring multiple geocoded queries to approximate geographic distribution:

Advertising Trackers

Page Maintainer

Afton

If users choose to turn on location settings on their devices, X canthe GPS coordinates of this device at the time of the post. This is particularly helpful when users want to take advantage of the search results near their respective locations.

You can also set a distance using "within:[radius]" to narrow down results within a certain radius in , for example “within:2mi”

Geocoded searches are more effective for recent posts. Older posts often lack location tags, reducing the volume of retrievable data. For instance, user profile location information used to georeference tweets only for the most recent week, leading to a drop in older tweet volumes. The 2021 study finds that: "user profile location information is only used to georeference tweets for the most recent week (seven to eight days, approximately). The effect of this is that recent tweet volume appears much greater than that from more than a week ago." In a separate test done by a Global Authentication Project volunteer in July 2024, the tool was tested to find historical location data. The conclusion was that this limitation still seems to exist.

)

According to to building a query, distance-based searches can be limited to 25 mi. This means they can exclude relevant tweets just outside the specified area. For instance, an investigator is researching environmental impacts in a 50-mile radius around an industrial site. X’s search may only allow a smaller radius, potentially missing relevant tweets from just outside the boundary.

According to it's important to note that the platform's methodology for determining a tweet's location is not fully transparent, potentially impacting the precision of location-based queries.

identify
mi or km
Bellingcat found
Radius limited to 25 mi (40.23 km
X’s guide
this case study,
https://www.bellingcat.com/resources/2021/05/19/geofenced-searches-on-twitter-a-case-study-detailing-south-asias-covid-crisis/
https://twitter.com/explore
According to X
This post shows a post with an explicit location reported by the user. This location info appears at the bottom of the post. For example, we are interested in discussions about the art community around Estes Park, Colorado. On the search bar, we enter our search term "art" and the location we are interested in, "near:estes-park"
On the other hand, user profiles sometimes indicate where they are based as shown in this image. The platform may then use this information when generating location-based search results.
If you're looking to find posts near your current location, there's a quicker method available. Use the “posts near me” location feature. Here are the steps: Open X on a browser or the mobile app, and enter a hashtag or search term. Choose “Near you” under the “Location” heading to filter the search results to show only posts from nearby.