Skip to content
Demo data · resets
  • Records through 17 Aug 2026
  • Generated sample records
  • Resets on every visit; nothing is saved.
Restoration monitoring Demo Data Hub

Data & methods

Data checks

Advisory questions about the generated records. Opening a question changes nothing.

Correct the record · 3

Executed · 3 questions, one per record Warning

Should the taxon assignment for this tag be reconciled?

The same generated plant tag carries more than one taxon assignment across reads.

What to do: Keep the species the planting record supports and correct the other reads.

Run 17 Aug 2026 Review 3 records
Executed · 3 questions, one per record Warning

Should the planting and first-read dates be reconciled?

The generated planting date follows the earliest generated monitoring read.

What to do: Check the planting sheet and correct whichever date is wrong.

Run 17 Aug 2026 Review 3 records
Executed · clean For review

Can each restoration species label be resolved?

This check completed and found no unresolved generated restoration label.

What to do: Nothing to do now; the check stays on so a new unresolved label would show here.

Run 17 Aug 2026 Review clean result

Confirm in the field · 2

Executed · 13 questions, one per record For review

Should this status sequence be reconciled?

A later generated read reports a more-live status after a terminal status.

What to do: Confirm the plant's status on the next visit, then correct the earlier read if needed.

Run 17 Aug 2026 Review 13 records
Executed · 5 questions, one per record Warning

Were all expected plant reads recorded for this plot read?

The plot-level generated read reports one or more plants without a corresponding scored read.

What to do: Score the missing plants on the next visit to the site.

Run 17 Aug 2026 Review 5 records
Executed · 4 questions, one per record For review

Plan around it

Is a monitoring read due for this established plot?

The generated plot has passed the configured age threshold without a generated plot read.

What to do: Schedule a first monitoring read for the site.

Run 17 Aug 2026 Review 4 records

Record preparation

Check Result State
Declared duplicate public plant reads removed from analysis 7 Prepared
Plant records withheld from public views 15 Withheld
Plant-level points outside their named planting area 2 Not mapped
Plant-level points drawn on the public map 0 Not mapped: planting sites are mapped at site level

What each check asks

Every check below ran on the generated records through 17 Aug 2026. Each one asks a question; none of them changes a record.

Correct the record

Should the taxon assignment for this tag be reconciled?
The same generated plant tag carries more than one taxon assignment across reads.
What to do: Keep the species the planting record supports and correct the other reads.
Warning · Executed · 3 questions, one per record
Should the planting and first-read dates be reconciled?
The generated planting date follows the earliest generated monitoring read.
What to do: Check the planting sheet and correct whichever date is wrong.
Warning · Executed · 3 questions, one per record
Can each restoration species label be resolved?
This check completed and found no unresolved generated restoration label.
What to do: Nothing to do now; the check stays on so a new unresolved label would show here.
For review · Executed · clean

Confirm in the field

Should this status sequence be reconciled?
A later generated read reports a more-live status after a terminal status.
What to do: Confirm the plant's status on the next visit, then correct the earlier read if needed.
For review · Executed · 13 questions, one per record
Were all expected plant reads recorded for this plot read?
The plot-level generated read reports one or more plants without a corresponding scored read.
What to do: Score the missing plants on the next visit to the site.
Warning · Executed · 5 questions, one per record

Plan around it

Is a monitoring read due for this established plot?
The generated plot has passed the configured age threshold without a generated plot read.
What to do: Schedule a first monitoring read for the site.
For review · Executed · 4 questions, one per record
Thresholds in use Fixed in this demonstration

The values the checks and the Action center read. None can be changed here.

Check Setting Configured value
Action center: visit list Configured monitoring cadence 180 days
Action center: visit list Upcoming window 30 days
Action center: visit list Revisit bar 353 days, measured from 108 gaps between recorded visits

Restoration

Records

One record type at a time.

Demo data
What the columns mean
Planting site
The public alias of one planting site.
Planting area
The planting area, by its public label.
Cohort
The planting year.
Established
When the site was established.
State
Active, destroyed or access lost.
Recorded area
Site area in hectares.
Public plant records
Plants on the site shown in public views.
Reads
Monitoring reads on file.
Last read
Date of the latest read.
Data status
Demo data on every row. In the file; left off the screen.
Record class
GENERATED_SAMPLE on every row. In the file; left off the screen.
What the columns mean
Plant ID
The public alias of one planted plant.
Planting site
The site it was planted in.
Planting area
The planting area, by its public label.
Plant
The species planted.
Cohort
The planting year.
Planted
The planting date.
Method
How it was planted.
Cage
Whether a cage was fitted at planting.
Reads
Monitoring reads of this plant.
Latest recorded status
Status at the latest read.
Data status
Demo data on every row. In the file; left off the screen.
Record class
GENERATED_SAMPLE on every row. In the file; left off the screen.
What the columns mean
Visit
The public alias of one site visit.
Planting site
The site visited.
Planting area
The planting area, by its public label.
Date
The visit date.
Type
Full read or partial read.
Cage
Cage state recorded at the visit.
Water hauled
Whether water was hauled.
Nurse canopy
Nurse plant canopy cover, once the form carried it.
Unscored public plant records
Plants on the site without a scored read at this visit.
Data status
Demo data on every row. In the file; left off the screen.
Record class
GENERATED_SAMPLE on every row. In the file; left off the screen.
What the columns mean
Record
The public alias of one plant read.
Plant
The plant read.
Visit
The site visit the read belongs to.
Date
The read date.
Planting area
The planting area, by its public label.
Plant age
Days since planting.
Status
The recorded status, decoded.
Height
Plant height.
DBH
Stem diameter, where it applies.
Data status
Demo data on every row. In the file; left off the screen.
Record class
GENERATED_SAMPLE on every row. In the file; left off the screen.
What the columns mean
Field
The form field counted.
Not recorded
Records where the field is blank.
Records
Records the field applies to.
State
How a blank value in the field should be read.
Data status
Demo data on every row. In the file; left off the screen.
Record class
GENERATED_SAMPLE on every row. In the file; left off the screen.
What the columns mean
Domain
The coded list a field draws from.
Label
What the code means.
Active
Whether the code is still offered on the form.
Data status
Demo data on every row. In the file; left off the screen.
Record class
GENERATED_SAMPLE on every row. In the file; left off the screen.

Restoration

Reports

One question per report, each checked against its own totals.

Restoration

Methods

Where a screen and this page differ, one of them has a defect.

How every figure on these screens is computed

Every record here is generated and runs through 17 Aug 2026. Each section below names the screen it explains; every number in it is read from the same setting or count the screen uses.

Action center

The visit list

What is drawn
One row per active planting site that meets a visit reason: 10 of 20 active sites.
When it appears
Five reasons in order, first match wins: never visited; a plant nobody could find; a plant not scored at the last visit; recorded dead, then alive; not visited in over 353 days.
What counts as overdue
The overdue bar is the upper quartile of 108 measured gaps between visits to one site: 353 days. With too few gaps the 180-day plan cadence would stand in, with a 30-day upcoming window.
What would throw it off
A visit date typed a season late shortens the gaps around it and moves the bar for every site.

Survival

Survival bounds

What is drawn
Per cohort, a band at each recorded plant age between two readings of the same records, never one number.
When it appears
Cohorts are never pooled: 6 cohorts are drawn apart, each only as far as its own reads reach.
What counts as an unknown plant
A plant whose fate at an age is not on file. Lower edge: Every unknown counted dead, including never-monitored plants. Upper edge: Every unknown counted alive, including never-monitored plants.
What would throw it off
Settling an unknown plant either way. Not found is not a death, and choosing one edge would move the figure by the width of the band.

Map

The site map

What is drawn
Each of 22 planting sites at its recorded center, one mark size. Color carries one fact: whether the site is on the visit list.
When it appears
Always at site level. A plant-level point is never drawn, and recorded plot area is not encoded at all.
What counts as on the list
The same test as the visit list, on the same records: 10 sites are drawn as listed.
What would throw it off
A site center recorded in the wrong place is drawn there. The map does not move positions to look right.

Plants and every download

Public records

What is drawn
Reader-facing identifiers are generated aliases: RS- for a planting site, RP- for a plant.
When it appears
A plant record reaches a table or a file only when it is publishable: 465 are, and 15 are withheld everywhere.
What counts as withheld
A record whose disclosure class does not allow it on a public page. A withheld record never reveals its planting site, not even as a count on that site.
What would throw it off
A disclosure class entered wrongly publishes or hides a whole record. Every download carries Demo data and GENERATED_SAMPLE on every row.

