Buildings, repairs and essential services.
GULF CIVICRECORD

Alabama · Florida · Louisiana
Mississippi · Texas

← Latest reporting

New Orleans · Public records

New Orleans records 191 code-enforcement violation entries across 48 cases

Weeds and plant growth lead the entries in a September 1–7 snapshot. The source links violations to cases but does not establish which conditions remain unresolved.

An archival panorama of the New Orleans skyline across the Mississippi River.
New Orleans skyline, 2007. Archival context; this photograph does not identify properties in the analyzed records. Photo: M. Lamar Griffin, Sr. (Louisiana Thunder), Wikimedia Commons, CC BY-SA 3.0. Original image, scaled for display.

New Orleans’ published code-enforcement table contains 191 distinct violation entries linked to 48 cases with violation dates from September 1 through September 7, 2026. Gulf Civic Record counted the entries in an extract collected on September 9 from the city’s Code Enforcement All Violations dataset.

The figures describe the records returned for that date window. They do not represent 191 properties, 48 newly opened cases or a count of conditions that remain unresolved today. A single case can contain several violation entries, and this table has no open-or-closed status field.

What appears most often

The largest group under a single code section was weeds and plant growth, with 39 entries. Rodent harborage accounted for 23, followed by sanitation with 20. These are the city’s recorded violation labels, not findings from independent inspections by this publication.

Five most frequent code sections in the selected extract. A section can include several violation labels.
Code sectionLabels in this extractEntries
26-160(a)Weeds and Plant Growth39
26-161(a)Rodent Harborage23
26-157Sanitation20
26-159Sidewalks (15); Driveways (3)18
26-172Roofs (10); Gutters and Downspouts (8)18

Across all 191 entries, the extract contains 22 distinct code-section strings and 28 combinations of section and violation label. Keeping both fields matters: combining everything under section 26-172, for example, would hide the difference between roof entries and gutter or downspout entries.

Dates do not answer every question

All returned violation dates fall on September 1–4: 50 entries on September 1, 35 on September 2, 50 on September 3 and 56 on September 4. The selected window also included September 5–7, but the extract returned no entries bearing those dates. That does not establish that no inspections, complaints or enforcement work occurred on those days.

The city’s case number and case identifier remain separate from the violation identifier. The table does not supply a case-opening date. A violation date therefore cannot be treated as the date a case first opened.

What the table leaves unanswered

The table supplies case identifiers, a location, a violation date, a code section, a violation label and description text. The descriptions include ordinance wording; they should not be read as a detailed inspector’s account of each location. There is no violation-status field, and the extract alone does not establish repairs, compliance, occupancy, residential use or financial circumstances.

Questions about a particular property would require additional records and a current-status check. This article reports aggregates and does not identify individual properties or owners.

How we checked this snapshot

We selected records whose source ViolationDate was on or after September 1 and before September 8, 2026, retaining the source’s civil date values without assigning a timezone. The requested limit was 500 rows; the city returned all 191 matching rows, with 191 unique violation identifiers and 48 unique case identifiers and case numbers.

Separate JSON and CSV downloads matched field for field. Counts and the dataset revision agreed before and after download. We preserved the originals and checked identifiers, duplicates, required source fields and dates before calculating these aggregates.

The portal’s dataset revision was September 9 at 04:10:37 UTC. Its per-record LastUpload field was absent for every returned entry, so that portal revision is not a per-violation update date. A later download may differ. These source checks establish the basis for this article; they do not certify a property’s current condition.

Primary source: City of New Orleans, Code Enforcement All Violations, dataset 3ehi-je3s. Collected September 9 at 09:00 UTC.

The records operation behind this publication also supports commercial property research. No sale intent or financial-distress finding is drawn from these enforcement entries. For a documented correction, contact the editorial inbox.