How to Prepare a Consistent Weather Observation for a Citizen-Science Project
Prepare the parts that are useful everywhere—time, place, method, value, and uncertainty—then leave the project-specific parts blank until you check the named programme’s current instructions. That sequence giv

Prepare the parts that are useful everywhere—time, place, method, value, and uncertainty—then leave the project-specific parts blank until you check the named programme’s current instructions. That sequence gives you a truthful observation packet without pretending that every citizen-science project uses the same instrument, schedule, or form.

Start with two layers of information
Make two columns before you observe:
| Reusable in most projects | Must be checked for the named project |
|---|---|
| Date and local time | Official observation time or reporting window |
| Place and viewing or sensor position | Required station ID, coordinates, or site approval |
| What you observed and how | Accepted variable, instrument, units, or code |
| Missing fields and uncertainty | Training, login, deadline, and correction rules |
The NCEI metadata guidance treats geographic and temporal extent, descriptive fields, and variable/unit keywords as documentation that should be planned rather than reconstructed later. Use that as a thinking aid, not as a universal submission form.
The NWS WxCoder guide shows why the distinction matters. Its station information includes an identifier, official observation time, location, elevation, and supervising office. Its daily observation also covers a defined period before that official time. A personal note can borrow the habit of recording these fields without claiming that it is already an NWS report.
Build the generic observation packet
Before opening a project form, complete this small packet:
- Observation identity: a short label such as “back garden, east fence, visual sky and rain note.”
- Date and time: local date and clock time, plus the time zone or daylight-saving convention if it matters.
- Place: a usable description, coordinates if you know them, and the position of the observer or sensor.
- Variable: what you are reporting—rainfall, cloud amount, temperature, wind cue, or another defined element.
- Method: what you did, what instrument or visual cue you used, and the reading interval.
- Value and units: the number, category, or plain-language description exactly as observed.
- Conditions and exposure: shade, obstacles, blocked view, surface, or anything that could change the result.
- Uncertainty: unknown time basis, estimated amount, missing instrument, or any reason the value should not be treated as exact.
This is documentation, not certification. The NCEI metadata guidance recommends planning geographic and temporal information early because it is harder to reconstruct after collection. For a home observation, “record it while you are there” is the practical version of that principle.
If you use a photograph, voice memo, or spreadsheet, give it the same observation label as the written note. A file called IMG_4821 is difficult to reconcile later; 2026-11-18_0720_back-garden-east-fence keeps the evidence tied to the packet. The file name does not prove the observation, but it reduces the chance that a useful image becomes separated from its time, place, and method.
Add a verification card before submission
Do not submit the generic packet until you have a small verification card beside it:
| Verification field | What to write |
|---|---|
| Programme name | The exact project or network |
| Current rules URL | The page or document you checked |
| Checked on | Date of your verification |
| Required variable | The project’s wording, not your paraphrase |
| Required method or instrument | Copy the requirement or mark “not yet known” |
| Official time window | Required time, local convention, or reporting interval |
| Missing project field | Leave blank until confirmed |
| Question to resolve | The smallest unanswered question |
The checked-on date matters because programmes change forms, schedules, and eligibility. A note that says “rules checked” but gives no date cannot tell a later reader which version you followed.
Keep the project-specific blank visible
Imagine that your notes are ready for a precipitation project, but you have not confirmed whether it accepts an estimated amount after a gauge overflow. Do not fill the blank with “probably acceptable.” Write:
> Project-specific field: overflow procedure — not verified. Current instructions checked: [project URL], 18 November 2026. Question sent: should the amount be reported as a value, an estimate, or a missing field?
That sentence preserves the generic observation while stopping you from claiming compliance. The same rule applies to an unfamiliar time window, a required station number, a training step, or a method that your equipment cannot perform.
A completed pre-submission packet
The following is hypothetical. It is a preparation example, not a report submitted to a real project.
> Observation label: back garden, east-facing fence > > Date/time: 18 November 2026, 07:20 local time; time zone recorded in the journal > > Variable: visible rainfall at the site; no rain gauge reading taken > > Method: stood at the same marked position for five minutes; noted whether rain was falling and photographed the view from the same direction > > Value: rain visible for about two minutes, then no rain; amount not measured > > Exposure: fence and roof edge partly blocked the east view; observer remained under cover > > Uncertainty: no measured accumulation; exact start and end times are approximate > > Programme check: named project and current instructions not yet selected; method, instrument, required time, and station fields remain blank
This packet is useful even before it is eligible for submission. It tells a future reader what happened, where, when, and how, while clearly marking the field that still needs a project rule.
Use one programme as an example, not a template
The CoCoRaHS data-quality page describes a programme-specific daily precipitation observation, training materials, and separate intense-rain or hail reports. Those details illustrate why a project can define its own schedule and report type; they do not create universal rules for every citizen-science network.
If you choose CoCoRaHS, read its current instructions for the station, gauge, training, observation time, and report form. If you choose another project, replace the CoCoRaHS fields with that project’s wording. The packet stays the same in spirit, but the blanks and acceptance rules may change.
Stop, verify, or keep the note private
Use this decision rule:
- Ready to verify: your generic packet has time, place, method, value, and uncertainty.
- Ready to ask: one project-specific field is missing, and you can state the exact question.
- Not ready to submit: you do not know the current rule, cannot meet a required method, or would have to reconstruct a value from memory.
- Still useful privately: keep the observation as a personal record and label it as such.
For the difference between a private journal, a programme report, and official information, see A Private Weather Journal or a Citizen-Science Report? Choose the Right Record. For site and exposure context, use How to Record Your Weather Sensor Location and Exposure. A consistent packet improves the truthfulness of a possible submission; it does not guarantee acceptance or turn a local note into an official observation.