Data & methods: Reports

Reports

What is drawn
Each report prints one table and, above it, a second computation of its own totals.
When it appears
Every time the pane opens, from the records as loaded (through 17 Aug 2026); a report that cannot be prepared says so instead of printing zeros.
What counts as agreement
Two totals agree when they are equal, or when a part does not exceed its whole. Every pair is listed with both values under The pairs compared.
What would throw it off
A record that belongs to no site breaks a pair, and the report then leads with the disagreement rather than the table.

What these records can and cannot support

Read from the claim policy every figure on these screens obeys: 6 of 16 quantities can be drawn for at least one record group, 10 are refused outright, and 2 are refused for some groups.

These records support (6)

  • Plants planted Every record group.
  • Survival bounds per cohort Every record group.
  • Survival at a given age Record groups: followed, stopped, not found. Caveat for stopped: This arm's plants stopped being read before the age asked about, so their fate at that age is an assumption and the value is carried only as one edge of a band. Caveat for not found: This arm's plants were looked for and not found, so counting them alive or dead is a choice rather than a record, and the value is carried only as one edge of a band.
  • Survival by species Record groups: followed. Caveat for followed: The comparison holds the plot constant and therefore holds the planting year constant, because every plot carries exactly one year; it does not hold the planting window, the stock source or the weather of a first summer constant, and it cannot.
  • Monitoring effort Every record group.
  • A map of planting sites Every record group.

These records do not support (10)

  • One survival figure across cohorts No survival number pooled across cohorts is computed anywhere in this program. The cohorts differ substantially at the same age, and an average would conflate two different populations.
  • Time to death No time-to-event statistic of any kind is computed. Dead is not absorbing in these records: plants are read again after a dead score and some return to alive, which on drought-deciduous stock is often two correct records rather than one wrong one. And the censoring is informative: the largest censoring event removed the worst-performing plot, so a risk-set denominator makes survival rise.
  • Height growth Growth is not computed from recorded height. Among the plants eligible for the check, a small minority rise throughout and a much larger group end shorter than they started. A stem measured to the nearest centimeter by a different person each visit is being re-established, not re-measured.
  • Stem-diameter growth Growth is not computed from recorded stem diameter. Diameter is essentially uncorrelated with plant age and with recorded height in these records, and the correlations are computed and printed rather than asserted.
  • Saguaro arm counts Arm count is unreachable rather than merely empty. The field is scoped to a saguaro at least two meters tall, and the tallest plant of any taxon in these records is far short of that, so no read could ever have qualified. Both heights are drawn so the refusal is arithmetic rather than assertion.
  • A planting-method effect Planting method is not drawn as a treatment. The spread between the three methods is a few points against a cohort spread of tens of points, and methods are not randomized across plots or years. A method contrast here is a cohort contrast wearing a method label.
  • A cage effect Caging is not drawn as a treatment. Cage state moves with the calendar and therefore with cohort age, the never-caged reference arm is thin, and nothing is randomized.
  • A watering effect Hauled water is not drawn as a treatment. Supplemental water is a step function of calendar year in these records, perfectly collinear with cohort age, so a water contrast is a relabelling of the year.
  • A map of individual plants No plant is drawn on any map. A large minority of the plant points sit farther from their plot's centroid than the plot's own radius, and two are absurd. The measured share is printed so the refusal is checkable.
  • The mix of photograph kinds No photo-keyword breakdown is drawn. A majority of this program's photographs carry keywords from the other three programs' vocabularies, because the generator draws from one shared pool. The mix is a property of the generator and nothing else.
Refused for some record groups only (2)
  • Survival at a given age Refused for: never read. A point value on the never-read arm would be invented outright. Nobody ever returned to these plots, so there is no read of any kind to compute a share from.
  • Survival by species Refused for: stopped, not found, never read. Stopped: A species contrast on plants whose plots stopped being read compares species against different follow-up, not against different ground. Not found: A species contrast cannot be built on plants nobody located. Never read: A species contrast cannot be built on plots nobody visited.

Questions this data can answer

Choose one question. Each answer shows what was counted, what was left out, and the decision it can support.

All questions