Estimate non-zero FlowAmounts when below source reporting threshold
matthewlchambers opened this issue · 6 comments
The Aircraft row is missing from a newly generated EPA_GHGI_T_3_14
FBA (year is 2016, if that matters).
Yes there are a few lingering issues in a handful of tables that i'm working through. Feel free to document any more that you see here.
I see that for 2016, that row is identified as being less than 0.05 MMT (specific value not given). Is that why it's excluded? If so, maybe there's a better way of handling that situation?
I see that for 2016, that row is identified as being less than 0.05 MMT (specific value not given). Is that why it's excluded? If so, maybe there's a better way of handling that situation?
Yep that would be it. I do think your update to add a new field for that makes sense. In the current GHGI branch its not yet implemented.
Renamed this issue to broaden the scope to the issue at heart of this example.. when a source provided no value but it is also not given as zero, such as a '+' or '-' symbol. This could be, for example, when it's less than the significant figures provided.
This is really something that needs to be implemented for each specific FBA. We have a few examples now where this is done:
EIA MECS:
flowsa/flowsa/data_source_scripts/EIA_MECS.py
Lines 426 to 432 in 0d44ae9
Census SAS:
flowsa/flowsa/data_source_scripts/Census_SAS.py
Lines 66 to 82 in c18da34
GHGI:
flowsa/flowsa/data_source_scripts/EPA_GHGI.py
Lines 441 to 460 in 56c6da4
The approach to handling of the suppressed data is then indicated in a FBS, for example this function for MECS:
flowsa/flowsa/data_source_scripts/EIA_MECS.py
Lines 437 to 458 in 0d44ae9
Going to close this issue as resolved knowing that this can be added to FBAs as they are updated.