Comments (15)
I think it'll be alright. olca_jsonld_writer has a way to generate sources already. I just need to find a clean way to add the sources in the yaml, so that they can be created in jsonld.
from electricitylci.
The upstream datasets should also have a documentation source that is perhaps separate if available
from electricitylci.
@jump2conclusionsmatt I started a metadata_fixes branch for working on these different issues with the metadata tag
from electricitylci.
Flagging this so we can make sure the upstream models use the same source. @dannyhage
We have sources for both coal and gas - but it might make sense to generate them (and their UUIDs) with the code instead.
from electricitylci.
Someone please correct me if I'm wrong, but there doesn't appear to be any examples for entering openLCA "sources" correct? The request is to add these? This might take some work - will need to structure the data correctly within process_metadata.yml and then correctly implement it within process_dictionary_writer.py.
If openLCA "sources" aren't needed, I tried to provide links to data sources within the metadata text.
from electricitylci.
I'm not familiar with a way to access sources within a process for the ipc. But it does look like you can create a source and add it to a json.
from electricitylci.
Sorry looks like I was wrong: http://greendelta.github.io/olca-schema/html/ProcessDocumentation.html
from electricitylci.
Alright - this has been started. See process_metadata.yml for an example source. Anyone have real strong feelings about this format? Seems fairly straightforward. There are some changes in process_dictionary_writer and olca_json_ld_writer as well. Hopefully the changes to _source don't break anything. It appears to not ever be used, more specifically, no processes ever have "publication" defined.
from electricitylci.
@jump2conclusionsmatt Looks great in process_metadata.yml. Ideally the publication field would only be used when it has the primary documentation to describe that particular process. It's probably more valuable than the Sources field which doesn't necessary suggest exactly how those Sources are used.
from electricitylci.
I added the rest of the sources. I was able to run ELCI without failures, so it seems okay. The one thing @WesIngwersen that I wanted to point out was the inclusion of the draft eLCI manuscript as a source. I know we had always intended to include documentation in the manuscript about some of these technologies that aren't well documented already (e.g., solar PV, wind). I don't know how you feel about that: (link to example)
from electricitylci.
@jump2conclusionsmatt Yes this is fine - we need to make sure we have documentation of the work somewhere and that was one intended source of it. I was hoping to get some more support to finish that..it is well on its way and hope we can find a way to complete it
from electricitylci.
Was this kept open because there aren't sources for the technologies or various mixes? I added the eLCI manuscript as the default source to cover this. The one exception that I thought there might be is the eGRID-based consumption mix. @bl-young - didn't Troy have a manuscript for this? Can you post that info here or add it to process_metadata.yaml?
from electricitylci.
I don't know what the preferred documentation would be but there are several publications in the works, I have been working with @TJTapajyoti to get the trading methodology submitted.
from electricitylci.
Similar to this, I would just mark it as in preparation and put today's years and an author list. Just to give people the idea that documentation is in works somewhere. If it changes down the line, we can just update the metadata. So I just need a working title and authors I guess.
from electricitylci.
@hottleta @jump2conclusionsmatt Closing this issue for now as Matt put a temp reference in for the Hottle trade methodology in this commit
from electricitylci.
Related Issues (20)
- Script used to format the solar inventory is not written to handle inputs
- FlowAmount column needs to be converted to float type to avoid error when performing groupby/aggregate
- Typo in conversion of water volume to mass HOT 2
- using joblib memory class to improve performance for duplicate function calls HOT 2
- Remove reliance on eGRID data
- FileNotFound Error on L53 of nuclear_upstream.py HOT 1
- Need to modify import_impacts to use new international file
- AttributeError: module 'olca' has no attribute 'ProcessRef' HOT 3
- Unused Argument found in generate regional grid loss function HOT 1
- Typo in upstream_dict.py
- Include list of eGRID/EIA plant IDs that are included in aggregate data
- ResolutionImpossible Error: lciafmt and electricitylci depend on different versions of fedelemflowlist HOT 3
- URLError during eia_trans_dist_download_extract in eia_trans_dist_grid_loss.py HOT 1
- Use of print statements within methods
- incorporate esupy for data storage
- inventory from industrial facilities HOT 1
- Use new authoritative EPA-EIA power generator x-walk in place of internal crosswalks
- NCR ID column name mismatch
- Update olca-ipc calls to use 0.12 HOT 3
- Update setup.py dependency list
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from electricitylci.