API Explorer 896 endpoints

Get digital_mrv_observation List

GET /obp/dynamic-entity/banks/ogcr/digital_mrv_observation

OBPv4.0.0-dynamicEntity_getdigital_mrv_observationList_ogcr Roles: CanGetDynamicEntityRecord_digital_mrv_observation(per bank) _Digital_mrv_observation(ogcr)Dynamic-EntityDynamic

Get digital_mrv_observation List.

A single digital MRV (Monitoring, Reporting and Verification) output record for a parcel, covering a defined monitoring period. dMRV uses satellite imagery, geospatial data, and modelling (from WP3) to quantify soil organic carbon (SOC) and biomass changes continuously and at scale, without requiring a formal CRCF audit for each period. These records feed into Batch NFT issuance at the CRCF registry layer and into Scope 3 marketplace pricing and filtering. This Dynamic Entity is part of OGCR.

Property List:

  • digital_mrv_observation_id: Unique internal identifier automatically assigned to this dMRV observation record.
  • parcel_id: The parcel this observation covers. Links the dMRV result to the parcel geometry, ownership record, and any associated CRCF activity.
  • growing_season_id: Optional link to the specific crop season this observation is associated with. Useful when dMRV data is available at crop-season resolution, allowing the carbon signal to be attributed to a particular practice change (e.g., cover cropping in winter 2026).
  • observation_date_start: Start date of the monitoring window covered by this dMRV observation. Defines the period over which carbon stock changes are measured. Must align with the activity or reporting period for CRCF or Scope 3 use.
  • observation_date_end: End date of the monitoring window. Together with observation_date_start, this defines the observation period. Corporate buyers need this to confirm the period overlaps their reporting year.
  • digital_mrv_protocol: The name and version of the dMRV methodology used to produce this estimate. Generated by WP3. Required for audit trails, marketplace filtering, and CSRD methodology disclosure.
  • data_source: The primary remote sensing or modelling data source used to generate this observation. Controlled vocabulary: sentinel2, planetscope, modelled (no imagery), combined (imagery + model ensemble).
  • lulc_classification: The Land Use / Land Cover (LULC) class assigned to this parcel during the observation period, using the LUCAS classification standard. Used to confirm the parcel is in active agricultural use and to flag land use change events that would affect carbon accounting.
  • soc_estimate_t_per_ha: The soil organic carbon (SOC) stock on this parcel under the counterfactual baseline scenario (what would have happened without the activity), expressed in tonnes of carbon per hectare. Derived from the GCDC standardised baseline for the parcel's pedoclimatic zone.
  • soc_baseline_t_per_ha: The measured or modelled soil organic carbon stock on this parcel at the end of the observation period, in tonnes of carbon per hectare. Compared against soc_baseline_t_ha to determine the net carbon removal signal.
  • soc_delta_t_per_ha: The change in soil organic carbon stock between the baseline and the end of the observation period, in tonnes of carbon per hectare. A positive value indicates carbon sequestration. This is the primary carbon removal signal used for the Parcel Snapshot.
  • biomass_estimate_t_per_ha: Above-ground biomass carbon stock estimated for this parcel at the end of the observation period, in tonnes of carbon per hectare. Relevant for agroforestry or perennial cropping activities where above-ground woody biomass contributes to the carbon removal claim.
  • uncertainty_pct: The percentage uncertainty band around the SOC or biomass estimate, reflecting model error, spatial heterogeneity, and data quality. Required by CRCF methodology rules and used by the Scope 3 marketplace to apply conservative discounting to credit quantities and pricing.
  • data_quality_indicator: A tiered quality rating for this dMRV observation, reflecting cloud cover, image resolution, model confidence, and validation against ground-truth samples. Controlled vocabulary: high, medium, low. Used by certifiers and marketplace buyers to assess reliability.
  • risk_score: A score between 0 and 1 representing the probability of carbon reversal on this parcel over the monitoring period, produced by the WP4 risk assessment model. A higher score means higher reversal risk. Used by the registry to apply buffer pool deductions and by the marketplace to adjust pricing.
  • verification_method: Indicates whether this observation was verified through automated dMRV only, a traditional CRCF third-party audit, or a combination of both. Determines the applicable pathway.
  • generated_by: The name and version of the WP3 processing pipeline or algorithm that produced this observation. Needed for reproducibility, audit trails, and methodology version tracking.

MethodRouting settings example:

<details>

