CODEBOOK

The Geocoded Peacekeeping Operations (Geo-PKO) Dataset

Dataset Version 1.2 January 2020

1

Introduction

Geo-PKO v.1.2. extens the temporal coverage of the Geo-PKO to 2018 and includes 551 maps in total. Dataset covers sub-national deployments of all peacekeeping missions in the context of internal conflicts/wars and a few special political and peacebuilding missions (BINUB, UNOISIL, UNIPSIL) to Africa from 1994 to 2018. In total, it covers 27 missions in 15 countries. Depending on the purpose of the analysis, users of the data should determine if they should include or exclude these peacebuilding missions.

Current version of Geo-PKO dataset also excludes three peacekeeping missions, UNOMUR, UNASOG, and UNMEE, that were deployed in the context of interstate conflicts/wars and militarized disputes during 1994 and 2018 to Africa. The next iteration of the dataset will include missions deployed in the context of interstate conflicts. Furthermore, the next iteration of the dataset will expand the geographical coverage to include all peacekeeping missions globally through 2018. The process of updating the geographical coverage is underway, please contact the authors to access the most recent version.

2

List of missions covered by Geo-PKO v.1.2 Abbreviation Full mission name Main location BINUB United Nations Integrated Office in Burundi Burundi MINUCI United Nations Operation in Côte d’Ivoire Côte d’Ivoire MINURCA United Nations Mission in the Central African Central African Republic Republic MINURCAT United Nations Mission in the Central African Central African Republic Republic and Chad and Chad MINURSO United Nations Mission for the Referendum in Western Sahara Western Sahara MINUSCA United Nations Multidimensional Integrated Central African Republic Stabilization Mission in the Central African Republic MINUSMA United Nations Multidimensional Integrated Mali Stabilization Mission in Mali MONUA United Nations Observer Mission in Angola Angola MONUC United Nations Organization Mission in the Democratic Republic of Democratic Republic of the Congo the Congo MONUSCO United Nations Organization Stabilization Mission Democratic Republic of in the Democratic Republic of Congo the Congo ONUB United Nations Operation in Burundi Burundi ONUMOZ United Nations Operation in Mozambique Mozambique UNAMID African Union/United Nations Hybrid Operation Sudan in Darfur UNAMIR United Nations Assistance Mission for Rwanda Rwanda UNAMSIL United Nations Mission in Sierra Leone Sierra Leone UNAVEM II United Nations Angola Verification Mission II Angola UNAVEM III United Nations Angola Verification Mission III Angola UNIOSIL United Nations Integrated Office in Sierra Leone Sierra Leone UNIPSIL United Nations Integrated Peacebuilding Office in Sierra Leone Sierra Leone UNISFA United Nations Interim Security Force for Abyei Sudan UNMIL United Nations Mission in Liberia Liberia UNMIS United Nations Mission in the Sudan Sudan UNMISS United Nations Mission in the Republic of South South Sudan Sudan UNOCI United Nations Operation in Côte d’Ivoire Côte d’Ivoire UNOMIL United Nations Observer Mission in Liberia Liberia UNOMSIL United Nations Observer Mission in Sierra Leone Sierra Leone UNOSOM II United Nations Operation in Somalia II Somalia

3

General variables: Source “Source” indicates where the information was taken from. The main sources used are the deployment maps of the peacekeeping missions, obtained via the UN Library in New York. Those maps are referenced with map number and revision number. If other sources are used, this is clearly indicated here. For the sources concerning the geographical coordinates, see below.

Mission “Mission” gives the official abbreviation of the peacekeeping mission name.

Year / Month Those two variables give indication on the date (year/month) to which the row refers to.

Geographical variables Location This variable gives the name of the location (city, town, village) of the peacekeepers base, as indicated on the mission’s deployment maps. Note that “location” always refers to a specific place and not to a higher level administrative district (e.g. “New York” refers to New York City and not to New York State).

