Plot Emissions
Plot-level emissions metrics.
Plot metrics are the finest granularity, representing individual plot geometries.
โถPlot-specific attributes
| Field | Type | Description |
|---|---|---|
luc | number | Land use change emissions (tCO2e) |
removal | number | Carbon removals (tCO2e) |
soc | number | Soil organic carbon change (tCO2e) |
biogenic | number | Biogenic emissions (tCO2e) |
annual_emissions | object | Annual emissions time series |
annual_agb | object | Annual above-ground biomass time series |
annual_bgb | object | Annual below-ground biomass time series |
annual_lc | object | Annual land cover time series |
annual_soc | object | Annual soil organic carbon time series |
area | number | Area (ha) |
โถPagination
Same contract as /locations/* โ see Query Parameters โ Pagination.
- Page-number (default):
?page[number]=2&page[size]=50. - Cursor (keyset):
?page[cursor]=<value>&page[size]=50โ use for deep pagination on big result sets (e.g. all plots under a facility). At 100k-plot scale a cursor jump is ~60ms vs ~6s for page-number page=1000.
Every response carries meta.next_cursor and links.next; clients can switch from page-number to cursor at any point.
Combine with filter[assets.task_id] for the single-task fast path (entity_map narrows by task in one pivot instead of 4) and fields[metric]=โฆ to drop unused metric columns from both the SQL projection and the response.
โถGeometry (include_geometries)
include_geometries)Geometry is opt-in. By default the metric resource omits the geo
attribute (the location's geometry) โ the server doesn't read it from the
database, keeping responses small and fast. Pass ?include_geometries=true
to include it:
application/json/application/x-ndjsonโgeopresent only withinclude_geometries=true.application/geo+json/application/x-ndgeo+jsonโ geometry is always included; the flag isn't needed.
Accepted values are true / false (default false); any other value is 400. See Query Parameters โ Geometry.
Required scope:
metrics:read