Open bkuczenski opened 2 years ago
It is actually only "a few" flows that are not categorized:
[('015046c6-bae5-3f2c-9b6e-d2d693275b5a', 'Jobs'),
('2e21b0ba-5505-3a0e-a7ec-4cb04c031c70', 'Gross operating surplus'),
('946a7ad3-1042-3ded-8a7f-8368643372ac', 'Compensation of employees'),
('d9fe7de6-cf17-30f9-8863-d722dd839af7', 'Taxes on production and imports, less subsidies')]
Thanks for raising this @bkuczenski. Because they don't fit the elementary flows definition, they aren't part of the FEDEFL. And because they aren't product flows, they don't use the NAICS categories either. We welcome your suggestions on which categories to use.
cc @bl-young
When importing into openLCA, I believe these flows get dropped just in the Flows folder:
Does this lack of categorization have ramifications elsewhere?
The schema does suggest that it is not required. But since the flows are implicitly categorized (tagged, at least) as "ECONOMIC_FLOW", it improves reusability to make that categorization explicit. Note that there are a few other entities for which the omitted categorization "sticks out":
"Producer price" and "units of currency" both seem to be appropriately "Economic" entities
I will acknowledge that there is no clear procedure for altering OpenLCA's "reference" category list, e.g. to add an "economic flows" category that could be adopted and used by others.
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?
Under the OpenLCA schema, all objects should be categorized. Flows that are elementary have elementary categories; however, many flows are not categorized. See the following two examples, chosen at random from a recent build: