How many homicides were recorded in Washington, D.C. during the last 30 days according to the MPD open dataset?
Executive summary
The specific count of homicides in Washington, D.C. "during the last 30 days according to the MPD open dataset" cannot be stated from the supplied reporting because none of the provided sources publish a concrete, up‑to‑date numerical total for that exact rolling 30‑day window in the materials given here [1] [2] [3]. The MPD maintains a "Crime Incidents in the Last 30 Days" data feed and a daily crime dashboard that are the authoritative places to pull that figure, but the documents in the search results describe the datasets and the dashboard rather than reporting the live 30‑day homicide count itself [2] [3] [1].
1. What the user is asking and why the supplied sources fall short
The user seeks a precise number: how many homicides the MPD’s “last 30 days” open dataset records for Washington, D.C. The materials provided point to where MPD publishes that rolling dataset (the MPD daily crime page and the "Crime Incidents in the Last 30 Days" dataset listing), but those items in the search results are metadata and product pages describing the feed rather than extracts of the feed showing a timestamped homicide total for the last 30 days—so the reporting supplied does not contain the direct numeric answer requested [1] [2] [3].
2. Where the MPD publishes the last‑30‑day homicide metric
MPD’s public crime tools include the daily crime dashboard (District Crime Data at a Glance) and crimecards/DC Crime Cards datasets; the "last 30 days" dataset is explicitly identified in the catalog entries and is compiled from MPD’s ASAP (Analytical Services Application) reports, with violent crime categories including homicide listed among the datasets’ contents [1] [2] [3]. These resources are the authoritative sources for an up‑to‑the‑minute or recent 30‑day total, but the search snippets provided describe functionality and definitions rather than giving a snapshot number that can be quoted here [1] [2].
3. Data definitions and caveats a reader must know
MPD’s published statistics reflect data entered into the department’s records management system as of a stated time (for example "as of 12 am on the date above") and are organized by DC Code offense definitions; those tallies do not necessarily line up with FBI NIBRS Part I reporting definitions and can be influenced by case classification and record updates [1]. The datasets are compiled by “report date” in MPD’s public tools, which affects whether a death appears in a rolling 30‑day extract immediately or only after reclassification or additional investigation [3]. Any single numeric answer should therefore include the time and source snapshot used to extract the count.
4. Conflicting signals and why a reader should verify the live feed
Beyond the technical caveats, reporting and oversight documents raise questions about trust in MPD data that bear on how to interpret any published number: national reporting highlighted large year‑over‑year declines in violent crime based on MPD figures (Justice Department/US Attorney release), while later oversight scrutiny and political coverage have alleged data misclassification or manipulation within MPD—issues the House Oversight Committee and national outlets have flagged—meaning independent verification of a live MPD extract is prudent before drawing conclusions [4] [5] [6]. These are alternative viewpoints that do not invalidate the MPD feed but underscore why citing the exact dataset snapshot is important.
5. Actionable next step to get the exact count
To obtain the exact number the MPD dataset reports for homicides in the last 30 days, query MPD’s live "Crime Incidents in the Last 30 Days" dataset or the DC Crime Cards application (links and dataset entries are named in the catalog metadata provided) and record the dataset timestamp and the homicide count; the dataset listings in the federal catalog and MPD’s data pages are the public entry points for that query [2] [3] [1]. Because the supplied sources do not include the live extract, the precise numeric answer cannot be responsibly asserted here without accessing the live dataset.