Closed gplssm closed 4 years ago
@nailend I've added some plotting functions in draw.py incl. plotting geodata, you may want to make use of parts...
@nailend Feel free to create a new branch from feature/#18-highlevel-results
for your tasks, cf. #26
nr. 1:
- shall this be accumulated values or specific for every district?
Aggregated values for ABW should be fine. Land use (Flächenbedarf) should be given per mun but this is part of #31. You may skip this for now.
- no costs for LCOE available yet... TODO
?
- rel CO2 emission to SQ: where do I get the SQ emissions from? isn't it a different scenario?
They result from the SQ analysis which should be done before. To allow for multiple scenarios, see #39.
- total area required or for each technology? == highlevel-results
Not sure what you mean here, I guess the land use again (see above, #31)
As we will update the table above successively, I added a column "Done?" to the table above to track your progress..
The params and numbers of abs.+rel. areas required by wind+pv will change when #57 is merged, the notebook need to be adjusted. I'll come back to you with some ideas+comments on what needs to be done @nailend .
Ok, some updates:
RES Landuse: 1 scenario
'Area required rel. PV ground XXX'
'Area required rel. wind XXX'
If the 3 barplots above fit smoothly into a single plot, go for it.
I saw that I didn't update the units dict in #57, I'll fix this.
RES Landuse: Scenario comparison (I'll add this to the list in #64)
Other Furthermore, I think it'd be good to have more general information on the scenario setting, e.g. visualization of the spatial mismatch between supply and demand, so 2 plots just prior to the reqd. areas
Does this make sense to you?
results_scns[scn_id]['results_t']["LCOE"]
zu finden