complete reference list

[nesnoj]

Hey all,

I'm wondering whether we have an exhaustive reference list for the data used in DP? I'm aware of the BPMN and the table metadata, but it would require some work to join all the information..

[nesnoj]

Comments, anyone?

[ulfmueller]

I like the idea. I guess this list would be part of rtd, right? I just do not know when we find time for this. Do you want this very soon or can we start listing successively and find a deadline day which I would rather see in October?

[nesnoj]

I like the idea. I guess this list would be part of rtd, right?

Right.

I just do not know when we find time for this. Do you want this very soon or can we start listing successively and find a deadline day which I would rather see in October?

I think October would be fine but not later. Do your students have time to do this? If not, I'd try to assign this task to someone here..

Furthermore, we have to discuss the format. I'm fine with a plain list. But it'd be nice to have a format beyond a plain list which also includes information on where the data is used (e.g. linked to OEDB tables?).

[ulfmueller]

The only student right now working here is @birgits :wink:. I'm fine with a plain list. The linkage as a simple table could be obtained by going through the meta data.

[nesnoj]

:laughing:

Ok, I found someone who can start to work on this right now. More sources to be considered except metadata? I'm afraid that the metadata of some tables are incomplete..

[nesnoj]

One more thing: Do you prefer a ReST table or reference list? Examples here

[ulfmueller]

I'd say if you link it to tables/scripts a table otherwise a reference list...

[nesnoj]

Ok, @01lillyschoen09 will create a ReST reference list in the following format: [SourceYear] Source: Name, Year, License, Link

If you have comments on this, please reply fast..

[nesnoj]

@wolfbunke Could you please enable automatic creation (hook) of branch feature/readthedocs for RTD as it does not seem to be created automatically.. and I cannot build a new one on RTD.

[wolfbunke]

It doesn't create all Documentation automatically at the moment, therefore we (@IlkaCu ) turned it off. The reason is, that you need to run the build_script_doc.py script in https://github.com/openego/data_processing/blob/feature/readthedocs/documentation/build_script_doc.py in order to create the preprocessing and dataprocessing docs of the SQL header. Do you have a readthedocs account? Write me an email and I can add you to the DP readthedocs.

I just started a update/ new creation of the branch.

[wolfbunke]

Docu is updated except of the SQL script.

[nesnoj]

A first version can be found at RTD (source here). Thank you @01lillyschoen09 !

As you can see, some sources are missing. This is due to missing metadata in the eGo tables (the list was created from ego_* tables only).

A list I drafted some time ago which the current list could be updated with:

1. OpenStreetMap ( diverse Dinge, z.B. HS/MS-Trafos, Siedlungs-/Industrie-/...-Gebiete, ...)
2. Statistisches Bundesamt (z.B. Zensus 2011, GVA)
3. Statistische Landesämter
4. Länderarbeitskreis Energiebilanzen
5. BDEW (Lastprofile)
6. BKG (VG250, DLM250)
7. BfN (Schutzgebiete)
8. EE-Anlagedaten : https://www.netztransparenz.de/EEG/Anlagenstammdaten, BNetzA EE Anlagen Stammdaten Register, OpenPowerSystemsData
9. open_FRED (Wetterdaten vom Helmholtz-Zentrum Geesthacht – Zentrum für Material- und Küstenforschung)
10. open_eGo (Datenverschneidung, Methoden)
11. Weiteres, z.B. Annahmen zu Kabeltypen aus div. Quellen

I'd be great if someone could update the current list...

Or update the metadata and I might find someone who can do it..

[nesnoj]

Discontinued