Track drone-related reporting on the existing map
Open Conflict / Military → Drone incidents to filter reports by time window, incident type, source class, country and location basis. Mappable reporting appears on the existing map; selecting a marker or report opens its sources, dates, claim status and location method. Unresolved reports stay available in the list.
The layer distinguishes reported attacks/strikes, interceptions/downings, airport or airspace disruptions, crashes, sightings/incursions, recovery/investigation and denial/correction wording. These are source-report classifications, not independently verified events. Counts represent canonical reports/source records, not unique attacks, aircraft or confirmations.
Broad public feeds with explicit source gaps
The collector scans all usable retained public buckets from the reviewed publisher and social/account feed catalogues, plus the latest UCDP Candidate GED monthly release. At qualification the catalogues contained 556 publisher feeds and 479 public social/account feeds. Configured counts are not the number of independent confirmations, responding feeds or complete platform coverage.
The projection refreshes approximately every five minutes using existing publisher caches; UCDP discovery is checked daily. Original publication, update, capture and historical event clocks remain distinct. UCDP history is provisional and can lag current reporting; choose a longer window to inspect it.
FAA automated source qualification and CENTCOM returned access denials, GDELT document discovery was rate-limited, and ACLED requires account/licence rights. Those are visible gaps rather than represented as connected data. Private sources, borrowed credentials and unlicensed bulk data are excluded.
Locations retain their uncertainty
UCDP coordinates retain their source geographic-precision code. News and public posts receive rounded city-reference anchors through disclosed incident-context and city-name disambiguation rules; publisher headquarters and feed countries are not used as incident locations. Country-only and unresolved locations stay off the map.
City matching is heuristic and can be wrong; anchors are not exact strike sites or affected-area boundaries. Multiple source reports can concern the same event, and a drone can be a weapon, target or part of a combined-weapon report. Original links and attribution remain available for assessment.
Read the same evidence through MCP
The reviewed MCP catalogue adds a drone-incidents route with overview, record, map, detail and source views. Native source pagination and snapshot identifiers remain separate from MCP JSON Pointer/scalar pagination. Existing private military-access controls and source-layer semantics are retained.