Geosplit In the rare situation where the source indicates several location-names for a specific deployment, the coding is split. This occurs typically in situations where troops are deployed to a main base and an outpost, yet the source does not specify how many troops are deployed to which location. The variable “Geosplit” is coded as 1 if a geosplit was done; and as 0 otherwise. In case of a Geosplit, the location-link is specified in the Geocomment. Further, this means that the total number for the variables “battalion”, “company”, “platoon”, “other”, “no troops”, “inf_no”, “FPU_no” and the “no troops per TCC” are divided by the amount of locations. In case of odd numbered troop strengths (“no troops”, “inf_no”, “FPU_no”, “no troops per TCC”), the resulting split person is fully assigned to one of the locations. E.g. 35 troops deployed to location A and B would be coded as 18 for location A and 17 for location B, rather than 17,5 for both locations. This does not apply for the unit deployment (“battalion”, “company”, “platoon”, “other”) which can be divided. Further note that the geosplit variable does not affect the troop type variables or the number and names of TCC or any other variable not specified above. Concretely, if an Infantry and an Engineering company are deployed by country X and Y to location “A and B”, they are split as follows: Rather than arbitrarily assign the infantry company deployed by X to one of the locations and the Engineering company from Y to the other, it is assumed that at both locations both troop types from both TCCs are present, it would hence be coded as 0,5 Infantry and 0,5 Engineering company from X and Y at both locations.

Country “Country” gives the English name of the country in which the location lies in. Note that the country is coded contemporary to the row’s time. E.g. Juba is coded as “Sudan” prior to South Sudan’s independence, and coded as “South Sudan” after.

4

Latitude/Longitude These two variables give the geographical coordinates of “location”. If not specified otherwise in the “geocomment”, the coordinates are taken from the National Geospatial- Intelligence Agency, and systematically cross-checked with Google Earth, the UCDP GED Point Dataset v.1.1. 2011 and the original source map. The format and system of the geocoding was done according to the rules and procedures of the Uppsala Conflict Data Program UCDP Georeferenced Event Dataset. (see: Sundberg Ralph, Lindgren Mathilda and Padskocimaite Ausra, 2010, “UCDP GED Codebook version 1.0-2011”.)

Geocomment A line used by the coder for a wide variety of comments regarding the coding of “location”, “geosplit”, “country”, “longitude” and “latitude” variables. Notably it is specified if other sources than the above mentioned standard sources where used, if several locations with the same name were found and, in such a case, how the coded location was chosen.

Zone de confidence This variable is only coded for UNOCI, in all other cases the variable is given as “NA”. The variable indicates whether the location lies within or on the border of the “Zone de Confidence” (coded as 1) or outside (0). The coding indicates “NA” for the times in which the Zone de Confidence ceased to exist (as of December 2007).

