Data Legends

There is also an Excel file with details and examples that may be helpul. The file is available here.

Input Data

Portfolio Data

Data field	Expected value	Explanation	Optional / required	comment
company_name	Text	Name of the company in your portfolio	Required	Used for output purposes only
company_id	Text	Identifier for the company in your portfolio, used to map target and fundamental data to the company	Required	You can use any unique company identifier, but must use the same identifier in all three input data files/tabs.
company_isin	Text	Identifier for the company in your portfolio, used to identify the company e.g. for SBTi status	Required, for portfolio coverage and temperature score.	The column is needed in the file even if data is missing
company_lei	Text	Legal Entity Identifier for the company in your portfolio, used identify the company e.g. for SBTi status	Required, for portfolio coverage and temperature score.	The column is needed in the file even if data is missing
investment_value	Monetary value	The monetary value invested in the company. Used for aggregation	Required	Make sure all values are in the same currency.
engagement_target	TRUE, FALSE or empty	Used for engagement analysis. When set to TRUE for a company it is possible to analyze what it would do for your portfolio temperature score if this company would set a 1.5 degree a well below 2C target.	Optional
user_fields	Text or dict {key: value}	It is possible to add additional fields to your portfolio data. These fields can be used to group companies by other categories than sectors, industries, regions and countries, e.g. market cap bucket, investment strategy, asset class, etc.	Optional	Plain text objects, eg. ‘Europe’, will be added in a column called ‘category’. If a python dictionary object is used, the key will be used as a column label eg. {‘portfolio’: ‘Europe FMCG’}

Fundamental Data

Data field	Expected value	Explanation	Optional / required	comment
company_name	Text	Name of the company in your portfolio	Optional
company_id	Text	Identifier for the company in your portfolio, used to map target and fundamental data to the company	Required	You can use any unique company identifier, but must use the same identifier in all three input data files/tabs.
isic	Text	Sector classification code for the company based on the International Standard Industrial Classification (https://siccode.com/page/what-is-an-isic-code). Used to map targets to the correct regression model. Should include at least the first two levels: Section and Division.	Required
country	Text	Country where the company has its headquarter. Used for analysis purposes only.	Optional
region	Text	Region where the company has its headquarter. Used for analysis purposes only. Can be continental or more granular.	Optional
industry_level_1-4	Text	Level 1 through 4 of the industry classification of the company. Used for analysis purposes only. Can be based on any industry classification system.	Optional
sector	Text	Sector of the company. Used for analysis purposes only. Can be based on any classification system.	Optional
ghg_s1	tCO2e	Reported year total GHG emissions for scope 1 for the company. Used to combine temperature scores for scope 1 + 2 and scope 3 to temperature score for scope 1 + 2 and 1 + 2 + 3. Required together with ghg_s3 when using all aggregation methods (except WATS)	Optional
ghg_s2	tCO2e	Reported year total GHG emissions for scope 2 for the company. Used to combine temperature scores for scope 1 + 2 and scope 3 to temperature score for scope 1 + 2 and 1 + 2 + 3. Required together with ghg_s3 when using all aggregation methods (except WATS)	Optional
ghg_s1s2	tCO2e	Use if GHG data for separate scopes is unavailable. Reported year total GHG emissions for scope 1+2 for the company. Used to combine temperature scores for scope 1 + 2 and scope 3 to temperature score for scope 1 + 2 + 3.	Optional	Kept from v1.0 for reasons of backward compatibility
ghg_s3	tCO2e	Reported year total GHG emissions for scope 3 for the company. Used to combine temperature scores for scope 1 + 2 and scope 3 to temperature score for scope 1 + 2 + 3. Required together with ghg_s1 and ghg_s2 in all aggregation methods (except WATS)	Optional
company_revenue	Monetary value	In single dollars / euros / …. (can be any currency you choose). Revenue of the company in the most recent year.	Required only if using aggregation method ROTS.	All values must be in the same currency.
company_market_cap	Monetary value	Market capitalization of the company in single dollars / euros / ….	Required only if using aggregation method MOTS.	All values must be in the same currency.
company_enterprise_value	Monetary value	Enterprise value of the company in single dollars / euros / ….	Required only if using aggregation method EOTS or ECOTS.	All values must be in the same currency.
company_total_assets	Monetary value	Total assets of the company in single dollars / euros / ….	Required only if using aggregation method AOTS.	All values must be in the same currency.
company_cash_equivalents	Monetary value	Cash equivalents of the company in single dollars / euros / … .	Required only if using aggregation method ECOTS.	All values must be in the same currency.
ghg_s3_i (i = 1 to 15)	tCO2e	Total GHG emissions for the different categories in scope 3 for the company. Used to combine multiple scope 3 targets into one temperature score.	Optiomal

Target Data

Data field	Expected value	Explanation	Optional / required	comment
company_name	Text	Name of the company in your portfolio	Optional
company_id	Text	Identifier for the company in your portfolio, used to map target and fundamental data to the company	Required	You can use any unique company identifier, but must use the same identifier in all three input data files/tabs.
target_type	Absolute, Int_to_abs, Intensity, T_score or Other	Type of target. Can be absolute or intensity based GHG emission reduction target. Can be a temp score from the CDP-WWF method. If intensity has been converted to absolute type must be entered as “Int_to_abs”	Required	If target_type is left empty the target will not be valid. If no other target is available for that time-frame and scope combination the company will be given a default score.
intensity_metric	Revenue, Product, Cement, Oil, Steel, Aluminum, Power or Other	The metric the intensity based GHG emission reduction target is based on. All intensity metrics must be mapped - literally - to on of these 8 categories. Used in target validation protocol and to map the target to the relevant regression model in the temperature score module.	Required for targets with target type “Intensity”. Can be left empty for other targets.	Note that “Power” refers to power generation
base_year_ts	A non negative decimal number	The base year temperature score calculated using the CDP-WWF temperature scoring method.	Required for target type “T_score”, otherwise optional	Note that Scope must be S3
end_year_ts	A non negative decimal number	The end year temperature score calculated using the CDP-WWF temperature scoring method.	Required for target type “T_score”, otherwise optional	Note that Scope must be S3
scope	S1, S2, S1+S2, S1+S2+S3, S3	The scope(s) covered by the target. All scope 3 targets, whether covering downstream, upstream or both must be mapped to S3.	Required	Targets without scope are not valid. If no target is available for a time-frame and scope combination the company will be given a default score.
s3_category	Integer number 1 - 15 (or empty)	The scope 3 category of the target.	Required if target is for particular scope 3 category.	If left out the target will be interpreted as a headline target.
coverage_s1	Number in decimals, between 0 and 1, e.g. 70% is denoted 0.7.	The part of emissions covered in scope 1 for the target. Used to determine the temperature score. For targets covering scope 1 and 2 specify the same coverage percentage in coverage_s1 and coverage_s2	Required for a target that covers scope 1
coverage_s2	Number in decimals, between 0 and 1, e.g. 70% is denoted 0.7.	The part of emissions covered in scope 2 for the target. Used to determine the temperature score. For targets covering scope 1 and 2 specify the same coverage percentage in coverage_s1 and coverage_s2.	Required for a target that covers scope 2
coverage_s3	Number in decimals, between 0 and 1, e.g. 70% is denoted 0.7.	The part of emissions covered in scope 3 for the target. Used to determine the temperature score. Note: this should be the coverage compare to the whole scope 3 emissions, so not just the part that is covered by the target.	Required for a target that covers scope 3
reduction_ambition	Number in decimals, between 0 and 1, e.g. 70% is denoted 0.7.	The emission reduction that is set as ambition in the target. Used to determine the temperature score.	Required
base_year	Year	Base year of the target. Used in the target validation protocol and to determine the time frame of the target.	Required
end_year	Year	End year of the target. Used in the target validation protocol and to determine the time frame of the target.	Required
start_year	Year	Year the target was announced. Used in the target validation protocol. If not specified, it will be assumed the start year is equal to the base year.	Optional
statement_date	Date in format YYYY-MM-DD (YYYY or YYYY-MM also accepted)	The date the target was confirmed or updated. Used in the target validation protocol. If not specified, the start year will be assumed.	Optional
base_year_ghg_s1	tCO2e	Total reported GHG emissions for scope 1 for the company at the base year of the target. Used when splitting combined scope targets to single scope targets	Required for scope 1 targets.
base_year_ghg_s2	tCO2e	Total reported GHG emissions for scope 2 for the company at the base year of the target. Used when splitting combined scope targets to single scope targets	Required for scope 2 targets.
base_year_ghg_s1s2	tCO2e	Total reported GHG emissions for scope 1+2 for the company at the base year of the target.	Optional
base_year_ghg_s3	tCO2e	Total reported GHG emissions for scope 3 for the company at the base year of the target.	Optional
achieved_reduction	Number between 0 and 1	Part of the reduction ambition of the target that is already achieved by the company. Used in the target validation protocol. Targets with achieved reduction of 1 are invalidated.	Optional. If not specified, assumed below 1
target_ids	String	Some data providers assign identifiers to targets. Enables tracking from target to company temp scores.	Optional.

Output data

Data field	Expected value	Explanation	From
achieved_reduction	Number between 0 and 1	Part of the reduction ambition of the target that is already achieved by the company. Used in the target validation protocol. Targets with achieved reduction of 1 are invalidated.	Target data
base_year	Year	Base year of the target. Used in the target validation protocol and to determine the time frame of the target.	Target data
base_year_ghg_s1	In tCO2e	Total GHG emissions for scope 1 for the company at the base year of the target.	Target data
base_year_ghg_s2	In tCO2e	Total GHG emissions for scope 2 for the company at the base year of the target.	Target data
base_year_ghg_s3	In tCO2e	Total GHG emissions for scope 3 for the company at the base year of the target.	Target data
company_id	text	Identifier for the company in your portfolio, used to map target and fundamental data to the company	Portfolio data
company_isin	text	Identifier for the company in your portfolio, used to get the SBTi status of the company (i.e. whether or not the company has a target approved by the SBTi)	Portfolio data
company_name	text	Name of the company in your portfolio	Portfolio data
coverage_s1	Number in decimals, between 0 and 1	The part of emissions covered in scope 1 for the target. Used to determine the temperature score.	Target data
coverage_s2	Number in decimals, between 0 and 1	The part of emissions covered in scope 2 for the target. Used to determine the temperature score.	Target data
coverage_s3	Number in decimals, between 0 and 1	The part of emissions covered in scope 3 for the target. Used to determine the temperature score.	Target data
end_year	Year	End year of the target. Used in the target validation protocol and to determine the time frame of the target.	Target data
Intensity_metric	Revenue, Product, Cement, Oil, Steel, Aluminum, Power Generation or Other	The metric the intensity based GHG emission reduction target is based on. All intensity metrics must be mapped to the eight categories in the column on the left. Used in target validation protocol and to map the target to the relevant regression model in the temperature score module.	Target data
Reduction_ambition	Number in decimals, between 0 and 1	The emission reduction that is set as ambition in the target. Used to determine the temperature score.	Target data
start_year	Year	Year the target was announced. Used in the target validation protocol. If not specified, it is assumed the start year is equal to the base year.	Target data
Target_type	Absolute, Intensity or Other	Type of target. Can be absolute or intensity based GHG emission reduction target. All targets that are not GHG emissions reduction targets can be mapped to Other. Used in the target validation protocol and to map the target to the relevant regression model in the temperature score module.	Target data
Time_frame	SHORT, MID or LONG	The targets are sorted by time frame.	Determined in tool
		SHORT: targets shorter than 5 years
		MID: targets between 5 and 15 years
		LONG: targets between 15 and 30 years.
ghg_s1s2	tCO2e	Total GHG emissions for scope 1 + 2 for the company. Used to combine temperature scores for scope 1 + 2 and scope 3 to temperature score for scope 1 + 2 + 3. Also used in combination with ghg_s3 in most aggregation methods (except WATS)	Fundamental data
ghg_s3	tCO2e	Total GHG emissions for scope 3 for the company. Used to combine temperature scores for scope 1 + 2 and scope 3 to temperature score for scope 1 + 2 + 3. Also used in combination with ghg_s3 in all aggregation methods, except WATS.	Fundamental data
sbti_validated	FALSE or TRUE	Returns true if the company has a SBTi-approved target.	SBTi data or fundamental data
Investment_value	Monetary value	The monetary value invested in the company.	Portfolio data
engagement_target	TRUE, FALSE or empty	Used for engagement analysis. When set to TRUE for a company it is possible to analyze what it would do for your portfolio temperature score if this company would set a (well below) 2 degrees target.	Portfolio data
ar6	text	The regression model used. This is determined based on the target type, ISIC, intensity_metric and scope. See [link to methodology doc, updated mapping section] for more detail	Output from the tool
Annual_reduction	Number in decimals, between 0 and 1	The annual reduction based on the reduction_ambition and the length of the target. Calculated as	Output from the tool
slope	Slope5, slope15, slope30	Used in determining the regression model to use to calculate the temperature score for a specific target based on its time frame.	Output from the tool
		Short-term targets: slope5
		Mid-term targets: slope15
		Long-term targets: slope30
samplesize	Number	The sample size used in the regression model. For model 4 this is 128. Not used in calculations. See https://github.com/CDPworldwide/TROPICS-regression/ for more detail about the regressions.	Regression model
model	Integer	The regression model used. This is model 4 by default. See https://github.com/CDPworldwide/TROPICS-regression/ for more detail about the regressions.	Regression model
variable	text	The regression scenario used to determine the temperature score of a target, for example	Regression model
		Emissions|Kyoto Gases
param	Number in decimals, between 0 and 1	The temperature score (TS) is calculated using linear regressions.	Regression model
intercept	Number in decimals, between 0 and 1	The temperature score (TS) is calculated using linear regressions.	Regression model
r2	Number in decimals, between 0 and 1	r2 represents the fit of the regression model on the data used to create the regressions. Not used in calculations.	Regression model
temperature_score	Number	The temperature score calculated for the combination of company, scope and time frame	Output from tool
temperature_results	Number in decimals, between 0 and 1	Represents the part of the score that is calculated using a valid target as defined by the target validation protocol vs. the part using the default score. For more detail, see [link to Chapter 2 of Methodology document]