openego / data_processing

(geo)data processing, database setup, data validation
GNU Affero General Public License v3.0
7 stars 5 forks source link

Missing metadata on CORINE Land Cover dataset subsets on OEP #364

Open EvaWie opened 4 years ago

EvaWie commented 4 years ago

Dear all, There are two subsets of the CORINE Land Cover 2012 dataset without metadata on the OpenEnergyPlatform. a) Filter b) Germany I could not find a script dealing with CORINE Land Cover data within the data_processing. Nevertheless, I was ask to address the issue here and hope you find a good solution. Thank you.

IlkaCu commented 4 years ago

I could not find a script dealing with CORINE Land Cover data within the data_processing.

That's correct, the data processing is not accessing these tables. And as I'm not familiar with this dataset, I can't give any further information. @Ludee: Can you help?

Ludee commented 4 years ago

I uploaded and processed the data in the beginning of open_eGo to validate and check OSM landuse. We decided to not use CORINE for egoDP because the spatial resolution is not high enough. There was no time for synthesis of the data. I created filters to reduce the data size for manual checks in QGIS.

I will have a look if I find the old scripts, must be somewhere.

Ludee commented 4 years ago

Stichprobensichtung: Datensatz umfasst im Vergleich zu OSM und Zensus nicht alle Siedlungsflächen, bsw. Orte mit drei vier Häusern. Datensatz umfasst außerdem mehr Versiegelungsflächen als vergleichbarer DLM Datensatz. Es sind keine Attribute hinterlegt (bsw. Eiwohnerdichte), Die bestehenden Polygone decken sich aber weitesgehend mit Angaben auf DLM/OSM.

Betrifft: Copernicus clc 2012 v 18 4 Quelle: http://redmine.iks.cs.ovgu.de/oe/projects/opendata/wiki/Copernicus_clc_2012_v_18_4

Ludee commented 4 years ago

https://github.com/openego/data_processing/blob/d0c2da7464e02af63edcab627dad934f757038c3/documentation/SQL%20Documentation/orig_geo_copernicus.sql

EvaWie commented 4 years ago

Thank you very much for your replies. If we want to keep all three datasets, the subsets should have metadata. As they are not used by the data processing, they could maybe be deleted, if they are not valuable for other projects. @Ludee can you please make a decision and implement the changes? Thanks a lot!