This issue documents the development of an approach to address cases where both the NEI and GHGRP provide data for the same combustion unit in a facility. Generally, the GHG emissions reported by the GHGRP and associated energy estimates are preferred to the GHG emissions reported by the NEI (energy estimates are derived from several types of combustion-related emissions), due to the GHGRP being solely focused on GHGs and the availability of supporting data to derive energy estimates.
However, there are instances where the GHGRP unit is an unknown type (i.e., is labeled as "OCS (other combustion source)") and the NEI provides disaggregation of this unit, as well as defined unit types and capacities (GHGRP reporting guidelines allow reporters to aggregate units if two or more units each has a maximum capacity of <250 MMBtu/hr [name is denoted GP-]; if flue gases from 2 or more units are combined in a common stack and if CEMS is used [name is denoted CS-\; or 2 or more units combust the same fuel, fed by a common supply line [name is denoted CP-]. See 40 C.F.R. § 98.36(b)(3) for specific language and details).
fied_compilation.py uses two methods to address these cases:
allocate_shared_ocs.py : allocates energy or GHG emissions from GHGRP OCS (other combustion source) units to units from NEI data based on matched registryID and fuelTypeStd pairs.
reconcile_shared_nonocs.py : chooses between GHGRP and NEI as the source of energy or GHG emissions for matched registryID and fuelTypeStd pairs.
Issue is determining how these two methods should appropriately select between data sources.
Approaches to explore:
[ ] Should reconcile_shared_nonocs.py match based on registryID, fuelTypeStd, and unitTypeStd?
This issue documents the development of an approach to address cases where both the NEI and GHGRP provide data for the same combustion unit in a facility. Generally, the GHG emissions reported by the GHGRP and associated energy estimates are preferred to the GHG emissions reported by the NEI (energy estimates are derived from several types of combustion-related emissions), due to the GHGRP being solely focused on GHGs and the availability of supporting data to derive energy estimates.
However, there are instances where the GHGRP unit is an unknown type (i.e., is labeled as "OCS (other combustion source)") and the NEI provides disaggregation of this unit, as well as defined unit types and capacities (GHGRP reporting guidelines allow reporters to aggregate units if two or more units each has a maximum capacity of <250 MMBtu/hr [name is denoted GP-]; if flue gases from 2 or more units are combined in a common stack and if CEMS is used [name is denoted CS-\; or 2 or more units combust the same fuel, fed by a common supply line [name is denoted CP-]. See 40 C.F.R. § 98.36(b)(3) for specific language and details).
fied_compilation.pyuses two methods to address these cases:allocate_shared_ocs.py: allocates energy or GHG emissions from GHGRP OCS (other combustion source) units to units from NEI data based on matched registryID and fuelTypeStd pairs.reconcile_shared_nonocs.py: chooses between GHGRP and NEI as the source of energy or GHG emissions for matched registryID and fuelTypeStd pairs.Issue is determining how these two methods should appropriately select between data sources.
Approaches to explore:
reconcile_shared_nonocs.pymatch based on registryID, fuelTypeStd, and unitTypeStd?