Biome Lookup and Peer Matching

The Action Ideas tab shows the jurisdiction’s biome as Similar climate conditions: {ecoregion}. In the data model and API this value is named ecoregion; the product uses the broader, user-facing phrase “similar climate conditions.”

Lookup flow

1. The data pipeline assigns each jurisdiction an ecoregion in the BigQuery table dim_cdp_geo_and_ecoregion_TEST, using the jurisdiction geometry.
2. The pipeline loads that assignment into the Cloud SQL table CSTAR_2025_Dim_Central.
3. The backend location metadata lookup reads CSTAR_2025_Dim_Central.ecoregion for the requested CDP organisation number.
4. The location profile API returns the nullable value as LocationProfile.ecoregion.
5. The frontend displays the value above the Action Ideas hazard filters. If it is absent, the page uses its generic peer-jurisdiction explanation instead.

This is a stored lookup, not a biome calculation performed in the browser or during an API request.

How it affects Action Ideas

Peer actions are prepared from jurisdictions in the target jurisdiction’s ecoregion and hazard pool. The pipeline ranks the candidate actions for each target and hazard filter, keeps the top 25, and the API groups a maximum of five examples per action category for display.

The ecoregion is therefore both explanatory UI context and an input to peer matching. A missing ecoregion can leave a jurisdiction—particularly a non-discloser—without peer matches and produce an empty Action Ideas result. A geometry correction can also change the assigned ecoregion and consequently change the peer actions shown.

Implementation references

• Backend model: backend/app/models/location_details.py (DimCentral.ecoregion)
• Cloud SQL lookup: backend/app/services/clients/database/location_details_repository.py (get_metadata)
• API response: backend/app/schemas/location.py (LocationProfile.ecoregion)
• Frontend display: frontend/src/app/features/location-card/solutions/solutions.component.html
• Pipeline methodology: docs/data_pipeline.md
• Peer solution tables: docs/data.md
• Shipped feature: CDPworldwide/cdp-adapt-ex#53
• Condensed display copy: CDPworldwide/cdp-adapt-ex#62

Known follow-up

The biome value is visible in the UI, but the product still needs a methodology tooltip or link that explains its role in peer matching to end users.