July 12, 2022 Dataset Open Access

Robin Lamboll; Joeri Rogelj; Carl-Friedrich Schleussner

MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nmm##2200000uu#4500</leader>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <controlfield tag="005">20221013164734.0</controlfield>
  <controlfield tag="001">6373278</controlfield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Imperial College</subfield>
    <subfield code="0">(orcid)0000-0003-2056-9061</subfield>
    <subfield code="a">Joeri Rogelj</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Climate Analytics</subfield>
    <subfield code="0">(orcid)0000-0001-8471-848X</subfield>
    <subfield code="a">Carl-Friedrich Schleussner</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">220723</subfield>
    <subfield code="z">md5:b2f7c241a2e3e39b076376d3ec878375</subfield>
    <subfield code="u">https://zenodo.org/record/6373278/files/all_emissions.csv</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">16820787</subfield>
    <subfield code="z">md5:68463215354f199a0a4e9e60cef91dfd</subfield>
    <subfield code="u">https://zenodo.org/record/6373278/files/fair_temperatures.7z</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">1261099513</subfield>
    <subfield code="z">md5:1858cc2740fbed47ba19a9a0833c2fe2</subfield>
    <subfield code="u">https://zenodo.org/record/6373278/files/tier_2_fair_temperatures.7z</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">20603819</subfield>
    <subfield code="z">md5:5aa613a5259d551a7ad516e886b08ef7</subfield>
    <subfield code="u">https://zenodo.org/record/6373278/files/Tier2_scenarios_emissions.csv</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2022-07-12</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire_data</subfield>
    <subfield code="o">oai:zenodo.org:6373278</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">Imperial College</subfield>
    <subfield code="0">(orcid)0000-0002-8410-037X</subfield>
    <subfield code="a">Robin Lamboll</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Scenario emissions and temperature data for PROVIDE project</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="c">101003687</subfield>
    <subfield code="a">Paris Agreement Overshooting – Reversibility, Climate Impacts and Adaptation Needs</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">https://creativecommons.org/licenses/by/4.0/legalcode</subfield>
    <subfield code="a">Creative Commons Attribution 4.0 International</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&lt;p&gt;Data for tier 1 and tier 2 PROVIDE scenarios.&amp;nbsp;&lt;/p&gt;

&lt;p&gt;Tier 1 scenarios are mostly&amp;nbsp;from integrated assessment models. Tier 2 scenarios are much more numerous and are kept in a separately zipped folder for temperatures and csv file for emissions data. The temperature folders contains the full FaIR output for scenarios entirely defined by emissions, plus summary information for all scenarios, including the scenarios defined by combinations of emissions and temperature trends.&amp;nbsp;&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;10 Tier 1 scenarios until 2100&lt;/li&gt;
	&lt;li&gt;15 Tier 1 scenarios defined until 2300, all of which are variations of the original 10&lt;/li&gt;
	&lt;li&gt;Many Tier 2 scenarios, aiming to completely tile reasonable emissions space parameterised with 4 variables&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;Several objectives of the PROVIDE project depend on a set of scenarios that can be modelled through either a &amp;lsquo;classical&amp;rsquo; forward-looking approach or by a novel approach that &amp;lsquo;reverses the impact chain&amp;rsquo;. These scenarios are also key elements for the integration of PROVIDE findings in the outward-looking stakeholder Dashboard of the project. Here we describe the set of scenarios that has been developed and will be used within PROVIDE. In total, PROVIDE explores &lt;strong&gt;three complementary approaches&lt;/strong&gt;:&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
	&lt;li&gt;&lt;em&gt;10 distinct tier 1 scenarios extending until 2100, mostly based on the existing literature, used for short-term assessments of impacts&lt;/em&gt;&lt;/li&gt;
	&lt;li&gt;&lt;em&gt;15 distinct tier 1 scenarios extending until 2300, based on different extensions of the 10 literature scenarios, used for assessing longer-run impacts and the geophysical impact of significant temperature overshoot&lt;/em&gt;&lt;/li&gt;
	&lt;li&gt;&lt;em&gt;~1350 distinct tier 2 scenarios, exploring several dimensions of emissions space systematically, such as CO&lt;sub&gt;2&lt;/sub&gt; net zero date and relative methane intensity. This is used to explore which scenarios are compatible with given climate outcomes. These scenarios can be used to reverse the traditional impact chain, going from acceptable climate risks to descriptions of acceptable emissions. &lt;/em&gt;&lt;/li&gt;
&lt;/ol&gt;</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">doi</subfield>
    <subfield code="i">isVersionOf</subfield>
    <subfield code="a">10.5281/zenodo.6373277</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.6373278</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">dataset</subfield>
  </datafield>
</record>