Empty geometries and NAs in WDPAID - supported PAs about mapme.protectedareas HOT 4 CLOSED

HI @Ohm-Np . I fixed all the issues. IT took me quite a while. that was really a pain. As for your last comment

"In mapme.forest package, if there are duplicate rows, then the saved raster file gets overwritten when polygons are passed individually and when passed as a big polygon, it throws error (no unique values)"

-> there are still duplicate WDPAIDs in the data. This is if a protected area has somehow two polygons that are listed spereatly. IF you use the WDPA_PID however, they are all unique. So that might fix the Global Forest Watch problem right?

Please see my most recent push to main to obtain the new data.

Please also note that I just save one polygonset now called data/wdpa_kfw_spatial_latinamerica_2021-04-22_allPAs.gpkg. In this dataset are all PAs and we can filter the KfW areas out later. It does not make too much sense to each time process both of them. so for the bigdata analysis it is enought to just process this file.

Please confirm if it works and if so you may close the issue.

from mapme.protectedareas.

I tried with the new gpkg and while running the script, it still says Data in column WDPA_PID does not uniquley identify observations.

First I thought that the problem might be, there were NA values in WDPA_PID of few WDPAIDs namely:
900715, 903013, 903016, 26621, 67744 & 900668. I then removed only those rows and run the script, still there was same error.

I then noticed that there are still two polygons with same WDPAID and WDPA_PID: 10903.


So, I think we should:

• replace NAs with respective WDPAIDs for 900715, 903013, 903016, 26621, 67744 & 900668
• set WDPA_PID as 10903_A and 10903_B respectively for duplicate ones

from mapme.protectedareas.

I have figured out the problem. I guess that now everything should run totally smooth. There should be no empty polygons anymore and no NAs in PID. Also, all PIDs should be unique. Could you check from main please? Also I created buffers which I would like to process as well (later). If everything runs smoothly you can close the issue...

from mapme.protectedareas.

That's great. It works fine now.
I will close this issue here.

from mapme.protectedareas.