このページはまだ日本語に翻訳されていないため、英語で表示しています。
Reading a report
What is inside a CropWatch report, part by part, and how to get the sense of one in about a minute.
このページの内容
A report is a PDF, emailed to everyone on its recipient list. One sensor, one report: a template covering four sensors sends four PDFs.
Every page carries the same dark blue bar across the top with the report's name, the period it covers, the sensor and its location, so a printed page is never orphaned. Along the bottom, the same three details and the page number.
The first page is the summary. The pages after it are the readings, and the last page holds any notes.
Under the title bar are the details of what you are looking at:
- Location and Device Name — where the sensor is and what it is called in CropWatch.
- Device Type — Air Sensor, and so on.
- Dev EUI — the sensor's serial number. Quote this if you ever ask us about a reading.
- Period — the days the report covers.
- Samples — how many readings went into it. A week of readings every 15 minutes is about 672.
On the right are three empty boxes: “Approved”, “Reviewed” and “Prepared”. They are for signatures. If your paperwork needs someone to sign off the week, print the report and sign there.
Under the details is a short list of coloured squares. These come from the alerts set on the report, and they are the fastest thing on the page to read.
Each line says the same three things:
- What it is watching for, and at what number.
- How many readings crossed it.
- What share of the whole period that was.
“High Temp (≥ 25°C): 82 (27%)” means 82 readings were at or above 25 °C, which was 27% of the week. Not a disaster, but not nothing either.
The same colours are used further down, on the readings themselves. That is how you find which hours they were.
Two boxes give the period in four numbers each.
- Max — the highest reading.
- Min — the lowest.
- Avg — the average across every reading.
- Std Dev — how much the readings moved about. Small means steady; large means it swung. Two weeks can share an average and be nothing alike, and this is the number that tells them apart.
A greenhouse averaging 21 °C with a standard deviation of 1 °C held steady. The same average with 6 °C was on a rollercoaster.
The chart is the shape of the period. Two lines are drawn on it, and they use different scales:
- The red line is temperature, read against the numbers on the left edge, in degrees.
- The blue line is humidity, read against the numbers on the right edge, as a percentage.
The regular rise and fall is day and night. What to look for is anything that breaks the pattern: a night that did not cool, a spike in the middle of the afternoon, a flat line where the sensor stopped reporting.
Because the two lines use different scales, they cross each other often. That means nothing in itself.
The rest of the report is the readings themselves, two columns to a page to save paper: a time, the temperature, the humidity, and a Comments column.
The rows are spaced by the report's “Data pull interval” — every 30 minutes unless it was changed.
Two things stand out in this table:
- Coloured readings — a value shaded red or amber crossed one of the limits at the top of the report. The colour tells you which one.
- A small number in Comments — somebody wrote a note about that reading. The note itself is on the last page.
A reading that set off an alert is always listed, even when the spacing would otherwise have skipped past it. Nothing that crossed a limit is hidden.
If anybody added notes, the final page is headed “Report Notes” and lists them in order, each with its time and who wrote it.
This is where the report explains itself. A spike at two in the afternoon looks alarming on its own; “sensor briefly in direct sun” turns it into nothing. Without the note, somebody re-investigates the same spike next month.
The numbers in the Comments column match the numbers here. If there are no notes, the page is not printed at all.
Notes are added afterwards, from the Reports page, and the report is rebuilt with them. It is not emailed round again — the copy with notes sits beside the original, ready to download.
If a report lands in your inbox and you have a minute, do this:
- Check the period and the sensor name in the title bar — the right report about the right thing.
- Read the coloured lines. No lines at all means nothing crossed a limit.
- Look at the two panels. Are Max and Min where you expect?
- Glance at the chart for anything that breaks the daily rhythm.
- Only then go to the table, and only for the hours you care about.
The table is there for proof and for the record. The first page is the one that tells you whether to worry.
Every report is kept. On the Reports page, the clock button on a row lists everything that template has produced, newest first, with a “Download” button on each.
That is the place to go for last quarter's paperwork, or when somebody deleted the email.
Readings are kept for 24 months, and notes can be added to a report for up to 23 months after its period ends. Older reports can still be downloaded; they simply cannot be annotated.
The report is produced with Japanese labels — 温度 for temperature, 湿度 for humidity, 備考 for comments. The layout, the numbers and the colours are the same either way; only the words change.
If your reports should be in English instead, ask support to switch them. It is not something you can change yourself on the Reports page.