Los Angeles police reports — 2024-02

February membership is a date field

The 16,931 rows are incidents with report dates in 2024-02, every published crime-code category included. This page will not convert 16,931 into a daily rate, and it will not blame the calendar length for the total, because those claims are not in the packet. The factual statement is the indexed month count.

Valentine's Day, awards-season civic calendars, and rain-week weather are not packet subtotals. If they produced reports, those rows sit inside 16,931 when the report date is in February. Filter the overlay by date if you need a shorter window.

Report date, not date-occurred, defines the 2024-02 slice. An occurrence in January that was reported in February is in. A February occurrence reported in March is not. This packet does not quantify that lag.

Los Angeles in 2024-02 is 16,931 indexed LAPD incidents with report dates in 2024-02. Do not convert 16,931 into a daily rate; this packet does not support that math. Valentine's Day and awards-season weeks are not broken out. Division blanks still count toward 16,931. LocalCrimeVault does not guess a division from a nearby pin. Arrest fields are not convictions.

Geography without inventing a division ranking

LAPD geographic division names appear when LAPD published them. The 16,931 headline is Los Angeles as a whole. Do not quote it as Hollywood, Central, or any other single division.

Block-level pins are often offset to a reporting area. They are not household identifications. A February cluster on the map is a set of report locations from the public extract.

LocalCrimeVault does not impute missing divisions. Rows without geography still count toward 16,931. Filtering them out of the table will make the visible set smaller than the headline. Council districts are a different system.

On the 2024-02 overlay, LAPD geographic division names are the geography this Los Angeles index supports when LAPD published them. The 16,931 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 16,931 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 16,931. LocalCrimeVault does not fill them. Stay with the division table and the city-wide 16,931 when you cite 2024-02.

Using the 2024-02 overlay

Sort by date, crime-code category, or division. Arrest fields are not convictions. Unfounded or later-reclassified reports can remain until LAPD updates the source row.

Later harvests can move 16,931. Cite it as the current indexed count for Los Angeles report dates in 2024-02, not as a locked annual statistic.

The 2024-02 table is the working surface for these 16,931 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 16,931. Sealed or restricted records that LAPD does not publish never enter 16,931. If a type filter reduces the table, the caption should say the slice is no longer the city-wide 2024-02 headline. LocalCrimeVault does not reclassify charges inside the 16,931 mix.

What sits outside 16,931

911 calls that never became open-data rows, unreported events, and court dispositions are outside the total. Sealed records LAPD does not publish never enter the 16,931.

This page does not compare February to January or March. Those other counts are not in this packet. Keep 16,931 attached to 2024-02.

Los Angeles hub and citation

The February overlay holds the 16,931-row table. The Los Angeles hub is the parent city view for other months, offense types, and division pages. Use the hub when 2024-02 is the wrong filter.

Citation form: 16,931 LAPD incidents with a report date in 2024-02, indexed on LocalCrimeVault from LA Open Data. Counts are reports, not convictions. Report date can differ from date-occurred.

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-02, 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-02 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 16,931 only.

Documenting the 2024-02 harvest for Los Angeles

Los Angeles 2024-02 remains 2024 indexed LAPD incidents with report dates in 2024-02 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-02. 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-02, not a live CAD feed and not a promise that a portal query tomorrow returns the same integer. Record the month label 2024-02 next to 2024 if you republish the figure so a later snapshot is not silently mixed into the same sentence.

Questions

How many Los Angeles incidents are indexed for February 2024?

LocalCrimeVault currently indexes 16,931 LAPD incidents with a report date in 2024-02. The source is LA Open Data. The mix includes published crime-code categories in that window. The figure counts police reports, not convictions. 16,931 is the current indexed total for Los Angeles report dates in 2024-02, drawn from LAPD records on LA Open Data. LocalCrimeVault does not reclassify charges. Later harvests can still move the integer.

Why is the February total different from other months?

This packet does not include other months, so this page does not explain a month-to-month change. The claim here is 16,931 indexed reports with report dates in 2024-02. Later harvests can still move that integer. The packet facts give one month total for Los Angeles in 2024-02. Event-day isolation requires a date filter on the overlay. This page does not invent a subtotal that is not in the facts. Counts remain reports, not convictions.

Is 16,931 limited to one LAPD division?

No. It is city-wide for Los Angeles. Division names appear when LAPD published them. Some rows lack a division. Filter the overlay for a single division; do not treat 16,931 as that division's volume. 16,931 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 February 2024 report mean someone was convicted?

No. Public incident rows are reports. Arrest fields are not court findings. LocalCrimeVault indexes LAPD incidents by report date and does not reclassify charges. The 16,931 count is monthly report volume. Public incident rows for Los Angeles in 2024-02 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 16,931 as a guilty-finding total. Court outcomes live in a different system.