Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

there is no DP preprocessing BPMN documentation about wind potential table #347

Closed
gplssm opened this issue Mar 23, 2020 · 5 comments
Closed
Assignees

Comments

@gplssm
Copy link
Contributor

gplssm commented Mar 23, 2020

Please add a BPMN explaining how the table

  • supply.soethe_wind_potential_area

gets created.

@gplssm gplssm changed the title there is no DP preprocessing BPMN documentation about demand wind potential table there is no DP preprocessing BPMN documentation about wind potential table Mar 23, 2020
@IlkaCu
Copy link
Member

IlkaCu commented Mar 24, 2020

I guess you refer to this table: supply.vernetzen_wind_potential_area

@IlkaCu
Copy link
Member

IlkaCu commented Mar 24, 2020

The table supply.vernetzen_wind_potential_area was created in the project VerNetzen. Therefore we can treat it as an input table in our dataprocessing and in the corresponding BPMN documentation.

@gplssm
Copy link
Contributor Author

gplssm commented Mar 24, 2020

The table supply.vernetzen_wind_potential_area was created in the project VerNetzen. Therefore we can treat it as an input table in our dataprocessing and in the corresponding BPMN documentation.

True. But, i'd like to be able to run the pre-processing from scratch, see #339. Therefore, it would be great to realized one of these options:

  1. Run the vernetzen code as part of the DP pre-processing
  2. Save the supply.vernetzen_wind_potential_area data permanently somewhere else (i.e. Zenodo) and download and import via script from there

What do you think? Is (1) far from possible? Would option 2 be legally ok?

@IlkaCu
Copy link
Member

IlkaCu commented Mar 30, 2020

As we already discussed in one of our last web conferences (26 March 2020) I would propose making use of 'external' OEP tables as input data for the preprocessing.

@gplssm
Copy link
Contributor Author

gplssm commented Apr 1, 2020

👌 just as a safety measure and for easing the automization of the DP-pre, I saved the table as .shp (d33f844) and provided it downloadably. Furthermore, it was added to the DP-pre from scratch script (c80c3e4).

@gplssm gplssm assigned gplssm and unassigned IlkaCu Apr 10, 2020
IlkaCu added a commit that referenced this issue Apr 24, 2020
…pre-wind-potential-areas

Add BPMN for wind_potential_table data import
@IlkaCu IlkaCu closed this as completed Apr 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants