Los Angeles police reports — 2024-06
Los Angeles's June 2024 slice on LocalCrimeVault currently holds 8,002 LAPD incidents with a report date in 2024-06. The rows come from Los Angeles Police Department records on LA Open Data. Eight thousand two is city-wide monthly report volume as indexed, not a Pride-weekend scoreboard and not a conviction file. Later extracts can still move the figure.
Key figures
- 8,002 Los Angeles LAPD incidents in this index have a report date in 2024-06.
- Cite 8,002 as the current harvest; later extracts can move.
- No Pride or festival subtotal is published.
- Counts are police reports, not convictions.
June report dates, not a parade ledger
The 8,002 rows are every indexed LAPD incident whose report date falls in 2024-06 in this harvest, across published crime-code categories. Pride events, school-year endings, and early-summer beach hours are not packet subtotals. If those days produced reports, they sit inside 8,002 when the report date is in June. This page will not attribute the month total to any march or festival.
Report date is the membership rule. An occurrence in May that was reported in June is in. A June occurrence reported in July is not in this slice. The packet does not quantify that lag.
Crime-code labels on the overlay are LAPD's published strings. Filter for one type if you need it. The month page does not recode charges and does not publish a type mix, because type counts are not in the facts.
Los Angeles in 2024-06 is 8,002 indexed LAPD incidents with report dates in 2024-06 in this harvest. Pride-weekend calendars are not a cell. March-route pins are report locations, not a parade statistic. Crime-code labels stay as LAPD published them. LocalCrimeVault does not merge similar labels into a cleaner list. Filter the overlay if you need one published category.
Division geography is still city-wide
LAPD geographic division names appear when LAPD published them. The 8,002 headline belongs to Los Angeles as a whole, not to Hollywood, not to a parade route, and not to a council district.
Corridor pins along march routes, if they look dense in a June table, are report locations. They are not a packet fact about event crime. Offset coordinates are not venue identifications.
Blank division fields still count toward 8,002. Filtering them out of the overlay will shrink the visible set below the headline.
On the 2024-06 overlay, LAPD geographic division names are the geography this Los Angeles index supports when LAPD published them. The 8,002 headline is not Hollywood, not Central, not Newton, and not any other single division. Council districts, Census tracts, and informal Westside or Valley nicknames are different maps. They will not add to 8,002 unless the division field is the field LAPD stored. Location fields are often offset to a block or reporting area. They are not door-level identifications. Blank division fields still count toward 8,002. LocalCrimeVault does not fill them. Stay with the division table and the city-wide 8,002 when you cite 2024-06.
Working the 2024-06 table
Sort by date, crime-code category, or division. Arrest fields are not convictions. Missing coordinates stay blank. LocalCrimeVault does not impute geography.
Later harvests can move 8,002 as LAPD adds late rows or revises old ones. Cite the integer as the current indexed count for 2024-06 report dates.
The 2024-06 table is the working surface for these 8,002 rows. Sort by date, by published crime-code category, or by geography. An arrest field, if shown, is still an attribute of a LAPD report. It is not a charging decision and not a guilty finding. Unfounded or later-reclassified rows can remain until the source extract changes. Missing coordinates stay missing. CAD events that never became LA Open Data rows sit outside the total. Unreported events never enter 8,002. Sealed or restricted records that LAPD does not publish never enter 8,002. If a type filter reduces the table, the caption should say the slice is no longer the city-wide 2024-06 headline. LocalCrimeVault does not reclassify charges inside the 8,002 mix.
What 8,002 is not
It is not 911 call volume, not unique defendants, and not a prosecutor file. Unreported events never enter the extract. Sealed records LAPD does not publish never enter the 8,002.
This page does not compare June 2024 to May or July. Those other counts are not in this packet. Keep 8,002 attached to 2024-06.
Hub, overlay, and citation
The 2024-06 overlay is the live table for these 8,002 rows. The Los Angeles hub is the parent city view for other months, offense types, and division pages. Use the hub when June is the wrong window.
Citation: 8,002 LAPD incidents with a report date in 2024-06, indexed on LocalCrimeVault from LA Open Data. Counts are reports, not convictions. LocalCrimeVault does not reclassify LAPD charges.
A durable citation for this page names the agency, the date field, the month, the integer, and the indexer: 2024 LAPD incidents with a report date in 2024-06, indexed on LocalCrimeVault from LA Open Data. Add that counts are reports, not convictions, and that report date can differ from occurrence date. If you filtered the overlay to one type or one division, say so; that subset is no longer 2024. Later harvests can move the integer as LAPD adds late-submitted rows or revises old ones. Do not mix this 2024-06 total with another month's count on a chart unless that other integer is actually in hand from its own packet. This file's facts support 8,002 only.
Documenting the 2024-06 harvest for Los Angeles
Los Angeles 2024-06 remains 2024 indexed LAPD incidents with report dates in 2024-06 in this harvest. The overlay is the live table. The city hub is the parent view for other months and for type or geography pages that are not limited to 2024-06. Keep the reports-not-convictions clause next to 2024. LocalCrimeVault does not dramatize individual cases and does not turn 2024 into a ranking of neighborhoods, boroughs, or divisions.
Open data lags live dispatch. 2024 is the published extract LocalCrimeVault indexed for 2024-06, not a live CAD feed and not a promise that a portal query tomorrow returns the same integer. Record the month label 2024-06 next to 2024 if you republish the figure so a later snapshot is not silently mixed into the same sentence.
Questions
- How many LAPD incidents are indexed for June 2024 in Los Angeles?
- LocalCrimeVault currently indexes 8,002 incidents with a report date in 2024-06. The source is LA Open Data. The mix includes published crime-code categories in this harvest. The figure counts police reports, not convictions. Later extracts can still move the integer.
- Does 8,002 break out Pride-weekend reports?
- No. The packet has one month total. Event-weekend reports, if they exist in this extract, are inside 8,002 when the report date falls in 2024-06. Filter the overlay by date. This page does not publish a Pride or festival subtotal.
- Is the June total a Hollywood-only figure?
- No. 8,002 is city-wide for Los Angeles as indexed. Division names appear when LAPD published them. Parade-corridor pins, if denser, are report locations, not a packet fact about event crime. 8,002 is city-wide for Los Angeles. Lapd geographic division names appear when the source published them. Some rows lack geography. Filter the overlay for a single LAPD geographic division; do not treat the headline as that area's volume. Block-level pins are not household identifications.
- Does a June 2024 LAPD row mean a conviction?
- No. Public incident rows are reports. Arrest fields are not court findings. LocalCrimeVault indexes LAPD incidents by report date and does not reclassify charges. Public incident rows for Los Angeles in 2024-06 are LAPD reports across published crime-code categories. An arrest field is not a court finding. LocalCrimeVault indexes by report date and does not treat 8,002 as a guilty-finding total. Court outcomes live in a different system.
Los Angeles Police Department incidents via LA Open Data, indexed on LocalCrimeVault. Counts are reports, not convictions.