Los Angeles police reports — 2023-03

What 19,014 measures in March

Each of the 19,014 rows is a published police incident whose report date sits in 2023-03. Crime-code categories are mixed. This page will not publish a violent-crime subtotal or a property-crime subtotal because those splits are not in the packet. Filter category labels on the overlay if you need one type.

March sits at the winter-to-spring turn on the civic calendar. St. Patrick's Day, spring break, and awards-season calendars are not packet facts. If those days produced reports, they are inside 19,014 only when the report date is in March. Do not treat 19,014 as a parade-route or red-carpet statistic.

Date-occurred is a separate LAPD column. This harvest does not give a count of March occurrences that were reported later, or of earlier occurrences reported in March. Stay with report date as the membership rule for 19,014.

Los Angeles in 2023-03 is 19,014 indexed LAPD incidents with report dates in 2023-03. St. Patrick's Day and awards-season calendars are not cells. Red-carpet pins, if they appear, are report locations, not a Hollywood subtotal. The 19,014 headline is city-wide. Division filters produce a subset. Informal neighborhood names that never appear as the division field will not match 19,014.

Official division names, city-wide total

When LAPD populated the geographic division field, the overlay shows that name. The 19,014 headline is still Los Angeles as a whole. Adding a handful of divisions will undershoot 19,014 if other rows are blank or filtered out.

Map pins are often offset to a block or reporting area. They are not door-level identifications. A dense March cluster is a set of report locations, not a named-building accusation.

Researchers who need one division should filter the 2023-03 table rather than quoting 19,014 as that division's volume. Informal neighborhood nicknames that never appear as the division field will not match this file.

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

Reading arrest fields and blanks

An arrest field on a March row is still an attribute of a report. It is not a charging decision and not a guilty finding. Blank arrest fields do not prove that an event was minor.

Missing coordinates and missing divisions stay missing. LocalCrimeVault does not fill them. Later LAPD extracts can revise 19,014 up or down as rows are added, corrected, or removed.

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

What this March page is not

It is not a 911 log, not a victimization survey, and not a court docket. Unreported events never enter 19,014. CAD calls that never became open-data rows are outside the total.

Do not compare 19,014 to another month on this page. Other month integers live on their own packets. Mixing them here would invent a comparison this file cannot support.

Where to go after the March table

Stay on the 2023-03 overlay for the 19,014-row table. Step up to the Los Angeles hub for offense-type pages and division pages that are not limited to March. Pair any filtered subset with a caption that says you left the city-wide month headline.

Citation: 19,014 LAPD incidents with a report date in 2023-03, indexed on LocalCrimeVault from LA Open Data. Counts are reports, not convictions.

A durable citation for this page names the agency, the date field, the month, the integer, and the indexer: 2023 LAPD incidents with a report date in 2023-03, 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 2023. Later harvests can move the integer as LAPD adds late-submitted rows or revises old ones. Do not mix this 2023-03 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 19,014 only.

Documenting the 2023-03 harvest for Los Angeles

Los Angeles 2023-03 remains 2023 indexed LAPD incidents with report dates in 2023-03 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 2023-03. Keep the reports-not-convictions clause next to 2023. LocalCrimeVault does not dramatize individual cases and does not turn 2023 into a ranking of neighborhoods, boroughs, or divisions.

Open data lags live dispatch. 2023 is the published extract LocalCrimeVault indexed for 2023-03, not a live CAD feed and not a promise that a portal query tomorrow returns the same integer. Record the month label 2023-03 next to 2023 if you republish the figure so a later snapshot is not silently mixed into the same sentence.

Questions

How many LAPD incidents does LocalCrimeVault index for 2023-03 in Los Angeles?

The current indexed total is 19,014 incidents with a report date in 2023-03. Source: LA Open Data. The mix includes published crime-code categories in that window. The figure is a police-report count, not a conviction count. 19,014 is the current indexed total for Los Angeles report dates in 2023-03, drawn from LAPD records on LA Open Data. LocalCrimeVault does not reclassify charges. Later harvests can still move the integer.

Does 19,014 isolate St. Patrick's Day or awards-season reports?

No. The packet has one month total. Event-day reports, if they exist in the extract, are inside 19,014 when the report date falls in 2023-03. Filter the overlay by date. This page does not publish an event subtotal. The packet facts give one month total for Los Angeles in 2023-03. 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 the March total limited to one LAPD division?

No. 19,014 is city-wide for Los Angeles. Division names appear when LAPD published them. Some rows lack a division. Use the table filter for a single division. Informal neighborhood names are a different geography. 19,014 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.

If a March row has an arrest field, is that a conviction?

No. Arrest fields are attributes of police reports. Court outcomes are a different system. LocalCrimeVault indexes LAPD incidents by report date and does not treat 19,014 as a guilty-finding total. Public incident rows for Los Angeles in 2023-03 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 19,014 as a guilty-finding total. Court outcomes live in a different system.