-
Notifications
You must be signed in to change notification settings - Fork 0
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
create estimations for treatment effects #101
Comments
Open question regarding disbursement data: I suppose ignoring payments back to the donor under the assumption that the loan/grant has not been utilized to the full extent but will be used to reduce the outststanding debt (Restmittelverwendung) |
Agree.we should not count that as negative @melvinhlwong since it is not taking resources away from the projects |
@Jo-Schie Thanks for the feedback. I have some issues calculating the disbursements per cell. I have a last step where I need to aggragate the cells over all disbursements of all BMZ projects. However, there are couple of cells that are unmatched. I think they may be related to some MARINE WDPA. If yes, I would like to drop them and have a clean collapse/aggregation of the data. Here is the list of WDPAID that cause some issues ' # WDPAID |
I checked. First observations: Ten areas are kicked out because they are either Unesco Biosphere Reserves or they do not have valid geometry information. They are filter out with this code in the very beginning of the script: wdpa_kfw <-
wdpa_kfw %>%
filter(DESIG_ENG != "UNESCO-MAB Biosphere Reserve") %>%
filter(STATUS != "Proposed") %>%
filter(GEOMETRY_TYPE != "POINT") checkin now on the others. |
okay. I also checked all of the rest. There are two reasons, why we do not have WDPA-IDs. First option: they are marine areas or areas on small islands. In that case, they were not part of the original grid, which was created using GADM admin country boundaries (which do not include all smaller islands because of the rather coarse spatial resolution). Second option: The areas are very small (smaller 1 sqkm or sometimes between 2-3 sqkm). In that case, the intersection did not attribute the WDPA ID properly. Why? Because i used centroids for intersection to speed up the intersection of 3 Mio Gridcells with about 400 KfW PAs. In case of very small PAs centroids sometimes fall out of PA and no intersection information is returned. Often small PA projects do not have a dedicated Forest Conservation Focus but rather foster environmental education or rehabilitation in urban areas etc. Take away: Both cases do not exert a considerable influence on results. Therefore, please just ignore them. |
I accidently closed this issue, although it embraces more then just the question you had @melvinhlwong |
@Jo-Schie Thanks a lot for the thorough examination! That is great and I will simply drop the unmerged WDPA for the reasons you mentioned above (Marine, no geometry, small islands, small areas below 3sqm (no have a dedicated Forest Conservation Focus but rather foster environmental education or rehabilitation in urban areas). Great explanation! I put this into in progeress since the table above is still work in progress |
Fyi @Jo-Schie @melvinhlwong as I won't be available next week: I have started to create a markdown file for the separate table mentioned above - see the 05 file in the analysis branch. Please note that I haven't had the chance to review the calculations. In particular, "total loss avoided" and "total emissions avoided" need to be reviewed, as I was unsure about the units of the our estimates. If you have time please review (and adjust, if necessary) the code in the Rmd file. |
awesome job. I will reviews |
New table should be
seperate table
The text was updated successfully, but these errors were encountered: