Skip to content

Commit

Permalink
render all
Browse files Browse the repository at this point in the history
  • Loading branch information
eroten committed Mar 26, 2024
1 parent 98b223f commit 77f47f3
Show file tree
Hide file tree
Showing 27 changed files with 677 additions and 745 deletions.
Binary file modified assets/captions/captions-cap-12.rds
Binary file not shown.
Binary file modified assets/captions/captions-cap-13.rds
Binary file not shown.
Binary file modified assets/captions/captions-cap-14.rds
Binary file not shown.
Binary file modified assets/captions/captions-cap-16.rds
Binary file not shown.
Binary file modified assets/captions/captions-cap-22.rds
Binary file not shown.
79 changes: 39 additions & 40 deletions docs/_energy/_energy.html

Large diffs are not rendered by default.

11 changes: 4 additions & 7 deletions docs/_energy/data_electricity.html
Original file line number Diff line number Diff line change
Expand Up @@ -313,7 +313,6 @@ <h2 id="toc-title">Table of contents</h2>
<ul class="collapse">
<li><a href="#minnesota" id="toc-minnesota" class="nav-link" data-scroll-target="#minnesota"><span class="header-section-number">2.1.1</span> Minnesota</a></li>
<li><a href="#wisconsin" id="toc-wisconsin" class="nav-link" data-scroll-target="#wisconsin"><span class="header-section-number">2.1.2</span> Wisconsin</a></li>
<li><a href="#data-dictionaries" id="toc-data-dictionaries" class="nav-link" data-scroll-target="#data-dictionaries"><span class="header-section-number">2.1.3</span> Data dictionaries</a></li>
</ul></li>
</ul>
<div class="toc-actions"><div><i class="bi bi-github"></i></div><div class="action-links"><p><a href="https://github.com/Metropolitan-Council/ghg-cprg/blob/main/_energy/data_electricity.qmd" class="toc-action">View source</a></p></div></div></nav>
Expand Down Expand Up @@ -342,22 +341,20 @@ <h1 class="title"><span class="chapter-number">2</span>&nbsp; <span class="chapt
<h2 data-number="2.1" class="anchored" data-anchor-id="utility-activity-data"><span class="header-section-number">2.1</span> Utility Activity Data</h2>
<section id="minnesota" class="level3" data-number="2.1.1">
<h3 data-number="2.1.1" class="anchored" data-anchor-id="minnesota"><span class="header-section-number">2.1.1</span> Minnesota</h3>
<p>Under Minnesota Administrative Rules Chapter 7610 <span class="citation" data-cites="mndocCHAPTER7610ENERGY2005">(<a href="../references.html#ref-mndocCHAPTER7610ENERGY2005" role="doc-biblioref">Minnesota Department of Commerce 2005</a>)</span>, utilities are required to file an annual data report that supports the identification of “emerging energy trends based on supply and demand, conservation and public health and safety factors, and to determine the level of statewide and service area needs.” <span class="citation" data-cites="minnesotadepartmentofcommerceAnnualReportingForms2022">(<a href="../references.html#ref-minnesotadepartmentofcommerceAnnualReportingForms2022" role="doc-biblioref">Minnesota Department of Commerce 2022</a>)</span> This includes a report of county-level energy deliveries (reported in megawatt-hours, commonly written as mWh). Because the information is structured in this manner, electricity emissions at the county-level can be estimated as a direct function of energy deliveries to counties reported by utilities.</p>
<p>One utility operating within our study area, Great River Energy (GRE), is a non-profit wholesale electric power cooperative which provides wholesale power and delivery services to 28 Minnesota-based electric cooperatives, which collectively own GRE and provide retail electric service. They are the primary supplier of energy (&gt;99%) to the cooperative utilities operating in our study area. Though most electricity suppliers with relationships with Minnesota electric utilities do not file these annual data reports, GRE does, given their unique hybrid wholesale/transmission structure and cooperative ownership model. As a result, while we keep only GRE’s reporting in our data collection for county-level electricity deliveries, we exclude reporting from these subsidiary retail electric cooperatives, in order to avoid double counting electric deliveries. We use GRE’s reported deliveries to our 9 Minnesota study area counties as a full substitution for the deliveries of these utilities, which may represent a marginal undercount given that marginal-to-negligible amounts of energy delivered by these retail cooperatives came from other other sources, per their annual reports.</p>
<p>Under Minnesota Administrative Rules Chapter 7610 <span class="citation" data-cites="mndocCHAPTER7610ENERGY2005">(<a href="../references.html#ref-mndocCHAPTER7610ENERGY2005" role="doc-biblioref">Minnesota Department of Commerce 2005</a>)</span>, utilities are required to file an annual data report that supports the identification of “emerging energy trends based on supply and demand, conservation and public health and safety factors, and to determine the level of statewide and service area needs” <span class="citation" data-cites="minnesotadepartmentofcommerceAnnualReportingForms2022">(<a href="../references.html#ref-minnesotadepartmentofcommerceAnnualReportingForms2022" role="doc-biblioref">Minnesota Department of Commerce 2022</a>)</span>. This includes a report of county-level energy deliveries (reported in megawatt-hours, commonly written as mWh). Because the information is structured in this manner, electricity emissions at the county-level can be estimated as a direct function of energy deliveries to counties reported by utilities.</p>
<p>One utility operating within our study area, Great River Energy (GRE), is a non-profit wholesale electric power cooperative which provides wholesale power and delivery services to 28 Minnesota-based electric cooperatives, which collectively own GRE and provide retail electric service. They are the primary supplier of energy (&gt;99%) to the cooperative utilities operating in our study area. Though most electricity suppliers having relationships with Minnesota electric utilities do not file these annual data reports, GRE does, given their unique hybrid wholesale/transmission structure and cooperative ownership model. As a result, while we keep only GRE’s reporting in our data collection for county-level electricity deliveries, we exclude reporting from these subsidiary retail electric cooperatives, in order to avoid double counting electric deliveries. We use GRE’s reported deliveries to our 9 Minnesota study area counties as a full substitution for the deliveries of these utilities, which may represent a marginal undercount given that marginal-to-negligible amounts of energy delivered by these retail cooperatives came from other other sources, per their annual reports.</p>
</section>
<section id="wisconsin" class="level3" data-number="2.1.2">
<h3 data-number="2.1.2" class="anchored" data-anchor-id="wisconsin"><span class="header-section-number">2.1.2</span> Wisconsin</h3>
<p>Under Wis. Stat. § 196.07, investor- and municipally-owned electric utilities operating within the state of Wisconsin must submit annual reports to the State which include an array of information related to utility finance and operations, including key figures leveraged in our data collection, such as total energy deliveries made (in units of <em>kWh</em>) and total number of customer accounts within each county <span class="citation" data-cites="wisconsinstatelegChapter196Regulation2024">(<a href="../references.html#ref-wisconsinstatelegChapter196Regulation2024" role="doc-biblioref">Wisconsin State Legislature 2024</a>)</span>.</p>
<p>Of the seven in-scope electric utilities, only three (the investor- and municipally-owned utilities) were required to make these reports to the State in 2021 (four of the in-scope electric utilities are cooperative utilities); state data was leveraged in this case. For the four utilities (all cooperative utilities) not making these reports, we relied upon the detailed data files provided by the EIA, recording the responses of utilities to the Annual Electric Power Energy Report (Form EIA-861), which records retail sales by utilities and power marketers <span class="citation" data-cites="eia861">(<a href="../references.html#ref-eia861" role="doc-biblioref">U.S. Energy Information Administration 2023</a>)</span>. Two utilities (Dunn Energy Cooperative and Polk-Burnett Electric Cooperative) filled the long version of the form (filled by larger entities), and two (St.&nbsp;Croix Electric Cooperative and Pierce-Pepin Electric Cooperative Services) filled the short form (filled by smaller entities). For our purposes, both the long and short form provided suitable activity information (total energy delivered, total customers) to allocate energy deliveries to counties in concert with Census population data, in the process outlined below.</p>
<p>Because Wisconsin utilities do not report energy deliveries at the county level , it was necessary to estimate energy deliveries by a given utility <em>i</em> within a particular county <em>j.</em> For those three utilities who reported county-level customer counts and total customer counts to the state, we estimated mWh delivered by utility <em>i</em> in county <em>j</em> by multiplying their total statewide energy deliveries (as reported to the relevant state authorities) by the proportion of their customers residing in each of our two study area counties.</p>
<p>Because Wisconsin utilities do not report energy deliveries at the county level, it was necessary to estimate energy deliveries by a given utility <em>i</em> within a particular county <em>j.</em> For those three utilities who reported county-level customer counts and total customer counts to the state, we estimated mWh delivered by utility <em>i</em> in county <em>j</em> by multiplying their total statewide energy deliveries (as reported to the relevant state authorities) by the proportion of their customers residing in each of our two study area counties.</p>
<p><span class="math display">\[mWhDelivered_iCounty_j = (mWhEnergyDeliveries_i \times {ProportionOfTotalUtilityCustomers_j}) \]</span></p>
<p>Note: This approach implicitly assumes that customer accounts across counties within the operations of a given utility have the same average per-account demand for energy, when this is influenced by land-use mix and relative magnitude/scale of residential and commercial/industrial utility accounts within a given county.</p>
<p>To calculate the estimated energy delivered by utility <em>i</em> in county <em>j</em> for the four cooperatively-owned utilities that did not report county-level customer counts (i.e., did not report to the State), we used population figures to estimate/allocate reported electricity deliveries to counties. We took the actual total energy delivered by utility <em>i</em> across Wisconsin (as reported to the relevant federal authorities) and multiplied this by the proportion of total population within each utility’s entire service area residing within county <em>j</em> at the 2020 decennial Census.</p>
<p><span class="math display">\[mWhDelivered_iCounty_j = (mWhDelivered_i \times {ProportionOfTotalUtilityPopulation_j}) \]</span></p>
<p>The factor <em>ProportionOfTotalUtilityPopulation</em><sub>j</sub> was calculated by spatially joining Census block centroids containing population data to 1) polygons representing the entirety of our in-scope utilities’ service areas (including areas outside of St.&nbsp;Croix and Pierce counties) and 2) polygons representing only the portions of these utilities’ service areas within a) St.&nbsp;Croix county and b) Pierce County. These utility-county service areas are calculated separately, to facilitate an informed allocation of statewide energy use to each county in turn.</p>
</section>
<section id="data-dictionaries" class="level3" data-number="2.1.3">
<h3 data-number="2.1.3" class="anchored" data-anchor-id="data-dictionaries"><span class="header-section-number">2.1.3</span> Data dictionaries</h3>
<!-- ### Data dictionaries -->
<div style="page-break-after: always;"></div>


Expand Down
3 changes: 1 addition & 2 deletions docs/_energy/data_natural_gas.html
Original file line number Diff line number Diff line change
Expand Up @@ -341,13 +341,12 @@ <h1 class="title"><span class="chapter-number">3</span>&nbsp; <span class="chapt
<h2 data-number="3.1" class="anchored" data-anchor-id="utility-activity-data"><span class="header-section-number">3.1</span> Utility Activity Data</h2>
<section id="minnesota" class="level3" data-number="3.1.1">
<h3 data-number="3.1.1" class="anchored" data-anchor-id="minnesota"><span class="header-section-number">3.1.1</span> Minnesota</h3>
<p>Under Minnesota Administrative Rules Chapter 7610 <span class="citation" data-cites="mndocCHAPTER7610ENERGY2005">(<a href="../references.html#ref-mndocCHAPTER7610ENERGY2005" role="doc-biblioref">Minnesota Department of Commerce 2005</a>)</span>, utilities are required to file an annual data report that supports the identification of “emerging energy trends based on supply and demand, conservation and public health and safety factors, and to determine the level of statewide and service area needs.” <span class="citation" data-cites="minnesotadepartmentofcommerceAnnualReportingForms2022">(<a href="../references.html#ref-minnesotadepartmentofcommerceAnnualReportingForms2022" role="doc-biblioref">Minnesota Department of Commerce 2022</a>)</span> This includes a report of county-level energy deliveries (reported in thousand cubic feet, commonly written as mcf). Because the information is structured in this manner, natural gas emissions at the county-level can be estimated as a direct function of energy deliveries to counties reported by utilities, which isn’t the case in Wisconsin (some modeling and estimation is required in WI).</p>
<p>Under Minnesota Administrative Rules Chapter 7610 <span class="citation" data-cites="mndocCHAPTER7610ENERGY2005">(<a href="../references.html#ref-mndocCHAPTER7610ENERGY2005" role="doc-biblioref">Minnesota Department of Commerce 2005</a>)</span>, utilities are required to file an annual data report that supports the identification of “emerging energy trends based on supply and demand, conservation and public health and safety factors, and to determine the level of statewide and service area needs.” <span class="citation" data-cites="minnesotadepartmentofcommerceAnnualReportingForms2022">(<a href="../references.html#ref-minnesotadepartmentofcommerceAnnualReportingForms2022" role="doc-biblioref">Minnesota Department of Commerce 2022</a>)</span> This includes a report of county-level energy deliveries (reported in thousand cubic feet, commonly written as mcf). Because the information is structured in this manner, natural gas emissions at the county-level can be estimated as a direct function of energy deliveries to counties reported by utilities, which is not the case in Wisconsin (some modeling and estimation is required in WI).</p>
</section>
<section id="wisconsin" class="level3" data-number="3.1.2">
<h3 data-number="3.1.2" class="anchored" data-anchor-id="wisconsin"><span class="header-section-number">3.1.2</span> Wisconsin</h3>
<p>Under Wis. Stat. § 196.07, investor-owned natural gas utilities operating within the state of Wisconsin must submit annual reports to the State which include an array of information related to utility finance and operations, including key figures leveraged in our data collection, such as total energy deliveries made (in units of <em>therms</em>) and total number of customer accounts within each county <span class="citation" data-cites="wisconsinstatelegChapter196Regulation2024">(<a href="../references.html#ref-wisconsinstatelegChapter196Regulation2024" role="doc-biblioref">Wisconsin State Legislature 2024</a>)</span>. Because all four “in-scope” natural gas utilities in Wisconsin are investor-owned, we did not have to refer to federal sources or use population figures to estimate energy deliveries. We estimated county-wide emissions from natural gas in 2021 by first calculating the proportion of each utility customer accounts that were linked to either Pierce or St.&nbsp;Croix counties, and allocating that proportion of the utility’s total reported energy delivery to each county. This approach represents a divergence from our Minnesota process, which involves aggregating county-level numbers directly reported by utilities, and implicitly assumes that customer accounts across counties within the operations of a given utility have the same average per-account demand for energy, when in actuality this is likely impacted by land-use mix and relative magnitude/scale of residential and commercial/industrial utility accounts within a given county.</p>
<p><span class="math display">\[mcfDelivered_iCounty_j = (mcfEnergyDeliveries_i \times {ProportionOfTotalUtilityCustomers_j}) \]</span></p>
<p>Note: This approach implicitly assumes that customer accounts across counties within the operations of a given utility have the same average per-account demand for energy, when this is influenced by land-use mix and relative magnitude/scale of residential and commercial/industrial utility accounts within a given county.</p>
<div style="page-break-after: always;"></div>


Expand Down
Loading

0 comments on commit 77f47f3

Please sign in to comment.