0 votes
663 views

Dear All, 

 We have imported EF 3.0 and EF 3.1 LCI datasets and IA methods into OpenLCA -ILCD format from the hubs where they are downloadable from. 

It seems there is a bug with the water flows inside the LCI as well as inside de impact assesment methods: the flow “water” is repeated several times. It comes from the fact that instead of being different with different ID, they are within the same output list the same with the same ID, repeated in a series of the same flow. Therefore, the sum of water consumption taken into account in the method is wrong.

It looks like a bad translation of different flow, or maybe it comes from the original XMLs. I have not idea what it could be due to. But I would be very gratefull to you if you have any clue about this. 

Another remark : the impact assessment is named “other” rather than “AWARE” in 3.0

Best regards, 

Jean-Michel 

in openLCA by (160 points)

1 Answer

+1 vote
by (116k points)
Well the EF3.1 is not available yet from us in Nexus; the use of locations in exchanges in the ILCD format, as is used in these EF3.1 datasets, works only with openLCA 2. In openLCA 1.x, you get the same flow repeated, and you will need to use the "PEFlocus" tool from us to fix that, basically to create one new flow with a location, for each occurance of an exchange with a location, which is not very elegant but works (check https://github.com/msrocka/peflocus). We will release these datasets soon though (but, because of the way this is organised by the commission, this is basically unpaid work for us since we cannot charge for it due to the license conditions, and the commission does not support us either, and thus we need to find the time for this. And we need to visit all the different nodes to collect the datasets, where every node operator can just update or remove the datasets. In earlier versions, datasets were quite inconsistent, which required some cleaning and curation steps from us, but I hope this is now better).
by (130 points)
Hello, interested in the follow up of this issue. Thank you OpenLCA team :)
...