| Field | Recorded value | Recorded as unknown | Empty cell | Value present | Split |
|---|---|---|---|---|---|
| Damage Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states DAMAGE | 132,522 | 0 | 0 | 100.0% | |
| Structure type 156 values outside the published domain across 4 distinct spellings STRUCTURETYPE | 132,522 | 0 | 0 | 100.0% | |
| Structure category 7 values outside the published domain across 1 distinct spelling STRUCTURECATEGORY | 132,522 | 0 | 0 | 100.0% | |
| Incident name The layer publishes no coded-value domain for this field, so no value here is counted as outside one INCIDENTNAME | 132,522 | 0 | 0 | 100.0% | |
| Incident number The layer publishes no coded-value domain for this field, so no value here is counted as outside one INCIDENTNUM | 132,522 | 0 | 0 | 100.0% | |
| Incident start date The layer publishes no coded-value domain for this field, so no value here is counted as outside one INCIDENTSTARTDATE | 132,522 | 0 | 0 | 100.0% | |
| Hazard type HAZARDTYPE | 132,522 | 0 | 0 | 100.0% | |
| County The layer publishes no coded-value domain for this field, so no value here is counted as outside one COUNTY | 132,492 | 0 | 30 | 100.0% | |
| CAL FIRE unit The layer publishes no coded-value domain for this field, so no value here is counted as outside one CALFIREUNIT | 132,522 | 0 | 0 | 100.0% | |
| Community markers: - (43), n/a (50), na (640), none (11), unknown (28). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one COMMUNITY | 54,502 | 772 | 77,248 | 41.1% | |
| City markers: n/a (731), na (26,824), none (1), unknown (9). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one CITY | 100,033 | 27,565 | 4,924 | 75.5% | |
| Roof construction markers: unknown (18,535). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states 14,203 values outside the published domain across 5 distinct spellings ROOFCONSTRUCTION | 109,257 | 18,535 | 4,730 | 82.4% | |
| Eaves markers: not applicable (893), unknown (51,471). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md 2 values outside the published domain across 1 distinct spelling EAVES | 74,944 | 52,364 | 5,214 | 56.6% | |
| Vent screen markers: unknown (40,139). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states 5,740 values outside the published domain across 5 distinct spellings VENTSCREEN | 87,081 | 40,139 | 5,302 | 65.7% | |
| Exterior siding markers: unknown (17,540). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states 37,576 values outside the published domain across 4 distinct spellings EXTERIORSIDING | 109,970 | 17,540 | 5,012 | 83.0% | |
| Window pane markers: unknown (33,469). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states 3 values outside the published domain across 3 distinct spellings WINDOWPANE | 93,973 | 33,469 | 5,080 | 70.9% | |
| Deck or porch on grade markers: unknown (15,777). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states 7 values outside the published domain across 1 distinct spelling DECKPORCHONGRADE | 95,153 | 15,777 | 21,592 | 71.8% | |
| Deck or porch elevated markers: unknown (18,750). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states 17 values outside the published domain across 1 distinct spelling DECKPORCHELEVATED | 92,179 | 18,750 | 21,593 | 69.6% | |
| Patio cover or carport markers: unknown (20,235). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states PATIOCOVERCARPORT | 90,689 | 20,235 | 21,598 | 68.4% | |
| Fence attached to structure markers: unknown (15,133). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states FENCEATTACHEDTOSTRUCTURE | 95,795 | 15,133 | 21,594 | 72.3% | |
| Propane tank distance markers: unknown (6,646). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md PROPANETANKDISTANCE | 48,547 | 6,646 | 77,329 | 36.6% | |
| Utility or misc structure distance Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md 6,787 values outside the published domain across 3 distinct spellings UTILITYMISCSTRUCTUREDISTANCE | 37,783 | 0 | 94,739 | 28.5% | |
| Where fire started on structure markers: not applicable (23), unknown (8,716). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md 157 values outside the published domain across 7 distinct spellings WHEREFIRESTARTEDONSTRUCTURE | 3,661 | 8,739 | 120,122 | 2.8% | |
| What the fire started from markers: not applicable (18), unknown (5,810). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md 5 values outside the published domain across 4 distinct spellings WHATDIDFIRESTARTFROM | 4,848 | 5,828 | 121,846 | 3.7% | |
| Defensive actions taken markers: unknown (27,707). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states 691 values outside the published domain across 4 distinct spellings DEFENSIVEACTIONS | 8,462 | 27,707 | 96,353 | 6.4% | |
| Units in structure The layer publishes no coded-value domain for this field, so no value here is counted as outside one NUMBEROFUNITPERSTRUCTURE | 61,929 | 0 | 70,593 | 46.7% | |
| Damaged outbuildings The layer publishes no coded-value domain for this field, so no value here is counted as outside one NOOUTBUILDINGSDAMAGED | 61,939 | 0 | 70,583 | 46.7% | |
| Undamaged outbuildings The layer publishes no coded-value domain for this field, so no value here is counted as outside one NOOUTBUILDINGSNOTDAMAGED | 61,958 | 0 | 70,564 | 46.8% | |
| Damaged or destroyed cars The layer publishes no coded-value domain for this field, so no value here is counted as outside one NOOFCARSONPROPERTY | 56,188 | 0 | 76,334 | 42.4% | |
| APN (parcel) markers: none (42), unknown (1). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one APN | 131,615 | 43 | 864 | 99.3% | |
| Site address (parcel) markers: - (3), no address available (513), none (56), null null unknown ca 00000 (160). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one SITEADDRESS | 124,138 | 732 | 7,652 | 93.7% | |
| Year built (parcel) markers: 0 (12,148). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one YEARBUILT | 89,943 | 12,148 | 30,431 | 67.9% | |
| Assessed improved value (parcel) The layer publishes no coded-value domain for this field, so no value here is counted as outside one ASSESSEDIMPROVEDVALUE | 126,482 | 0 | 6,040 | 95.4% | |
| Street name (field determined) markers: n/a (18), na (1,204), none (12), unknown (295). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one STREETNAME | 126,660 | 1,529 | 4,333 | 95.6% | |
| Street type (field determined) markers: - (7), n/a (1), unk (1). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md 1,516 values outside the published domain across 8 distinct spellings STREETTYPE | 125,808 | 9 | 6,705 | 94.9% | |
| Latitude The layer publishes no coded-value domain for this field, so no value here is counted as outside one LATITUDE | 132,522 | 0 | 0 | 100.0% | |
| Longitude The layer publishes no coded-value domain for this field, so no value here is counted as outside one LONGITUDE | 132,522 | 0 | 0 | 100.0% |
There are three things a field can say about a published coded-value domain, and every row above says exactly one of them. It carries values the domain does not describe, which are counted and named under the field. It has a published domain and holds nothing outside it, and carries no note. Or the layer publishes no domain for that field at all, which the row says in words, because nothing there was compared against anything and a zero would have read as a finding that the file and the domain agree.
+A zero is a judgment call, and this says who made it. 6 of the 8 fields measured as numbers carry a reviewed reading of what a recorded zero means; 2 do not. None of them is: LATITUDE, LONGITUDE, which publish no recorded zero in this retrieval. A zero appearing in any of them stops the build until somebody rules on it. Of the 5 that publish a recorded zero today, 5 carry a reading. Each field's own reading is on its row below, and the evidence is in docs/MARKERS.md section 7.
| Field | Recorded value | Recorded as unknown | Empty cell | Value present | Split |
|---|---|---|---|---|---|
| Damage Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states DAMAGE | 132,522 | 0 | 0 | 100.0% | |
| Structure type 156 values outside the published domain across 4 distinct spellings STRUCTURETYPE | 132,522 | 0 | 0 | 100.0% | |
| Structure category 7 values outside the published domain across 1 distinct spelling STRUCTURECATEGORY | 132,522 | 0 | 0 | 100.0% | |
| Incident name The layer publishes no coded-value domain for this field, so no value here is counted as outside one INCIDENTNAME | 132,522 | 0 | 0 | 100.0% | |
| Incident number The layer publishes no coded-value domain for this field, so no value here is counted as outside one INCIDENTNUM | 132,522 | 0 | 0 | 100.0% | |
| Incident start date The layer publishes no coded-value domain for this field, so no value here is counted as outside one INCIDENTSTARTDATE | 132,522 | 0 | 0 | 100.0% | |
| Hazard type HAZARDTYPE | 132,522 | 0 | 0 | 100.0% | |
| County The layer publishes no coded-value domain for this field, so no value here is counted as outside one COUNTY | 132,492 | 0 | 30 | 100.0% | |
| CAL FIRE unit The layer publishes no coded-value domain for this field, so no value here is counted as outside one CALFIREUNIT | 132,522 | 0 | 0 | 100.0% | |
| Community markers: - (43), n/a (50), na (640), none (11), unknown (28). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one COMMUNITY | 54,502 | 772 | 77,248 | 41.1% | |
| City markers: n/a (731), na (26,824), none (1), unknown (9). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one CITY | 100,033 | 27,565 | 4,924 | 75.5% | |
| Roof construction markers: unknown (18,535). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states 14,203 values outside the published domain across 5 distinct spellings ROOFCONSTRUCTION | 109,257 | 18,535 | 4,730 | 82.4% | |
| Eaves markers: not applicable (893), unknown (51,471). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md 2 values outside the published domain across 1 distinct spelling EAVES | 74,944 | 52,364 | 5,214 | 56.6% | |
| Vent screen markers: unknown (40,139). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states 5,740 values outside the published domain across 5 distinct spellings VENTSCREEN | 87,081 | 40,139 | 5,302 | 65.7% | |
| Exterior siding markers: unknown (17,540). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states 37,576 values outside the published domain across 4 distinct spellings EXTERIORSIDING | 109,970 | 17,540 | 5,012 | 83.0% | |
| Window pane markers: unknown (33,469). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states 3 values outside the published domain across 3 distinct spellings WINDOWPANE | 93,973 | 33,469 | 5,080 | 70.9% | |
| Deck or porch on grade markers: unknown (15,777). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states 7 values outside the published domain across 1 distinct spelling DECKPORCHONGRADE | 95,153 | 15,777 | 21,592 | 71.8% | |
| Deck or porch elevated markers: unknown (18,750). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states 17 values outside the published domain across 1 distinct spelling DECKPORCHELEVATED | 92,179 | 18,750 | 21,593 | 69.6% | |
| Patio cover or carport markers: unknown (20,235). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states PATIOCOVERCARPORT | 90,689 | 20,235 | 21,598 | 68.4% | |
| Fence attached to structure markers: unknown (15,133). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states FENCEATTACHEDTOSTRUCTURE | 95,795 | 15,133 | 21,594 | 72.3% | |
| Propane tank distance markers: unknown (6,646). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md PROPANETANKDISTANCE | 48,547 | 6,646 | 77,329 | 36.6% | |
| Utility or misc structure distance Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md 6,787 values outside the published domain across 3 distinct spellings UTILITYMISCSTRUCTUREDISTANCE | 37,783 | 0 | 94,739 | 28.5% | |
| Where fire started on structure markers: not applicable (23), unknown (8,716). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md 157 values outside the published domain across 7 distinct spellings WHEREFIRESTARTEDONSTRUCTURE | 3,661 | 8,739 | 120,122 | 2.8% | |
| What the fire started from markers: not applicable (18), unknown (5,810). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md 5 values outside the published domain across 4 distinct spellings WHATDIDFIRESTARTFROM | 4,848 | 5,828 | 121,846 | 3.7% | |
| Defensive actions taken markers: unknown (27,707). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states 691 values outside the published domain across 4 distinct spellings DEFENSIVEACTIONS | 8,462 | 27,707 | 96,353 | 6.4% | |
| Units in structure 58,411 recorded zeros; reviewed, and undecidable from the published documentation: both readings are live and the file cannot separate them, so the zeros are left as recorded values. Do not read a zero here as a finding, and do not read it as an absence The layer publishes no coded-value domain for this field, so no value here is counted as outside one NUMBEROFUNITPERSTRUCTURE | 61,929 | 0 | 70,593 | 46.7% | |
| Damaged outbuildings 59,628 recorded zeros; reviewed: a zero here is a measurement. An inspector writing 0 observed none, and the zeros stay counted as recorded values The layer publishes no coded-value domain for this field, so no value here is counted as outside one NOOUTBUILDINGSDAMAGED | 61,939 | 0 | 70,583 | 46.7% | |
| Undamaged outbuildings 58,888 recorded zeros; reviewed: a zero here is a measurement. An inspector writing 0 observed none, and the zeros stay counted as recorded values The layer publishes no coded-value domain for this field, so no value here is counted as outside one NOOUTBUILDINGSNOTDAMAGED | 61,958 | 0 | 70,564 | 46.8% | |
| Damaged or destroyed cars 55,831 recorded zeros; reviewed: a zero here is a measurement. An inspector writing 0 observed none, and the zeros stay counted as recorded values The layer publishes no coded-value domain for this field, so no value here is counted as outside one NOOFCARSONPROPERTY | 56,188 | 0 | 76,334 | 42.4% | |
| APN (parcel) markers: none (42), unknown (1). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one APN | 131,615 | 43 | 864 | 99.3% | |
| Site address (parcel) markers: - (3), no address available (513), none (56), null null unknown ca 00000 (160). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one SITEADDRESS | 124,138 | 732 | 7,652 | 93.7% | |
| Year built (parcel) markers: 0 (12,148). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md 0 recorded zeros; reviewed and declared a marker: the zeros are counted as recorded-as-unknown above, not as values, so this field publishes none The layer publishes no coded-value domain for this field, so no value here is counted as outside one YEARBUILT | 89,943 | 12,148 | 30,431 | 67.9% | |
| Assessed improved value (parcel) 6,613 recorded zeros; reviewed, and undecidable from the published documentation: both readings are live and the file cannot separate them, so the zeros are left as recorded values. Do not read a zero here as a finding, and do not read it as an absence The layer publishes no coded-value domain for this field, so no value here is counted as outside one ASSESSEDIMPROVEDVALUE | 126,482 | 0 | 6,040 | 95.4% | |
| Street name (field determined) markers: n/a (18), na (1,204), none (12), unknown (295). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one STREETNAME | 126,660 | 1,529 | 4,333 | 95.6% | |
| Street type (field determined) markers: - (7), n/a (1), unk (1). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md 1,516 values outside the published domain across 8 distinct spellings STREETTYPE | 125,808 | 9 | 6,705 | 94.9% | |
| Latitude 0 recorded zeros; NOT REVIEWED. Nobody has read the inspection form for this field, so a zero here is published as a recorded value and may be an absence The layer publishes no coded-value domain for this field, so no value here is counted as outside one LATITUDE | 132,522 | 0 | 0 | 100.0% | |
| Longitude 0 recorded zeros; NOT REVIEWED. Nobody has read the inspection form for this field, so a zero here is published as a recorded value and may be an absence The layer publishes no coded-value domain for this field, so no value here is counted as outside one LONGITUDE | 132,522 | 0 | 0 | 100.0% |
There are three things a field can say about a published coded-value domain, and every row above says exactly one of them. It carries values the domain does not describe, which are counted and named under the field. It has a published domain and holds nothing outside it, and carries no note. Or the layer publishes no domain for that field at all, which the row says in words, because nothing there was compared against anything and a zero would have read as a finding that the file and the domain agree.
Each field carries the basis its markers rest on. A published basis means the value appears in the layer's own coded-value domain, which anyone can re-read at the endpoint listed under Provenance below. An inferred basis means diff --git a/site/perimeters.html b/site/perimeters.html index 23aa401..bcd5379 100644 --- a/site/perimeters.html +++ b/site/perimeters.html @@ -197,7 +197,8 @@
| Field | Recorded value | Recorded as unknown | Empty cell | Value present | Split |
|---|---|---|---|---|---|
| Year The layer publishes no coded-value domain for this field, so no value here is counted as outside one YEAR_ | 23,257 | 0 | 77 | 99.7% | |
| IRWIN ID The layer publishes no coded-value domain for this field, so no value here is counted as outside one IRWINID | 3,633 | 0 | 19,701 | 15.6% | |
| Alarm date The layer publishes no coded-value domain for this field, so no value here is counted as outside one ALARM_DATE | 17,950 | 0 | 5,384 | 76.9% | |
| Containment date The layer publishes no coded-value domain for this field, so no value here is counted as outside one CONT_DATE | 10,716 | 0 | 12,618 | 45.9% | |
| Fire name markers: n/a (72), none (1), unknown (12). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one FIRE_NAME | 16,666 | 85 | 6,583 | 71.4% | |
| Local incident number markers: 00000000 (12,469). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one INC_NUM | 9,910 | 12,469 | 955 | 42.5% | |
| Fire number (historical use) markers: 00000000 (3,620), <null> (3). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one FIRE_NUM | 13,521 | 3,623 | 6,190 | 57.9% | |
| Cause markers: 14 (10,514). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states CAUSE | 12,820 | 10,514 | 0 | 54.9% | |
| Collection method markers: 8 (15,081). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states C_METHOD | 8,253 | 15,081 | 0 | 35.4% | |
| Management objective OBJECTIVE | 23,063 | 0 | 271 | 98.8% | |
| Reporting agency AGENCY | 23,286 | 0 | 48 | 99.8% | |
| Unit The layer publishes no coded-value domain for this field, so no value here is counted as outside one UNIT_ID | 23,274 | 0 | 60 | 99.7% | |
| State STATE | 23,334 | 0 | 0 | 100.0% | |
| GIS calculated acres The layer publishes no coded-value domain for this field, so no value here is counted as outside one GIS_ACRES | 23,334 | 0 | 0 | 100.0% | |
| Complex name The layer publishes no coded-value domain for this field, so no value here is counted as outside one COMPLEX_NAME | 618 | 0 | 22,716 | 2.6% | |
| Complex ID markers: 00000000 (1). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one COMPLEX_ID | 583 | 1 | 22,750 | 2.5% | |
| Decade The layer publishes no coded-value domain for this field, so no value here is counted as outside one DECADES | 18,064 | 0 | 5,270 | 77.4% |
There are three things a field can say about a published coded-value domain, and every row above says exactly one of them. It carries values the domain does not describe, which are counted and named under the field. It has a published domain and holds nothing outside it, and carries no note. Or the layer publishes no domain for that field at all, which the row says in words, because nothing there was compared against anything and a zero would have read as a finding that the file and the domain agree.
+A zero is a judgment call, and this says who made it. 0 of the 1 fields measured as numbers carry a reviewed reading of what a recorded zero means; 1 do not. None of them is: GIS_ACRES, which publish no recorded zero in this retrieval. A zero appearing in any of them stops the build until somebody rules on it. Of the 0 that publish a recorded zero today, 0 carry a reading. Each field's own reading is on its row below, and the evidence is in docs/MARKERS.md section 7.
| Field | Recorded value | Recorded as unknown | Empty cell | Value present | Split |
|---|---|---|---|---|---|
| Year The layer publishes no coded-value domain for this field, so no value here is counted as outside one YEAR_ | 23,257 | 0 | 77 | 99.7% | |
| IRWIN ID The layer publishes no coded-value domain for this field, so no value here is counted as outside one IRWINID | 3,633 | 0 | 19,701 | 15.6% | |
| Alarm date The layer publishes no coded-value domain for this field, so no value here is counted as outside one ALARM_DATE | 17,950 | 0 | 5,384 | 76.9% | |
| Containment date The layer publishes no coded-value domain for this field, so no value here is counted as outside one CONT_DATE | 10,716 | 0 | 12,618 | 45.9% | |
| Fire name markers: n/a (72), none (1), unknown (12). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one FIRE_NAME | 16,666 | 85 | 6,583 | 71.4% | |
| Local incident number markers: 00000000 (12,469). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one INC_NUM | 9,910 | 12,469 | 955 | 42.5% | |
| Fire number (historical use) markers: 00000000 (3,620), <null> (3). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one FIRE_NUM | 13,521 | 3,623 | 6,190 | 57.9% | |
| Cause markers: 14 (10,514). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states CAUSE | 12,820 | 10,514 | 0 | 54.9% | |
| Collection method markers: 8 (15,081). Basis: published. Every value this field declares is a code in the layer's own coded-value domain, or a value the publisher's documentation states C_METHOD | 8,253 | 15,081 | 0 | 35.4% | |
| Management objective OBJECTIVE | 23,063 | 0 | 271 | 98.8% | |
| Reporting agency AGENCY | 23,286 | 0 | 48 | 99.8% | |
| Unit The layer publishes no coded-value domain for this field, so no value here is counted as outside one UNIT_ID | 23,274 | 0 | 60 | 99.7% | |
| State STATE | 23,334 | 0 | 0 | 100.0% | |
| GIS calculated acres 0 recorded zeros; NOT REVIEWED. Nobody has read the inspection form for this field, so a zero here is published as a recorded value and may be an absence The layer publishes no coded-value domain for this field, so no value here is counted as outside one GIS_ACRES | 23,334 | 0 | 0 | 100.0% | |
| Complex name The layer publishes no coded-value domain for this field, so no value here is counted as outside one COMPLEX_NAME | 618 | 0 | 22,716 | 2.6% | |
| Complex ID markers: 00000000 (1). Basis: inferred. At least one value this field declares is documented nowhere, and was read off the acquired file by this project. See docs/MARKERS.md The layer publishes no coded-value domain for this field, so no value here is counted as outside one COMPLEX_ID | 583 | 1 | 22,750 | 2.5% | |
| Decade The layer publishes no coded-value domain for this field, so no value here is counted as outside one DECADES | 18,064 | 0 | 5,270 | 77.4% |
There are three things a field can say about a published coded-value domain, and every row above says exactly one of them. It carries values the domain does not describe, which are counted and named under the field. It has a published domain and holds nothing outside it, and carries no note. Or the layer publishes no domain for that field at all, which the row says in words, because nothing there was compared against anything and a zero would have read as a finding that the file and the domain agree.
Markers listed under a field name are the exact text this project
reviewed for that field before counting it as a marker rather than as a value. A field
number of all zeros, for instance, is counted apart from recorded numbers, because reading
diff --git a/src/perimeter/artifacts.py b/src/perimeter/artifacts.py
index 17765db..ffacbaf 100644
--- a/src/perimeter/artifacts.py
+++ b/src/perimeter/artifacts.py
@@ -22,8 +22,10 @@
DinsReport,
FieldCoverage,
PerimeterReport,
+ ZeroReview,
dins_report,
perimeter_report,
+ zero_review,
)
from perimeter.dins import NOT_APPLICABLE_FIELD, AccessSplit, load_inspections
from perimeter.perimeters import (
@@ -36,7 +38,7 @@
FIELD_STATE_ORDER = ("present", "explicit_unknown", "not_recorded")
"""The order of the three counts in every compact per-incident field triple."""
-ARTIFACT_SCHEMA_VERSION = 1
+ARTIFACT_SCHEMA_VERSION = 2
"""The version of the published artifact contract, carried in every artifact.
Bump it when a consumer validating against the previous schema in ``site/data/schema/``
@@ -118,11 +120,30 @@ def _field_json(field: FieldCoverage) -> dict[str, Any]:
}
if field.zero_values is not None:
payload["recorded_zero_values"] = field.zero_values
+ if field.zero_reading is not None:
+ # Published beside the count and never instead of it. The count says how many
+ # zeros there are; this says whether anybody has ruled on what one MEANS, which
+ # `marker_basis: "none"` could not distinguish from "reviewed and left as a
+ # measurement" (issue #83).
+ payload["recorded_zero_reading"] = field.zero_reading.value
if field.note:
payload["note"] = field.note
return payload
+def _zero_review_json(review: ZeroReview) -> dict[str, Any]:
+ """The two numbers, and the unreviewed set named rather than counted away."""
+ return {
+ "fields_measured_as_numbers": review.examinable,
+ "fields_with_a_reviewed_zero_reading": review.reviewed,
+ "fields_without_one": list(review.unreviewed_fields),
+ "fields_publishing_a_recorded_zero": review.publishing_zeros,
+ "fields_publishing_a_recorded_zero_with_a_reviewed_reading": (
+ review.publishing_zeros_reviewed
+ ),
+ }
+
+
def _signal_json(signal: DuplicateSignal) -> dict[str, Any]:
return {
"key": signal.key,
@@ -185,6 +206,7 @@ def perimeters_payload(report: PerimeterReport, *, is_fixture: bool) -> dict[str
"records_without_year": report.records_without_year,
"irwin_id_present": report.irwin_present,
"fields": [_field_json(field) for field in report.fields],
+ "recorded_zero_review": _zero_review_json(zero_review(report.fields)),
"irwin_id_present_tenths_pct": present_tenths_of_percent(
report.irwin_present, report.records
),
@@ -241,6 +263,7 @@ def dins_payload(report: DinsReport, *, is_fixture: bool) -> dict[str, Any]:
for value, count in report.damage.items()
},
"fields": [_field_json(field) for field in report.fields],
+ "recorded_zero_review": _zero_review_json(zero_review(report.fields)),
"field_state_order": list(FIELD_STATE_ORDER),
# Three cuts of the same records. Each is a partition of the file, so summing a
# cut per field and per state returns the file totals; nothing is estimated and
diff --git a/src/perimeter/coverage.py b/src/perimeter/coverage.py
index c6d8120..7a77fef 100644
--- a/src/perimeter/coverage.py
+++ b/src/perimeter/coverage.py
@@ -38,7 +38,7 @@
year_cohorts,
)
from perimeter.records import Record
-from perimeter.schema import DINS_FIELDS, FRAP_FIELDS, Basis, FieldSpec
+from perimeter.schema import DINS_FIELDS, FRAP_FIELDS, Basis, FieldSpec, ZeroReading
OUTSIDE_DOMAIN_VALUE_CAP = 12
"""How many out-of-domain values to name per field.
@@ -75,6 +75,15 @@ class FieldCoverage:
outside_domain_values: dict[str, int] | None
outside_domain_values_listed: int | None
zero_values: int | None
+ zero_reading: ZeroReading | None
+ """What a recorded ``0`` in this field means, as a reviewer has ruled (ADR-0006,
+ issue #83), or ``None`` for a field that is not measured as a number.
+
+ ``None`` together with ``zero_values`` for the same reason the four out-of-domain
+ measures are ``None`` together: a field with no zeros to rule on was never ruled on,
+ and publishing ``unreviewed`` for it would put every free-text column into the
+ denominator of a review that does not apply to it.
+ """
@property
def total(self) -> int:
@@ -132,6 +141,73 @@ def field_coverage(records: Sequence[Record], spec: FieldSpec) -> FieldCoverage:
outside_domain_values=listed if has_domain else None,
outside_domain_values_listed=len(listed) if has_domain else None,
zero_values=zeros if spec.numeric else None,
+ zero_reading=spec.zero_reading if spec.numeric else None,
+ )
+
+
+@dataclass(frozen=True)
+class ZeroReview:
+ """How much of the zero question has been answered, and how much has not.
+
+ Two numbers, always, because one of them alone is the defect. "Five fields publish
+ recorded zeros and all five are reviewed" is a reassuring sentence that says nothing
+ about the fields measured as numbers that hold no zeros *today* -- and a zero arriving
+ in one of those tomorrow is exactly the case that used to be published as a
+ measurement nobody had ruled on. So: ``reviewed`` of ``examinable``, and the
+ unreviewed set named rather than counted away.
+ """
+
+ examinable: int
+ """Fields measured as numbers. Every one of them can have a zero, so every one of
+ them is a question this project either has or has not answered."""
+
+ reviewed: int
+ """Of those, how many carry a reading somebody made. See
+ :attr:`FieldSpec.zeros_are_reviewed`."""
+
+ unreviewed_fields: tuple[str, ...]
+ """The names of the rest, in registry order. Named rather than counted, because the
+ count alone cannot be acted on and this list is the work item."""
+
+ publishing_zeros: int
+ """Of the examinable fields, how many actually publish a recorded zero today."""
+
+ publishing_zeros_reviewed: int
+ """Of those, how many carry a reading. A build where this is smaller than
+ ``publishing_zeros`` is publishing a zero nobody has ruled on, and
+ ``tests/test_schema.py`` fails it."""
+
+ @property
+ def unreviewed(self) -> int:
+ return len(self.unreviewed_fields)
+
+
+def zero_review(fields: Sequence[FieldCoverage]) -> ZeroReview:
+ """Count the zero question over one artifact's fields, from the fields themselves.
+
+ Derived here rather than stated anywhere, so the pages and the artifact cannot carry a
+ figure that has fallen behind the registry. Every number a page prints about this
+ comes from this function via the artifact.
+ """
+ numeric = [field for field in fields if field.zero_reading is not None]
+ reviewed = [
+ field for field in numeric if field.zero_reading is not ZeroReading.UNREVIEWED
+ ]
+ with_zeros = [field for field in numeric if field.zero_values]
+ return ZeroReview(
+ examinable=len(numeric),
+ reviewed=len(reviewed),
+ unreviewed_fields=tuple(
+ field.name
+ for field in numeric
+ if field.zero_reading is ZeroReading.UNREVIEWED
+ ),
+ publishing_zeros=len(with_zeros),
+ publishing_zeros_reviewed=sum(
+ 1
+ for field in with_zeros
+ if field.zero_reading is not ZeroReading.UNREVIEWED
+ ),
)
diff --git a/src/perimeter/render.py b/src/perimeter/render.py
index 3675a44..d5431f3 100644
--- a/src/perimeter/render.py
+++ b/src/perimeter/render.py
@@ -26,8 +26,9 @@
FieldCoverage,
PerimeterReport,
SpellingCohort,
+ zero_review,
)
-from perimeter.schema import Basis
+from perimeter.schema import Basis, ZeroReading
from perimeter.sources import DINS, FRAP, Source
# Where these pages are served. The path segment is load-bearing: this is one of six project
@@ -64,6 +65,31 @@
"state agency."
)
+ZERO_READING_NOTE: dict[ZeroReading, str] = {
+ ZeroReading.MEASUREMENT: (
+ "reviewed: a zero here is a measurement. An inspector writing 0 observed none, "
+ "and the zeros stay counted as recorded values"
+ ),
+ ZeroReading.UNDECIDABLE: (
+ "reviewed, and undecidable from the published documentation: both readings are "
+ "live and the file cannot separate them, so the zeros are left as recorded "
+ "values. Do not read a zero here as a finding, and do not read it as an absence"
+ ),
+ ZeroReading.MARKER: (
+ "reviewed and declared a marker: the zeros are counted as recorded-as-unknown "
+ "above, not as values, so this field publishes none"
+ ),
+ ZeroReading.UNREVIEWED: (
+ "NOT REVIEWED. Nobody has read the inspection form for this field, so a zero "
+ "here is published as a recorded value and may be an absence"
+ ),
+}
+"""What a recorded zero in a field means, for a reader. See docs/MARKERS.md section 7.
+
+`UNREVIEWED` carries a sentence like the other three rather than rendering nothing,
+because rendering nothing is precisely what made an unexamined field and a reviewed one
+look identical on this page (issue #83)."""
+
BASIS_NOTE: dict[Basis, str] = {
Basis.PUBLISHED: (
"published. Every value this field declares is a code in the layer's own "
@@ -454,6 +480,40 @@ def scroll_region(caption_id: str, *, tall: bool = False) -> str:
return f' A zero is a judgment call, and this says who made '
+ f"it. {num(review.reviewed)} of the {num(review.examinable)} fields "
+ f"measured as numbers carry a reviewed reading of what a recorded zero means; "
+ f"{num(review.unreviewed)} do not.{named} Of the "
+ f"{num(review.publishing_zeros)} that publish a recorded zero today, "
+ f"{num(review.publishing_zeros_reviewed)} carry a reading. Each field's own "
+ f"reading is on its row below, and the evidence is in "
+ f"{esc(name)}" for name in review.unreviewed_fields)
+ + ", which publish no recorded zero in this retrieval. A zero appearing in any of "
+ "them stops the build until somebody rules on it."
+ if review.unreviewed_fields
+ else " There is none left unreviewed."
+ )
+ return (
+ f'docs/MARKERS.md section 7."
- f' {esc(field.label)}{marker_note}{outside}'
+ f' {esc(field.label)}{marker_note}{zeros}{outside}'
f' '
f'{num(field.present)} '
f'{num(field.explicit_unknown)} '
@@ -701,6 +773,7 @@ def perimeters_page(report: PerimeterReport, *, is_fixture: bool) -> str:
and a large share of them carry the published code for
Unknown / Unidentified. Collection method behaves the same way, which is what
FRAP's release note about editing null collection methods to Unknown describes.
+{zero_review_note(report.fields)}
{
field_table(
report.fields,
@@ -1082,6 +1155,7 @@ def dins_page(report: DinsReport, *, is_fixture: bool) -> str:
missing data. A recorded unknown is a published code or a marker word standing where a
value would go. An empty cell is what CAL FIRE describes as an attribute that could not be
determined.
+{zero_review_note(report.fields)}
{
field_table(
report.fields,
diff --git a/src/perimeter/schema.py b/src/perimeter/schema.py
index e3bd6ca..d1cc44b 100644
--- a/src/perimeter/schema.py
+++ b/src/perimeter/schema.py
@@ -67,6 +67,67 @@ class Basis(Enum):
"""At least one declared value was read off the acquired file's own distribution."""
+class ZeroReading(Enum):
+ """What a recorded ``0`` in a field measured as a number means — or that nobody has said.
+
+ ADR-0006: a zero is a judgment call of exactly the same kind as a marker word. Until
+ this existed the code could not tell the two ends of that call apart. A field whose
+ zeros a reviewer had read the inspection form for and left as measurements, and a
+ field nobody had ever looked at, both carried :attr:`Basis.NONE` and published
+ ``marker_basis: "none"``, which is the defect this project is about committed by the
+ registry that describes it: *a zero nobody has ruled on, published as a measurement.*
+ ``docs/MARKERS.md`` section 7 said so in its own last sentence — "the gate that reads
+ this file has no way to tell a reviewed decision from an unexamined one."
+
+ Deliberately a second axis rather than more :class:`Basis` members. ``Basis`` answers
+ *where a declared vocabulary came from*; this answers *what a zero is*, and a field can
+ have any combination of the two. Folding them would be the same conflation one column
+ over.
+
+ The default is :attr:`UNREVIEWED` and it must stay the default: a field added tomorrow
+ has not been reviewed, and the honest state is the one a reader is warned about rather
+ than the one they are reassured by.
+ """
+
+ UNREVIEWED = "unreviewed"
+ """Nobody has ruled on this field's zeros.
+
+ A recorded ``0`` is published as a recorded value **and may be an absence**. A reader
+ must not take it as a measurement. `tests/test_schema.py` fails the build if a field in
+ this state ever publishes a recorded zero, so the state is a promise that there are
+ none rather than a shrug about the ones there are.
+ """
+
+ MEASUREMENT = "measurement"
+ """Reviewed: a recorded ``0`` here is a finding.
+
+ An inspector writing ``0`` damaged outbuildings observed no damaged outbuildings. The
+ zero is a value, it stays counted as present, and ``docs/MARKERS.md`` section 7 carries
+ the reading and the distribution it rests on.
+ """
+
+ UNDECIDABLE = "undecidable"
+ """Reviewed, and the published documentation does not settle it.
+
+ Both readings are live and the file cannot separate them, so the zero is **left
+ present** — declaring it a marker would move tens of thousands of records on a reading
+ nothing supports. A reader must not treat a ``0`` here as a measurement **or** as an
+ absence; ``recorded_zero_values`` is published so either reading can be applied, and
+ section 7 records what would settle it.
+
+ This is the third answer issue #83 asks for by name: "undecidable from the published
+ documentation, which is itself a finding worth a note."
+ """
+
+ MARKER = "marker"
+ """Reviewed and declared: ``0`` is this field's marker for a value that was not recorded.
+
+ The zeros leave ``recorded_zero_values`` and are counted as recorded-as-unknown, so the
+ zero gate stops applying to the field exactly as ADR-0006 says. ``YEARBUILT`` is the
+ one instance: no structure standing in a California wildfire was built in year 0.
+ """
+
+
@dataclass(frozen=True)
class FieldSpec:
"""One measured column and the vocabulary this project has reviewed for it."""
@@ -115,8 +176,30 @@ class FieldSpec:
on the page, because the weakest declaration sets what a reader can rely on.
"""
+ zero_reading: ZeroReading = ZeroReading.UNREVIEWED
+ """What a recorded ``0`` in this field means, as a reviewer has ruled. See
+ :class:`ZeroReading`.
+
+ Meaningful only where ``numeric`` is true; a field that is not measured as a number has
+ no zeros to rule on and must leave this at :attr:`ZeroReading.UNREVIEWED`. Held to
+ ``docs/MARKERS.md`` section 7 in both directions by ``tests/test_schema.py``, so the
+ reading in the registry and the reading in the audit cannot drift apart.
+ """
+
note: str = ""
+ @property
+ def zeros_are_reviewed(self) -> bool:
+ """True when somebody has ruled on what a ``0`` in this field means.
+
+ The two-number denominator's numerator. Deliberately phrased as "somebody has
+ ruled" and not "the zeros are values": :attr:`ZeroReading.UNDECIDABLE` is a review
+ that reached no verdict, and a review that reached no verdict is still a review --
+ it is the state issue #83 asks for, and collapsing it into either neighbour would
+ lose the finding.
+ """
+ return self.numeric and self.zero_reading is not ZeroReading.UNREVIEWED
+
@property
def declares_vocabulary(self) -> bool:
"""True when this field makes any judgment call that needs a basis."""
@@ -759,10 +842,30 @@ def require_columns(
}
),
),
- FieldSpec("NUMBEROFUNITPERSTRUCTURE", "Units in structure", numeric=True),
- FieldSpec("NOOUTBUILDINGSDAMAGED", "Damaged outbuildings", numeric=True),
- FieldSpec("NOOUTBUILDINGSNOTDAMAGED", "Undamaged outbuildings", numeric=True),
- FieldSpec("NOOFCARSONPROPERTY", "Damaged or destroyed cars", numeric=True),
+ FieldSpec(
+ "NUMBEROFUNITPERSTRUCTURE",
+ "Units in structure",
+ numeric=True,
+ zero_reading=ZeroReading.UNDECIDABLE,
+ ),
+ FieldSpec(
+ "NOOUTBUILDINGSDAMAGED",
+ "Damaged outbuildings",
+ numeric=True,
+ zero_reading=ZeroReading.MEASUREMENT,
+ ),
+ FieldSpec(
+ "NOOUTBUILDINGSNOTDAMAGED",
+ "Undamaged outbuildings",
+ numeric=True,
+ zero_reading=ZeroReading.MEASUREMENT,
+ ),
+ FieldSpec(
+ "NOOFCARSONPROPERTY",
+ "Damaged or destroyed cars",
+ numeric=True,
+ zero_reading=ZeroReading.MEASUREMENT,
+ ),
FieldSpec(
"APN",
"APN (parcel)",
@@ -793,6 +896,7 @@ def require_columns(
unknown_markers=frozenset({"0"}),
basis=Basis.INFERRED,
numeric=True,
+ zero_reading=ZeroReading.MARKER,
note="Added by the same post-collection spatial join as APN and SITEADDRESS. "
"12,148 records hold the literal 0. No structure standing in a California "
"wildfire was built in year 0, so a 0 here is the parcel record carrying no "
@@ -802,7 +906,10 @@ def require_columns(
"docs/MARKERS.md holds the distribution it rests on.",
),
FieldSpec(
- "ASSESSEDIMPROVEDVALUE", "Assessed improved value (parcel)", numeric=True
+ "ASSESSEDIMPROVEDVALUE",
+ "Assessed improved value (parcel)",
+ numeric=True,
+ zero_reading=ZeroReading.UNDECIDABLE,
),
FieldSpec(
"STREETNAME",
diff --git a/src/perimeter/schema_export.py b/src/perimeter/schema_export.py
index f26a5c1..67ebaa9 100644
--- a/src/perimeter/schema_export.py
+++ b/src/perimeter/schema_export.py
@@ -45,6 +45,7 @@
from typing import Any
from perimeter.artifacts import ARTIFACT_SCHEMA_VERSION, FIELD_STATE_ORDER
+from perimeter.schema import ZeroReading
from perimeter.sources import DINS, FRAP, Source
SCHEMA_DIALECT = "https://json-schema.org/draft/2020-12/schema"
@@ -241,13 +242,29 @@ def _field_schema() -> dict[str, Any]:
"than folded into either presence or absence. Absent for a field that is "
"not numeric."
),
+ "recorded_zero_reading": {
+ "type": "string",
+ "enum": [reading.value for reading in ZeroReading],
+ "description": (
+ "What a recorded zero in this field MEANS, as a reviewer has ruled. "
+ "`measurement`: a zero is a finding. `undecidable`: reviewed, and the "
+ "published documentation does not settle it, so the zero is left "
+ "present and must not be read as a finding OR as an absence. "
+ "`marker`: declared as a marker, so this field's zeros are counted in "
+ "`explicit_unknown` and `recorded_zero_values` is 0. `unreviewed`: "
+ "NOBODY HAS RULED -- a zero here may be an absence, and the build "
+ "fails if such a field ever publishes one. Read beside "
+ "`recorded_zero_values`, never instead of it, and see "
+ "docs/MARKERS.md section 7. Absent for a field that is not numeric."
+ ),
+ },
"note": _string(
"The field registry's note on this field. Absent where the registry "
"carries none."
),
},
)
- optional = {"recorded_zero_values", "note"}
+ optional = {"recorded_zero_values", "recorded_zero_reading", "note"}
schema["required"] = sorted(set(schema["required"]) - optional)
return schema
@@ -287,6 +304,48 @@ def _access_schema() -> dict[str, Any]:
)
+def _zero_review_schema() -> dict[str, Any]:
+ """How much of the zero question has been answered, and how much has not.
+
+ Two numbers on purpose (issue #83). "Every field publishing a zero has been reviewed"
+ is a true and reassuring sentence that says nothing about the fields measured as
+ numbers holding no zero *today* -- and a zero arriving in one of those is exactly the
+ case that used to be published as a measurement nobody had ruled on.
+ """
+ return _object(
+ "Coverage of the zero question over this artifact's fields. Every figure is "
+ "derived from the fields beside it; none is stated anywhere.",
+ {
+ "fields_measured_as_numbers": _integer(
+ "The denominator: every field that can carry a zero, and so every field "
+ "this project either has or has not ruled on."
+ ),
+ "fields_with_a_reviewed_zero_reading": _integer(
+ "Of those, how many carry a `recorded_zero_reading` other than "
+ "`unreviewed`. `undecidable` counts as reviewed: a review that reached no "
+ "verdict is still a review, and it is a finding rather than a gap."
+ ),
+ "fields_without_one": {
+ "type": "array",
+ "items": {"type": "string"},
+ "description": (
+ "The rest, named rather than counted away. A zero appearing in any of "
+ "these fails the build until somebody rules on it."
+ ),
+ },
+ "fields_publishing_a_recorded_zero": _integer(
+ "Of the fields measured as numbers, how many actually carry a zero in "
+ "this retrieval."
+ ),
+ "fields_publishing_a_recorded_zero_with_a_reviewed_reading": _integer(
+ "Of those, how many carry a reading. Smaller than the figure above means "
+ "a zero nobody has ruled on is being published as a value, which is the "
+ "condition `tests/test_schema.py` fails the build on."
+ ),
+ },
+ )
+
+
def _envelope(properties: dict[str, Any], *, measurement: str) -> dict[str, Any]:
"""The keys both artifacts share, plus this artifact's own."""
shared = {
@@ -310,6 +369,7 @@ def _envelope(properties: dict[str, Any], *, measurement: str) -> dict[str, Any]
"measurement": _string("What this artifact measures, in one sentence."),
"source": _source_schema(),
"records": _integer("Records measured."),
+ "recorded_zero_review": _zero_review_schema(),
}
return {**shared, **properties}
diff --git a/tests/test_artifact_schemas.py b/tests/test_artifact_schemas.py
index 6d5c0b2..504f5b7 100644
--- a/tests/test_artifact_schemas.py
+++ b/tests/test_artifact_schemas.py
@@ -62,7 +62,7 @@
#: The keys `perimeter.artifacts._field_json` writes conditionally, and nothing else.
#: Every other key in every object of both artifacts is required.
-OPTIONAL_FIELD_KEYS = {"recorded_zero_values", "note"}
+OPTIONAL_FIELD_KEYS = {"recorded_zero_values", "recorded_zero_reading", "note"}
@pytest.fixture(scope="module")
diff --git a/tests/test_published_site_is_current.py b/tests/test_published_site_is_current.py
index 9eef313..81fd100 100644
--- a/tests/test_published_site_is_current.py
+++ b/tests/test_published_site_is_current.py
@@ -150,7 +150,22 @@ def spine(payload: Mapping[str, Any]) -> dict[str, Any]:
"measurement": payload["measurement"],
"source_keys": sorted(payload["source"]),
"fields": [
- [field["name"], field["label"], field["marker_basis"], sorted(field)]
+ [
+ field["name"],
+ field["label"],
+ field["marker_basis"],
+ # The zero reading is a registry decision, not a measurement, so a fixture
+ # build and a real one must agree on it exactly as they do on the basis
+ # beside it. `sorted(field)` alone catches a field that stops carrying the
+ # key and misses the case that matters: a ruling silently changed or
+ # withdrawn in `schema.py` while the published artifact keeps the old word.
+ # Measured 2026-09-13: removing `NOOFCARSONPROPERTY`'s ruling left all 534
+ # tests in tests/test_schema.py green, because every gate there reads the
+ # committed artifact and `make site-check` -- the only thing that rebuilds
+ # it -- needs data/raw/ and cannot run in CI.
+ field.get("recorded_zero_reading"),
+ sorted(field),
+ ]
for field in payload["fields"]
],
}
diff --git a/tests/test_schema.py b/tests/test_schema.py
index 8f7684f..03faa20 100644
--- a/tests/test_schema.py
+++ b/tests/test_schema.py
@@ -11,6 +11,8 @@
import pytest
from perimeter.cells import Cell, CellState, SentinelDriftError
+from perimeter.coverage import FieldCoverage, field_coverage, zero_review
+from perimeter.records import Record
from perimeter.schema import (
DINS_FIELDS,
DINS_FIELDS_BY_NAME,
@@ -19,6 +21,7 @@
Basis,
FieldSpec,
SchemaDriftError,
+ ZeroReading,
require_columns,
)
@@ -696,3 +699,264 @@ def test_the_gate_refuses_a_count_it_cannot_read() -> None:
assert problems[0].startswith(
"section 7 says 'Several' fields publish recorded zeros"
)
+
+
+# --------------------------------------------------------------------------------------
+# A zero nobody ruled on is not a measurement (ADR-0006, issue #83)
+# --------------------------------------------------------------------------------------
+
+#: The last column of section 7's table, where the registry's declared reading is repeated
+#: for a human. Matched as a backticked token so "reviewed" in prose cannot satisfy it.
+_ZERO_READING_IN_ROW = re.compile(
+ r"^\|\s*`(?P