Send us the boundary you want watched.
A concession, a supply shed or a district is enough. Tell us who should get the weekly list and we will scope the project from there.
A clearing shows up. You hear about it within days of the first clear pass.
Swap the manual imagery check and the annual land-cover update for a weekly alert list on the monitoring area you define, flagged within days of the first cloud-free pass.
- GSD
- Medium / 3–10 m
- Cadence
- Weekly
- Platform
- Medium-res satellite
- Spectral
- Multispectral
Found after the chainsaws have gone
Someone opens the viewer, pans across the priority districts and flips between this year's imagery and last year's. It takes a while, it depends on who is at the desk, and some districts get looked at less than others.
Or the team waits for the annual land-cover update and finds a clearing long after the fact. By then the land has been burned, planted or sold, and the referral goes out as a letter about something already done.
The same monitoring area, checked two ways
| Step | The manual check | With Deforestation Alerts |
|---|---|---|
| Finding new clearings | An analyst pans the viewer district by district and compares against an older scene, or waits for the annual land-cover product. | Every week the monitoring area is compared with the pass before it, and new clearings come back as polygons. |
| Sizing what was cleared | The polygon is traced by hand in the GIS and the hectares read off it, when there is time. | Each alert carries a cleared-area estimate from the pass that found it. |
| Building the list for the field office | Coordinates pasted into a spreadsheet or a case form, a few at a time, from whatever the analyst found that week. | One alert list for the week, by polygon, plus an export shaped for an enforcement or supplier referral. |
| Knowing whether a district was actually looked at | Which districts were skipped last month is rarely written down. | Every alert is tied to the pass date it came from, and the whole monitoring area is compared every week there is a clear view. |
| Still yours Reading the evidence, deciding what is a true clearing, and every call to a field office or supplier. | ||
| Screening supplier plots | Supplier polygons are checked once in a review cycle, against the last annual map. | Load your sourcing polygons as the monitoring area and new clearings inside or beside them appear in the weekly list. |
| Deciding what happens next | The analyst or sustainability lead weighs each case against a file, a contract or a campaign plan. | The same people decide. The list reaches them sooner and says where to look. |
| Still yours Enforcement referrals, supplier decisions and any legal step. Nothing is sent on automatically. | ||
What lands each week
One set of files per week for your monitoring area, in formats your GIS and case files already take.
- GeoJSON / CSV
Weekly alert list
New clearings flagged since the last pass, one row per polygon, with the date of the pass that found each. It is the file your analyst opens on Monday.
Finding new clearings - Column in the list
Cleared-area estimate
Hectares flagged per alert, taken from the pass that detected it. Use it to rank the list and to decide what goes to the field first.
Sizing what was cleared - GeoJSON
Alert map layer
The same polygons as a layer to drop over your concession, supply shed or jurisdiction boundary in the GIS you already run.
Screening supplier plots - CSV
Referral export
The week's alerts laid out for an enforcement referral or a supplier query, with the fields a case file asks for. Your team adds the evidence and sends it.
Building the list for the field office
From boundary to alert list
You send the area once. The list comes back every week.
- Setup
Define your monitoring area
A boundary file: a concession, a supply shed, a district or a set of supplier plots. Tell us who should get the list.
- Every week
Weekly cloud-free pass
We take the next medium-resolution multispectral pass over the area with a clear view of the ground.
- Every week
Change detection
The new pass is compared with the one before. Ground that was forest and no longer is gets flagged as a clearing alert.
- Within days of the pass
Delivery
The alert list, cleared-area estimates and map layer go out to the people you named.
- Every week
What the manual check still does better
Read these before you build a routine around the list.
Cloud holds an alert back
The imagery is optical. Under persistent cloud there is no clear pass, and a clearing waits for the next one. We do not report what we have not seen.
Small and partial clearings
At 3–10 m a pixel is 3 to 10 metres across. A clearing needs several pixels to show up. Selective logging, narrow tracks and single trees may not register until they grow.
Weekly, not instant
Alerts follow the cloud-free pass and go out within days of it. This is not a live feed, and a clearing that starts and finishes between passes is seen late.
Flags, not findings
Each alert marks ground that changed. A person decides whether it is a clearing for your purposes. Some flags will turn out not to be.
Forest loss, not its cause
The list says where and roughly how much. It cannot say who cleared it, for what, or whether they had a permit.
Switch if
- You monitor forest for an agency and want the news that week, not after the annual update.
- You screen a supply shed or supplier plots for a commodity buyer and need new clearings listed against your boundaries.
- Your team already reads polygons in a GIS and has someone to triage the list.
Stick with the manual check if
- You need to know the day a tree came down, or catch single-tree logging.
- You want alerts sent straight to enforcement with no one reviewing them.
- You need a legal finding or a named party behind a clearing.
Before you switch
Do we stop checking imagery ourselves?
No. Your analyst still looks at the evidence. The list says which districts to look at first.
How do we check it against our own records?
Hold the first weeks of alerts up against your field reports, permits and the imagery you already use. If something looks wrong, send it back and we will go through that week's pass with you.
What happens in a cloudy stretch?
The alert waits for the next cloud-free pass. We do not guess at a clearing we have not seen.
How small a clearing can you flag?
It is tied to the 3–10 m pass. Small or partial clearings near that limit may not register until they grow.
Do alerts go to enforcement automatically?
No. Alerts are flagged for your team to review. Nothing is referred on without a person.
Is this real-time?
No. It is weekly, tied to the next cloud-free pass.
Will it fit our GIS and case system?
There is no direct integration. You get GeoJSON and CSV, which open in the GIS and spreadsheet tools you already run.
Who owns the alerts, and can we share them?
Your boundary stays yours. What you can do with the alert files, and the licence on the imagery behind them, is written into the project agreement before the first week runs.
How is it priced?
It depends on the size of the monitoring area and how long you want it watched, so we quote after we have seen the boundary. There is no price list on this page.