Climate change objectives

[duncandewhurst]

Background

This issue relates to the following CoST IDS elements proposed in the CoST IDS/OC4IDS review:

Climate objective (identification)

## Climate objective (identification) **Module:** Climate finance **Indicator:** Project theme ### Disclosure format > Disclose the main climate objective that the project addresses. > > Select from a list: > > Eg: > > * mitigation > * adaptation > * cross-cutting ### OC4IDS mapping > **Project level:** Add the relevant code from the climateChangeGoal codelist to the `environment.climateChangeGoals` array

I suggested incorporating a project's climate change objectives into a broader modelling of sustainability objectives based on the EU's Sustainable Finance Taxonomy, however CoST's consultant that proposed the climate finance data points advised against aligning with the EU taxonomy due to sensitives in other parts of the world.

Proposal

Add a field and codelist to disclose whether a project's climate change goals are mitigation, adaptation or both.

Add the following field to the environment object proposed in #393:

Path	Title	Description	Type (format)	Codelist
environment.goals	Environmental goals	The environmental goals pursued, from the closed environmentalGoal codelist.	Array	environmentalGoal

Add a environmentalGoal codelist with the following codes:

Codelist	Code	Title	Description
environmentalGoal	climateChangeMitigation	Climate change mitigation	Reduction of emissions or enhancement of the sinks of greenhouse gases.
environmentalGoal	climateChangeAdaptation	Climate change adaptation	Adjustment to actual or expected climate and its effects, in order to moderate harm or exploit beneficial opportunities.

Example

{
  "environment": {
    "goals": ["mitigation"]
  }
}

Sources

• OCDS Sustainability Extension - field names, titles and descripitons
• IPCC Glossary - code descriptions

cc @evelyndinora, @mgraca-prado

[odscjen]

@jpmckinney any comments or objections to this proposal?

[jpmckinney]

My only idea is to perhaps have a broader goals field, and then codes like 'climateChangeMitigation', so that we don't have to create xyzGoals fields in the future.

[mgraca-prado]

@duncandewhurst Just one point to clarify: I believe we can exclude the word 'identification' from the name of the data point (Climate objective (identification) I included this in the initial table only to clarify the stage of the project cycle it refers to.

[duncandewhurst]

My only idea is to perhaps have a broader goals field, and then codes like 'climateChangeMitigation', so that we don't have to create xyzGoals fields in the future.

Sounds good. I've updated the proposal.

@duncandewhurst Just one point to clarify: I believe we can exclude the word 'identification' from the name of the data point (Climate objective (identification) I included this in the initial table only to clarify the stage of the project cycle it refers to.

Sounds good. I see that you already updated the spreadsheet so we'll use the updated titles from there in the documentation :-)