Tools for the People › Wildfire-code scorecard › DINS guide
Check the DINS file yourself
Download the same public wildfire-inspection file we used, filter it, and compare destroyed and surviving structures by year built — with the caveats attached.
A check-it-yourself guide. Prepared Nov 10, 2026 (America/Los_Angeles). Not an official finding.
California already publishes wildfire damage inspections. You can download the same file we used and repeat the count. This page shows how, then shows our count from the file opened Nov 10, 2026. That count is an example of what the public file contains. It is not a state scorecard, and it is not proof that the wildfire code worked or failed.
The official file
Catalog: https://data.ca.gov/dataset/cal-fire-damage-inspection-dins-data (opened Nov 10, 2026). The page lists a CSV resource last updated Sep 30, 2026; some catalog metadata also shows Oct 8, 2026. We downloaded the official CSV on Nov 10, 2026. It has 132,522 records.
The catalog, in its own words, says the database is used to document structures impacted by wildland fire within the Statewide Responsibility Area (SRA) that are inside or within 300 feet of the fire perimeter; that attributes with null values could not be determined; and that “not all structures impacted by the fire may be identified” because of fire damage and poor access, so “a small margin of error is expected.” It also says qualifying structures are generally 120 square feet or larger, and that parcel fields — including Address (parcel) and APN (parcel) — are added through a spatial join after collection. The CSV header includes a field named Year Built (parcel). That is a parcel join, like those other parcel fields. It is not a Chapter 7A / WUI code-edition field, and it is not filled in by the inspector on site as a code edition.
The public file still includes incident records named Camp, Palisades, and Eaton. We used those names as they appear in the file.
Step by step
- Open the catalog link above and download the CSV.
- Open it in a spreadsheet or a simple script. The useful columns for this check are
* Incident Name,Incident Start Date,* Damage,* Structure Type, andYear Built (parcel). - Filter
* Incident Nameto the exact names in the file: Camp, Palisades, and Eaton. - Look at
* Damage. In the file we opened, the labels are: Destroyed (>50%), No Damage, Affected (>0-10%), Minor (10-25%), Major (25-50%), and Inaccessible. The file does include non-destroyed rows, including “No Damage” and “Affected.” “Destroyed (>50%)” means more than half damaged, as the file labels it. It is not a legal finding. - Split
Year Built (parcel)into groups. A careful split is: a usable year from 1800 through 2026, then “before 2008” versus “2008 and after”; and a separate bucket for blank values, zeros, and other unusable years. Do not treat a year of 0 as a real construction year. - Count, for each fire and each year group, how many rows are labeled Destroyed (>50%) and how many are not. You can also filter
* Structure Typeto residences if you want a homes-like cut — but say what you included, because the file is not “homes only.” - Read the catalog caveats again before you describe the result.
We use calendar year 2008 as a rough split because opened sources in this research series (including IBHS 2025 early insights on the Los Angeles-area fires) state that new construction after July 1, 2008 in the State Responsibility Area, and in very high fire hazard severity zones of the Local Responsibility Area, must comply with Chapter 7A. That still does not make “year built 2008 or later” the same thing as “built to Chapter 7A.” A 2009 house outside those areas may not have been built to Chapter 7A. A 2008 year could be before or after July 1. Year built is a parcel join, not the permit’s code edition.
Our count from the file opened Nov 10, 2026
Method: we read the official CSV with a Python csv pass on Nov 10, 2026 (America/Los_Angeles). We did not change the file. “Usable year” means a Year Built (parcel) value from 1800 through 2026. “Missing / unusable” means a blank or a recorded year of 0. Five Camp rows had a year of 1 or 1543; those are listed separately and are not in the before / after groups. “Destroyed” means only the file’s label “Destroyed (>50%).” “Not marked destroyed” includes No Damage, Affected, Minor, Major, and Inaccessible. Inaccessible is not a confirmed survival; it is simply not labeled destroyed.
Start dates in the file: Camp, Nov 8, 2018 (all 23,624 rows). Eaton, Jan 7, 2025 (all 18,428 rows). Palisades, Jan 7, 2025 for 12,132 rows, plus 2 rows dated Jan 8, 2025 and 3 dated Jan 9, 2025 (12,137 rows in all). We kept those five Palisades rows in the Palisades count because the incident name is Palisades.
All structures in the file (not homes only)
| Incident | Year-built group | Rows | Destroyed (>50%) | Not marked destroyed | Share marked destroyed in this file |
|---|---|---|---|---|---|
| Camp | Before 2008 | 22,201 | 17,944 | 4,257 | 80.8% |
| Camp | 2008 and after | 576 | 291 | 285 | 50.5% |
| Camp | Missing / unusable year | 842 | 564 | 278 | 67.0% |
| Camp | Unusable year (1 or 1543) | 5 | 5 | 0 | — |
| Palisades | Before 2008 | 10,995 | 6,255 | 4,740 | 56.9% |
| Palisades | 2008 and after | 640 | 362 | 278 | 56.6% |
| Palisades | Missing / unusable year | 502 | 228 | 274 | 45.4% |
| Eaton | Before 2008 | 17,854 | 9,238 | 8,616 | 51.7% |
| Eaton | 2008 and after | 89 | 24 | 65 | 27.0% |
| Eaton | Missing / unusable year | 485 | 157 | 328 | 32.4% |
Incident totals in this file: Camp 23,624 rows (18,804 labeled Destroyed (>50%)); Palisades 12,137 (6,845 destroyed); Eaton 18,428 (9,419 destroyed). Palisades plus Eaton destroyed: 16,264.
The 2008-and-after groups are much smaller than the older groups, especially Eaton (89 rows). In Palisades, the share marked destroyed is almost the same in both year groups (56.9% before 2008, 56.6% in 2008 and after). That is why this table is not a verdict on the code.
Residence-like rows only (our type filter, not an official “homes” definition)
For this second table we kept rows whose * Structure Type contains “Residence,” “Mobile Home,” or “Manufactured” (including four rows with the typo “Famliy”). We did not include Utility Misc Structure, commercial buildings, schools, churches, infrastructure, motor homes, or “Mixed Commercial/Residential.” This is our filter, not an official homes list.
| Incident | Year-built group | Rows | Destroyed (>50%) | Not marked destroyed | Share marked destroyed in this file |
|---|---|---|---|---|---|
| Camp | Before 2008 | 16,448 | 13,294 | 3,154 | 80.8% |
| Camp | 2008 and after | 437 | 212 | 225 | 48.5% |
| Camp | Missing / unusable year | 487 | 339 | 148 | 69.6% |
| Camp | Unusable year (1 or 1543) | 5 | 5 | 0 | — |
| Palisades | Before 2008 | 9,142 | 5,125 | 4,017 | 56.1% |
| Palisades | 2008 and after | 581 | 336 | 245 | 57.8% |
| Palisades | Missing / unusable year | 180 | 90 | 90 | 50.0% |
| Eaton | Before 2008 | 11,951 | 6,018 | 5,933 | 50.4% |
| Eaton | 2008 and after | 66 | 16 | 50 | 24.2% |
| Eaton | Missing / unusable year | 181 | 71 | 110 | 39.2% |
Caveats (please read these with the numbers)
- Year built is a parcel join, not the code edition. It is not proof a structure was, or was not, built under Chapter 7A.
- Homes that were not inspected are not in the file. The official catalog says not all impacted structures may be identified.
- ⚠ The fill rate. Statewide, only 89,928 of 132,522 records (67.9%) had a usable Year Built (parcel) value from 1800 through 2026. Another 12,148 were recorded as 0, 30,431 were blank, and 15 had a year before 1800. These three fires had a much higher usable-year rate: Camp 22,777 of 23,624 (96.4%); Palisades 11,635 of 12,137 (95.9%); Eaton 17,943 of 18,428 (97.4%). A high fill rate in one fire is not a fill rate for the whole file.
- The file includes many structure types, not only homes. Utility miscellaneous structures alone were 12,442 of the 54,189 rows in these three incidents.
- These shares describe labels in one public file. They do not, by themselves, measure code effectiveness, and they do not assign motive to any agency or company.
If you want the state to produce its own analysis by code edition, and to say whether it tracks spending against results, use the state letter.
General information, not legal advice. You file in your own name. ⚠ = not verified from a primary page opened for this tool, or a limit of what we opened. Pages and numbers on this tool were prepared Nov 10, 2026 (America/Los_Angeles).