CleanZone Field Brief

Reading a Cell Like an Analyst

A location on a map is not a verdict. It becomes one only when you have run it through the same short routine every time; read the overview, stack the layers that are actually yours, pull a report, export the numbers, and check them against lines you fixed in advance. Done properly it takes about fifteen minutes and it ends in a decision you can defend to anyone, including yourself six months later. Here is the routine, step by step.

The order is the method: overview, then your own layers, then the report, then the export, then a verdict. Skipping ahead to "does it feel nice" is how people buy problems. Decide the thresholds before you open the cell, as a written line you cannot bend around a place you already like, because the report will hand you about sixty metrics, the decade flight trend and a named public source behind every number, and every one of them is arguable after the fact.

Export the row and the comparison becomes arithmetic. One cell is a reading; a folder of cells is a shortlist. The verdict itself has three settings: pass, fail, go-look. "Maybe" means a threshold you never actually set.

There is a particular way experienced due-diligence people look at a place, and it is almost boring. They do not scroll photos. They do not start from the price. They start from a fixed list of things that would kill the deal, check those first, and only spend attention on the survivors. The CleanZone map is built to be read that way (hard filters before soft preferences, numbers before impressions) and the workflow below is simply that habit, written down so you can borrow it whole.

Before you open anything: fix the lines

The single most important step happens before you touch the map. Write down your non-negotiables and the exact value that fails each one. Not "quiet", night noise audible at 3 a.m. is a fail. Not "clean water", hardness over 120 mg/L is a fail, over 180 is a walk-away. If you set these after you have seen a place you like, you will quietly move the lines to let it through; that is human, and it is exactly the failure the list exists to prevent. The non-negotiable quiz or the threshold-table brief will build this in a couple of minutes. Keep it beside you for every cell that follows.

The fifteen-minute routine

1. Read the overview before you touch a control

   Open the map on the region and let the default CleanZone layer load. A green cell means the two definitional gates are both met in that 25 km patch: no overhead flights logged and no G-tower masts recorded. That single colour is your first cull; it tells you where the rare cells even are before you have spent a click. Zoom in one step and give the grid a moment to sharpen; the map gets finer as you go, so let it.

2. Turn on only the layers that are yours

   Two or three, no more. If soft water is a gate, add Water Quality. If sleep is the thing, add the Flight Heatmap and Night Noise. Each layer you add is a filter, and you are watching for the cells that survive all of them, which is the intersection and never the union. Somewhere that clears every layer you care about is genuinely rare, and that scarcity is the whole signal. Resist the urge to switch on all eighty; a map lit up everywhere tells you nothing.

3. Zoom for the real number

   The overview colour screens; it does not read. Zoom into a candidate cell and the resolution sharpens — soil to about a kilometre, light pollution to ~460 m, forest to ~110 m — with no settings to change; zooming is the detail control. Watch the ranked panel at the bottom: it orders the best cells for whatever layer you are viewing, and clicking a row flies the map straight to it. This is how you find the good cell you would never have guessed to look at.

4. Pull a report, the one source of truth

   Open the star tools, choose "Open a cell report", and click the cell. This is the document analysts actually work from: roughly sixty metrics grouped by family, the ten-year flight trend for that exact patch, and a named public dataset behind every figure. Read it top to bottom once. The point of the report is that it does not editorialise, it hands you WHO, EU, EPA, USGS and OpenSky figures side by side and lets you apply your own lines to them.

5. Export the row, turn memory into arithmetic

   Export the cell to CSV. The moment a reading leaves the screen and lands in a spreadsheet, comparison stops depending on what you remember about a place and starts being subtraction. Pull a row for every cell that survives the map filters, and you have a shortlist you can sort instead of impressions you have to trust. Members can pull the same figures programmatically (one call per cell) when the shortlist runs to dozens:

   # one cell, every metric, with the source behind each number
   GET /api/v1/cite?lat=43.20&lon=-8.10
   # → per-metric value + the public dataset + retrieval date, ready to paste
   #    straight into a client report or a due-diligence file

6. Run the row against your lines, and write the verdict

   Now the table you wrote at the start earns its keep. Go down it: any hard gate crossed and the cell is out, full stop, no further reading required. Everything that clears the gates gets scored on your soft preferences, and that score is the only thing you compare between survivors. Then write the word down, pass, fail, or go-look — with the date. A verdict with a date on it stays decided; a "maybe" comes back to haunt you.