Plot Emissions

Plot-level emissions metrics.

Plot metrics are the finest granularity, representing individual plot geometries.

Plot-specific attributes

FieldTypeDescription
lucnumberLand use change emissions (tCO2e)
removalnumberCarbon removals (tCO2e)
socnumberSoil organic carbon change (tCO2e)
biogenicnumberBiogenic emissions (tCO2e)
annual_emissionsobjectAnnual emissions time series
annual_agbobjectAnnual above-ground biomass time series
annual_bgbobjectAnnual below-ground biomass time series
annual_lcobjectAnnual land cover time series
annual_socobjectAnnual soil organic carbon time series
areanumberArea (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)

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 โ€” geo present only with include_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