Create routine for Analyzing Copernicus Global Land Cover data about mapme.protectedareas HOT 14 CLOSED

by any chance. is there still this csv file somewhere? i wanted to send it now to DOPA people but I could not download it before...

Hi @Jo-Schie, I re-created the csv files and are stored in datalake as:
datalake/mapme.protectedareas/processing/dopa_rest/

from mapme.protectedareas.

HI @Ohm-Np . Can we close this issue? It seems to me that the routines are created and working, correct?

from mapme.protectedareas.

First we need to decide on which classes to use for our purpose. Brief overview of all the 23 classes in Copernicus Land Cover data listed here:

Further information can be found here.

from mapme.protectedareas.

Well I would guess we need all categories right? Or are there simplified ones? If not then we need the are of all classes per polygon area.

from mapme.protectedareas.

Yes, there are simplified ones too but only one raster can be downloaded at a time for one class. This discrete classification is the good one among them. They have currently gridded rasters (20*20) for years 2015 to 2019.

from mapme.protectedareas.

The routine to process area of different land cover classes for a single polygon using lc_classes:
Workflow

However, to process all Protected Area (PAs), we can simply get the results in long table format for a particular year by running a function lc_area_per_polygon.


Here is the script

from mapme.protectedareas.

Comparison of results with DOPA: 2015

For WDPAID: 2221

Also, for WDPAID: 34004

We see very big differences in some of the classes. Since, the raster files and even the area of polygon are same used by dopa and us, I don't know what could be the reason behind this much difference in the results.

Only thing I noticed something erroneus is that, when we match the area of polygon to the summation of the land cover classes area, in both cases(dopa & kfw), they are different, however, the one from dopa somehow is near to the polygon area. Might be the difference in adoption of CRS, still it doesn't justify the difference in area of particular land cover classes.

from mapme.protectedareas.

Hi @Ohm-Np. The comparison looks totally fine to me. I guess the differences are attributable to the polygon simplification that we apply. You can see the effects of this if you compare original wdpa data to the simplified ones. I think, nevertheless, that this is okay as long as we describe this in the end in the final documentation. Please keep the two tables also foe documentation purposes. Did you also check how many PAs could be identified from our dataset?

from mapme.protectedareas.

Did you also check how many PAs could be identified from our dataset?

I tried with the get_redlist_status and the result is:

Total number of polygons in our geopackage: 7495
Polygons whose data are found from DOPA: 2891

Now, I am trying with other functions too. I will update here the results.

Updates:

Regarding Ecoregion statistics from DOPA. They do not provide data on area of intersection between polygon and ecoregion rather generate variables (normalized indicator) on ecoregion label. So, it does not help us to make a comparison with the results from our script teow_intersection.

Variables to download:

• Land cover ESA
• land cover change percent ESA
• Country level normalized indicator
• Ecoregion level normalized indicator

from mapme.protectedareas.

Total KfW PA Polygons: 7495
Unique WDPAIDs: 7450

Comparing KfW PA polygons with DOPA Excel sheet

KfW WDPAIDs available in DOPA excel sheet: 2259
KfW WDPAIDs not available in DOPA: 5191

The CSV file containing the list of these 5191 polygons are stored in datalake as: datalake/mapme.protectedareas/processing/wdpa_kfw/polygons_in_kfw_not_in_dopa_excel.csv

Comparing KfW PA polygons with WDPAIDs from DOPA functions

wdpa_level_centroid
KfW WDPAIDs available: 5533
KfW WDPAIDs not available: 1917 [polygons_in_kfw_not_in_centroid.csv]

redlist
KfW WDPAIDs available: 2891
KfW WDPAIDs not available: 4559 [polygons_in_kfw_not_in_redlist.csv]

water_stats
KfW WDPAIDs available: 2823
KfW WDPAIDs not available: 4627 [polygons_in_kfw_not_in_water.csv]

land_cover
KfW WDPAIDs available: 2718
KfW WDPAIDs not available: 4732 [polygons_in_kfw_not_in_landcover.csv]

multiple_indicators
KfW WDPAIDs available: 2826
KfW WDPAIDs not available: 4624 [polygons_in_kfw_not_in_multiple.csv]

from mapme.protectedareas.

The CSV file containing the list of these 5191 polygons are stored in datalake as: datalake/mapme.protectedareas/processing/wdpa_kfw/polygons_in_kfw_not_in_dopa_excel.csv

by any chance. is there still this csv file somewhere? i wanted to send it now to DOPA people but I could not download it before...

from mapme.protectedareas.

by any chance. is there still this csv file somewhere? i wanted to send it now to DOPA people but I could not download it before...

Sadly, I don't have this csv now, but once the dopa variables are processed, I can re-create the files.

from mapme.protectedareas.

Thanks om!!!

from mapme.protectedareas.

Yes, we can close this issue already. Everything is up to date.

from mapme.protectedareas.