Ben Young (ERG)
Ben Young (ERG)
When importing into openLCA, I believe these flows get dropped just in the Flows folder:  Does this lack of categorization have ramifications elsewhere?
Yes, I agree it makes sense to embed those flow properties into the correct folder structure. By the way, did you modify them yourself for a different price year?
The [test for allocation method](https://github.com/GreenDelta/olca-ipc.py/blob/v2/tests/test_allocation.py) is no longer successful. It has not been updated with the latest changes to the module names, e.g.,: `import olca as ipc` `AttributeError: 'Result' object...
Current latest zenodo link: https://zenodo.org/doi/10.5281/zenodo.7400857
this has been pulled into develop for the next release (https://github.com/USEPA/useeior/commit/9eeb7724d61b9720993744a1e009e487db2fab9c) so if we decide this is not urgent we can close this PR
Will be integrated in v1.6, this commit is already on develop. Closing this PR
@WesIngwersen do you want me to also grab the 2012 Detail tables in the 2017 schema for standard model builds (Make and Use before redef, etc.)?
New action issue is a Warning due to `LazyDataCompression` need to explore further.
We could add this flow to the IPCC impact method? Or we could code flows with CO2e to have an impact assessment value of 1