create_monitored_area
Set up continuous satellite monitoring for a fixed area: choose a location and a metric (ships, fires, water, vegetation), and each new Sentinel-1/2/VIIRS image is measured automatically.
Instructions
Put a place under continuous satellite measurement: pick an area and what to count, and every new Sentinel-1 / Sentinel-2 / VIIRS acquisition over it is measured automatically from then on. Use this when the question is about a quantity at a fixed place over time ("how many ships are alongside", "how much has burned", "is the water receding") rather than about events, which is create_standing_order. Creating is free; each automatic check costs a small number of tokens only when it finds new imagery.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| bbox | Yes | The area to measure, [west, south, east, north] in WGS84. Must be under 5,000 km² — measurement is per-pixel over the area, so a country-sized box is rejected rather than silently sampled. | |
| name | No | Label for the area (default "Monitored area"). | |
| metric | Yes | What to count. Plain words work: ships, fires, vegetation, water, burn, snow, built_up, moisture, night_lights. Index names are also accepted: ship_detection, fire_count, ndvi, evi, savi, ndmi, ndwi, mndwi, ndbi, ndsi, nbr, dnb, vv, vh, rvi, rfdi, cr. The sensor is chosen from the metric. | |
| start_date | No | YYYY-MM-DD to begin the history from. Defaults to 30 days ago — a longer backfill measures more scenes and therefore costs more on the first check. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| area | Yes | ||
| summary | No | One-line natural-language summary of the result, ready to relay to a user. | |
| metering | No |