GWNO Country Code Gleditsch & Ward (gwno) country codes of the mission location. (Available at: http://ksgleditsch.com/statelist.html)

PRIO-GRID ID Grid cell id (gid) for each peacekeeping location from PRIO-GRID v.2.0. (Available at: http://grid.prio.org/)

Administrative Unit IDs First and second order administrative unit IDs and names for each peacekeeping location from Global Administrative Areas Database (GADM) v.3.6. (Available at: https://gadm.org/index.html)

Troop strengths variables Battalion / Company / Platoon / other / Comment on unit These variables indicated how many troop units of each size are deployed to the location. If there is another unit size than battalion, company or platoon, this is coded in the “other” variable, and specified in the “comment on unit”. Note that these variables only code troops, hence military observers, civilian police, security groups are not included. Further, it only codes the actual troops; hence Headquarters are also not included.

No troops “No troops” codes the estimated total number of troops present at the location. The estimate is made by multiplying the deployed units coded in “battalion”, “company”, “platoon”, “other” and “comment on unit” with their standard unit size. The standard unit size is based on NATO and UN standard military unit numbers, i.e. 650 troops per battalion, 150 troops per company,

5

35 troops per platoon, others as specified in the “comment on unit”. If there are troops present but none of the units have size symbol, it is coded as “unknown”.

RPF and RPF_No “RPF” is a dummy variable indicating the Regional Force Protection is present at the location (coded as 1), or not (coded as 0) (applicable to UNMISS starting September 2017). “RFP_No” gives the estimated troop strength of all troops in the Regional Force Protection present at the location, based on the same standard unit sizes applied above. Logically, if “RPF” is coded as 0, then “RPF_No” is set to 0, too, while if “RPF” is coded as 1, “RPF_No” has a value of at least 1. Number of RPF troops is not included in the total number of troops (No troops). Users can combine the two values (No troops and RPF_No), if they want to count these units in the total number.

RES and RES_No “RES” is a dummy variable indicating if at least one of the present units is a “Reserve unit” (coded as 1), or not (coded as 0). “RES_No” gives the estimated troop strength of all the RES troops present at the location, based on the same standard unit sizes applied above. Logically, if “RES” is coded as 0, then “RES_No” is set to 0, too, while if “RES” is coded as 1, “RES_No” has a value of at least 1. Number of reserve troops is also counted in the total number of troops (No troops). Users can subtract RES_No from No troops if they wish to exclude these units. Reserve units include RES (Reserve), FRB (Force Reserve Battalion), FRC (Force Reserve Company).

FP and FP_No “FP” is a dummy variable indicating if at least one of the present units is a force protection unit (coded as 1), or not (coded as 0). “FP_No” gives the estimated troop strength of all the force protection troops present at the location, based on the same standard unit sizes applied above. Logically, if “FP” is coded as 0, then “FP_No” is set to 0, too, while if “FP” is coded as 1, “FP_No” has a value of at least 1. Number of FP troops is also included in the total number of troops (No troops). Users can subtract FP_No from No troops if they wish to exclude these units. Force protection units include FP (Force protection), PSU (Protection and Support Unit), CCC (Combat Convoy Company).

TCC-variables No TCC This variable indicates the amount of “Troop Contributing Countries”, i.e. how many countries deployed troops to this location. Units for which the TCC are not known are not included in this variable. It is hence theoretically possible that “No TCC” is set to 0 even for locations to which troops are deployed to. Yet, cases for which the TCC is known, yet not the deployment strength for a given TCC, the TCC is included in “no TCC”.

Name of TCC1, No troops per TCC1 (*2, *3 etc) “Name of TCC1” lists the English name of the troop contributing country, while “no troops per TCC1” codes the estimated size of the troops deployed by a given TCC to the location. When there are several TCCs deploying to the same location, this information is given for all the TCCs separately. Note that only troops included in the “no troops” variable are included here, hence the sum of all the “No troops per TCC” variable for one location is equal to the “no troops” variable coded earlier.

6

Troops deployed to the location for which the TCC is unknown are coded as “unknown” for the TCC’s name, followed by the number of troops for which the TCC is not known. If the number of troops per TCC is not known, this is also coded as “unknown”.

Non-troops variables UNPOL and UNMO Those are two dummy variable containing information on the presence of UN civilian police (UNPOL) and UN Military Observers (UNMO). Their presence is coded as 1, while absence thereof are coded as 0. Note that for some missions, the sources specify that UNPOL or UNMO are not indicated. In such cases, the variable “UNPOL”/”UNMO” are given as NA.

HQ This variable contains information on whether the location serves as a Headquarter. If this is not the case, the variable is coded as 0. If the location serves as a TCC headquarter, the value is set to 1; if the location serves as the mission’s sector headquarter, the variable is coded as 2; if the location serves as the missions headquarter, the variable is coded as 3. If the location serves as different type of headquarters, the “highest” type of headquarter is coded. The reasoning to do so is that generally, locations serving as the mission headquarter are simultaneously also a sectorial headquarter, which are simultaneously also a TCC headquarter. It is noteworthy that for some missions or some time period of a given mission (typically in the beginning or end of a mission) there are no mission-sectors. Consequently, in those missions the variable “HQ” can only take the values 0, 1 or 3, yet not 2. Equally, not all missions have TCC-HQs, resulting in a lack of the value 1.

LO This dummy variable indicates if the location also serves as a liaison office (1) or not (0). Note that those locations frequently are located outside the country in which the mission takes place and/or frequently only serve as liaison offices without presence of any additional troops.

JMCO This dummy variable indicates if the location hosts a “Joint Monitoring and Coordination Office”. JMCO’s are only applicable to UNMIS, and are hence coded as “NA” in the other missions. JMCO is tasked to coordinate the monitoring and verification of the ceasefire and peace agreements in southern Sudan.

Security Group This is a dummy variable coding the presence (1) or absence (0) of a “security group” at this location. Generally, the size of the security group is not indicated in the sources, if so, this information is included in the “comments”.

Comment-variables Comments This is used for all type of comments regarding the coding. Note that comments regarding the location and the georeferencing are included in the “Geocomment”, while comments on unit sizes are included in the “Comment on unit”.

7