commit

README.md

@@ -28,10 +28,9 @@ Value factors are multipliers whose purpose is to convert between companies' non
 
 ![alt text](images/4.png)
 
+---
 
-## Impact Accounting's 'Big Idea'
-
-![alt text](images/2.png)
+![alt text](images/section-breaks/3.png)
 
 
 Various global frameworks govern how companies practice accounting - the most important of which are IFRS and GAAP. These standard-setters do not (themselves) proscribe the mandate to use their methods. But their application is mandated by governments and multilaterals (who may wish to use them to standardise accounting practices within a geopolitical blog, for instance).
@@ -63,9 +62,9 @@ The argued benefits of this system:
 
 In essence, impact accounting attempts to shift the viewpoint through which companies are valued from the self-serving one (how much money did we make or lose) to a 'global' one (how much money did we make or lose - offset by the proxied total cost of our net impacts to society and planet). 
 
-## Why "Value Factors" Are Required
+---
 
-![alt text](images/3.jpg)
+![alt text](images/5.png)
 
 For impact accounting to evolve into a viable practice that could eventually succeed traditional accounting, it must be standardized on multiple levels. Standardization is needed both in its application and in the precise mathematical methods used to translate companies’ environmental and social impacts into monetary values. This translation allows such impacts to be compared directly—on a like-for-like basis—with established financial reporting standards. In effect, the process involves converting raw data about impacts into monetary terms.
 
@@ -92,8 +91,7 @@ Each methodology underlying these calculations is supported by a substantial bod
 
 ---
 
-
-## About This Derivative Dataset
+![alt text](images/6.png)
 
 In late 2024, the International Foundation for Valuing Impacts (IFVI) released the **Global Value Factors Database (GVFD)**. This pioneering dataset provides a framework for converting non-traditional impacts into financial terms, offering a new lens for evaluating global value creation. For the full scope, methodology, and theoretical underpinnings, I encourage readers to consult the official IFVI website and accompanying documentation.
 
@@ -101,11 +99,14 @@ This document presents an overview of my **independent refactoring effort**, und
 
 The dataset continues to be governed by IFVI’s terms of use, as set out in the original publication (available at [ifvi.org](https://ifvi.org)). My work here is based on the **first release** of the GVFD. Should IFVI publish subsequent versions, they supersede the dataset refactored in this project.
 
----
+![alt text](images/7.png)
+
+
+No substantive changes were made to IFVI’s data values or methodologies. However, I applied several light-touch edits to improve usability and consistency:
 
-## Refactoring Purpose and Approach
+### XLSM -> CSV, JSON
 
-The original GVFD was released as a single `.xlsm` (macro-enabled Excel) file. While suitable for exploratory work, this structure posed limitations for reproducible data workflows and programmatic use.
+The original GVFD was released as a single `.xlsm` (macro-enabled Excel) file.  
 
 My primary aim was to reformat the GVFD for **machine readability** and **workflow compatibility**, especially in contexts requiring:
 
@@ -120,25 +121,22 @@ To achieve this, the following steps were taken:
 3. Creation of **structured JSON files**, reflecting the data’s original hierarchical presentation.
 4. Production of **compact Parquet versions**, auto-generated via Hugging Face for efficient querying and storage.
 
----
-
-## Data Edits (Non-Substantive)
-
-No substantive changes were made to IFVI’s data values or methodologies. However, I applied several light-touch edits to improve usability and consistency:
 
-### 1. Country Standardization
+### ISO Alpha-2 Mapping For Geographic Entities
 
 * Country names as listed in the original dataset were mapped to **ISO Alpha-2 codes**.
 * Both the **original names** and their **ISO equivalents** are retained in the refactored dataset.
 * Non-sovereign entities (e.g., certain territories, U.S. states) without ISO codes were omitted.
 
-### 2. Currency Formatting
+### Currency Symbol Redaction
 
 * The GVFD values are denominated in **U.S. dollars**.
 * To preserve numeric integrity, I removed dollar signs (`$`) from all values.
 * Currency denomination is now recorded in the dataset’s **metadata and documentation** rather than embedded in each cell.
 
-### 3. Structure and Accessibility
+Note: some of the value factors are six decimal places. If ingesting this dataset into databases it is recommended to choose an appropriate decimal type.
+
+Structure and Accessibility
 
 * **JSON representations** preserve the original units and structure of the GVFD.
 * **Country-level JSONs** were generated to allow users to focus on all value factors within a single nation.
@@ -158,6 +156,8 @@ Each format is accompanied by metadata documenting units, denominations, and dat
 
 ## Dataset Access Links
 
+These links are to the roots of the refactored dataset on Hugging Face and are provided for ease of navigation and access:
+
 | Category | Description | Link |
 |----------|-------------|------|
 | **Root Directories** | | |
@@ -173,6 +173,8 @@ Each format is accompanied by metadata documenting units, denominations, and dat
 | Per Country | JSON data organized by country | [View](https://huggingface.co/datasets/danielrosehill/IFVI-Global-Value-Factors-Dataset-V2/tree/main/refactored/json/per-country) |
 | US States | JSON data for US states specifically | [View](https://huggingface.co/datasets/danielrosehill/IFVI-Global-Value-Factors-Dataset-V2/tree/main/refactored/json/per-country/us-states) |
 
+## Thanks, Credits
+
 The GVFD represents a milestone in the effort to measure and assign value to non-traditional impacts. My **Data Analysis Refactoring V2** initiative is intended to extend the usability of IFVI’s work by making the dataset friendlier for modern analysis pipelines.
 
 I am grateful to IFVI for granting permission to republish the data in this restructured form. Any inaccuracies or errors in the refactoring are solely my own.