{
  "is_bank_id_exact_match":false,
  "method_name":"dynamicEntityProcess",
  "connector_name":"rest_vMar2019",
  "bank_id_pattern":".*",
  "parameters":[
    {
        "key":"entityName",
        "value":"digital_mrv_observation"
    }
    {
        "key":"url",
        "value":"http://mydomain.com/xxx"
    }
  ]
}

</details>

User Authentication is Required. The User must be logged in. The Application must also be authenticated.

Filtering, sorting and pagination on the list endpoint:

Queryable (declared indexed) fields: digital_mrv_observation_id, growing_season_id, parcel_id.

  • Filter: ?obp_filter[FIELD]=OP:VALUE. Operators: eq, ne, in, lt, gt, le, ge, between, like, is_null, not_set. in / between take comma-separated values; is_null / not_set take no value. Repeat the same key to AND several constraints on one field. e.g. ?obp_filter[status]=eq:active&obp_filter[amount]=between:10,100 or ?obp_filter[closed_date]=not_set
  • Legacy filter (still supported): bare field parameters, e.g. ?name=James%20Brown&number=123.456&number=11.11 filters by name == "James Brown" && (number == 123.456 || number == 11.11).
  • Sort: ?obp_sort_by=FIELD[,FIELD2]&obp_sort_direction=ASC|DESC.
  • Paginate: ?obp_limit=20&obp_offset=40.

Filtering, sorting, pagination and is_null / not_set work on every deployment (no special backend required).

One-hop joins (EXISTS / NOT EXISTS) — filter this entity by a condition on a related entity linked through a declared reference: field:

  • ?obp_exists[RelatedEntity] — keep rows that have at least one related RelatedEntity.
  • ?obp_exists[RelatedEntity]=filter[FIELD]=eq:VALUE — ...that have at least one matching the predicate.
  • ?obp_not_exists[RelatedEntity] — keep rows with NO related RelatedEntity at all.
  • ?obp_not_exists[RelatedEntity]=filter[FIELD]=eq:VALUE — ...with no related RelatedEntity matching the predicate (this includes rows that have no related RelatedEntity).
  • If two entities are linked by more than one reference, disambiguate the edge with via:, e.g. ?obp_exists[RelatedEntity]=via:buyer_ref;filter[status]=eq:signed.

The nested filter[...] reuses the operator grammar above. Mind the distinction: obp_not_exists[X]=filter[flag]=eq:true (no related X with flag=true — includes rows with no X) is not the same as obp_exists[X]=filter[flag]=ne:true (has a related X with flag≠true — excludes rows with no X).

Only a field typed reference:<Entity> and declared indexed: true forms a join edge; a plain string field holding ids is not joinable.

This entity's reference fields (each usable as a one-hop join edge to its target entity): growing_season_id → growing_season, parcel_id → parcel.

Joins require the SQL projection backend (dynamic_entity.indexing.backend=auto on Postgres or SQL Server) with the involved fields indexed and ready. On an in-memory deployment a join query returns 400 (OBP-09022); while an index is still building it returns 409. The plain filter / sort / paginate / is_null / not_set features above do not need the projection backend.

Example success response
{
  "bank_id": "ogcr",
  "digital_mrv_observation_list": [
    {
      "digital_mrv_observation_id": "3dece208-c95c-11f0-9041-54e1adfac5b1",
      "parcel_id": "3dece208-c95c-11f0-9041-54e1adfac5b1",
      "growing_season_id": "3dece208-c95c-11f0-9041-54e1adfac5b1",
      "observation_date_start": "2026-01-01",
      "observation_date_end": "2026-12-31",
      "digital_mrv_protocol": "WP3-SOC-Sentinel2-v1.2",
      "data_source": "sentinel2",
      "lulc_classification": "cropland_annual",
      "soc_estimate_t_per_ha": 42.3,
      "soc_baseline_t_per_ha": 44.1,
      "soc_delta_t_per_ha": 1.8,
      "biomass_estimate_t_per_ha": 3.2,
      "uncertainty_pct": 12.5,
      "data_quality_indicator": "medium",
      "risk_score": 0.08,
      "verification_method": "dMRV",
      "generated_by": "WP3-pipeline-v2.0.1"
    }
  ]
}
Possible errors (3)
  • OBP-20001: User not logged in. Authentication is required!
  • OBP-20006: User is missing one or more roles:
  • OBP-50000: Unknown Error.
Implemented by OBPv4.0.0 dynamicEntity_getdigital_mrv_observationList_ogcr Originally /banks/ogcr/digital_mrv_observation