Important
On June 26 2024, Linux Foundation announced the merger of its financial services umbrella, the Fintech Open Source Foundation (FINOS), with OS-Climate, an open source community dedicated to building data technologies, modeling, and analytic tools that will drive global capital flows into climate change mitigation and resilience; OS-Climate projects are in the process of transitioning to the FINOS governance framework; read more on finos.org/press/finos-join-forces-os-open-source-climate-sustainability-esg
Physical climate risk calculation engine.
An OS-Climate project, physrisk is a library for assessing the physical effects of climate change and thereby the potential benefit of measures to improve resilience.
An introduction and methodology can be found in the online documentation.
Physrisk is primarily designed to run 'bottom-up' calculations that model the impact of climate hazards on large numbers of individual assets (including natural) and operations. These calculations can be used to assess financial risks or socio-economic impacts. To do this physrisk collects:
- hazard indicators and
- models of vulnerability of assets/operations to hazards.
Hazard indicators are on-boarded from public resources or inferred from climate projections, e.g. from CMIP or CORDEX data sets. Indicators are created from code in the hazard repository to make calculations as transparent as possible.
Physrisk is also designed to be a hosted, e.g. to provide on-demand calculations. physrisk-api and physrisk-ui provide an example API and user interface. A development version of the UI is hosted by OS-Climate.
The library can be run locally. The library is installed via:
pip install physrisk-libHazard indicator data is freely available via the Amazon Sustainability Data Initiative, here. Information about the project is available via the community-hub.
An inventory of the hazard data is maintained in the hazard inventory (this is used by the physrisk library itself). The UI hazard viewer is a convenient way to browse data sets.
A good place to start is the Getting Started section in the documentation site which has a number of walk-throughs.