Skip to main content
zenodoopen

Spatio-temporal dynamics of attacks around deaths of wolves: A statistical assessment of lethal control efficiency in France

<h1>Description</h1> <p>This repository contains the supplementary materials (<em>Supplementary_information.pdf</em>, <em>Supplementary_figures.pdf</em>, <em>Supplementary_tables.pdf</em>) of the manuscript: "<strong>Spatio-temporal dynamics of attacks around deaths of wolves: A statistical assessment of lethal control efficiency in France</strong>". This repository also provides&nbsp;the R codes and datasets necessary to run the analyses described in the manuscript.&nbsp;</p> <h1>Datasets</h1> <p>We provide the spatially anonymized R datasets to respect confidentiality. Therefore, the preliminary preparation of the data is not provided in the public codes. These datasets, all geolocated and necessary to the analyses, are:</p> <ul> <li><em>Attack_sf.RData</em>: 19,302 analyzed wolf attacks on sheep &nbsp;<br>&nbsp; - ID: unique ID of the attack &nbsp;<br>&nbsp; - DATE: date of the attack &nbsp;<br>&nbsp; - PASTURE: the related pasture ID from "Pasture_sf" where the attack is located &nbsp;<br>&nbsp; - STATUS: column resulting from the preparation and the attribution of attacks to pastures (part 2.2.4 of the manuscript); not shown here to respect confidentiality &nbsp;</li> <li><em>Pasture_sf.RData</em>: 4987 analyzed pastures grazed by sheep &nbsp; &nbsp;<br>&nbsp; - ID: unique ID of the pasture &nbsp;<br>&nbsp; - CODE: Official code in the pastoral census &nbsp;<br>&nbsp; - FLOCK_SIZE: maximum annual number of sheep grazing in the pasture &nbsp;<br>&nbsp; - USED_MONTHS: months for which the pasture is grazed by sheep &nbsp;</li> <li><em>Removal_sf.RData</em>: &nbsp;232 analyzed single or multiple wolf removals &nbsp;&nbsp;<br>&nbsp; - ID: unique ID of the removal &nbsp;<br>&nbsp; - OVERLAP: are they single removal ("single" in the manuscript =&gt; "NO" here), or not ("multiple" in the manuscrit, here "SIMULTANEOUS" for removals occurring during the exact same operation or "NON-SIMULTANEOUS" if not). &nbsp;&nbsp;<br>&nbsp; - DATE_MIN: date of the single removal or date of the first removal of a group &nbsp;<br>&nbsp; - DATE_MAX: date of the single removal or date of the last removal of a group &nbsp;<br>&nbsp; - CLASS: administrative type of the removal according to definitions from 2.1 part of the manuscript &nbsp;<br>&nbsp; - SEX: sex of the removed wolves if known &nbsp;<br>&nbsp; - AGE: class age of the removed wolves if known &nbsp;<br>&nbsp; - BREEDER: breeding status of the removed female wolves, "Yes" for female breeder, "No" for female non-breeder. Males are "No" by default, when necropsied; dead individuals with NA were not found. &nbsp;&nbsp;<br>&nbsp; - SEASON: season of the removal, as defined in part 2.3.4 of the manuscript &nbsp;<br>&nbsp; - MASSIF: mountain range attributed to the removal, as defined in part 2.3.4 of the manuscript &nbsp;</li> <li><em>Mountain_range_buff_sf.RData</em>: one row for each mountain range, corresponding to the buffered mountain ranges where removal control events could be sampled, as defined in part 2.3.3 of the manuscript &nbsp;&nbsp;</li> <li><em>Area_to_exclude_sf.RData</em>: one row for each mountain range, corresponding to the area too close from other mountain ranges, terrestrial and maritime limits, where removal control events could not be sampled, as defined in part 2.3.3 of the manuscript&nbsp;</li> <li><em>Overlapping_removal_sf.RData</em> corresponds to the spatial dataset necessary to run the supplementary figures about overlapping removals (S9) &nbsp;</li> </ul> <p>You can also find the object called <em>Subset_lt.RData</em>, which gives the ID of removals for each dataset (single/multiple removals) or subsets of single removals. &nbsp;</p> <p>The other RData resulted from the analysis. How to read their names: &nbsp;</p> <ul> <li>First part: &nbsp; &nbsp;&nbsp;<br>&nbsp; - <em>Buffer</em>: they link the attacks to removals or of control events. &nbsp; &nbsp;<br>&nbsp; - <em>Kernel</em>: they give the results of the kernel density estimation (z), according to the spatial (y) and temporal (x) coordinates, for each dataset.<br>&nbsp; - <em>Int</em>: they give, for each distance and time, the total amount of attack intensities before (INT_BEF) and after (INT_AFT) the combined locations and days of removals or control events. 1 unit of distance = 50 meters, 1 unit of time = 1 day.<br>&nbsp; - <em>Trend</em>: they give, for each distance and time, the trends in % of the attack intensities when comparing before and after, with their uncertainties and significance. Files with&nbsp;<em>spatshift</em>&nbsp;are designed for figures about spatial shift (unnested scales), contrary to files without&nbsp;<em>spatshift</em>&nbsp;(nested scales). &nbsp;</li> <li>Middle parts: (noted with an X after) &nbsp; &nbsp;<br>&nbsp; - <em>obs</em>: results from removals &nbsp;<br>&nbsp; - <em>jack</em>: results from jackknife samples of the removals&nbsp;<br>&nbsp; - <em>ctl</em>: results related to control sets &nbsp;<br>&nbsp; - <em>cor</em>: results corrected for livestock presence<br>&nbsp; - <em>raw</em>: results uncorrected for livestock presence<br>&nbsp; - <em>sim</em>: results for simulated attacks according to livestock presence &nbsp;</li> </ul> <p>Lengths of lists or sublists correspond to: &nbsp;</p> <p>- 20 elements: the two main datasets (single/multiple) and the 18 subsets of single removals.&nbsp;<br>- 100 elements: the 100 control sets. &nbsp; &nbsp;<br>- 1000 elements: the 1000 simulations of attacks (for the livestock presence correction). &nbsp;&nbsp;<br>- Other lengths and&nbsp;<em>jack</em>&nbsp;within the name: the jackknife samples. &nbsp; &nbsp; &nbsp;</p> <h1>Structure of the repository</h1> <h2><strong>Code 1</strong>: file&nbsp;<em>Buffer.R</em>&nbsp; &nbsp; &nbsp;&nbsp;</h2> <p>We keep only removals within geographic zones for the analysis (<em>Removal_analyzed_sf</em>), and sample their control events (100 simulations = control sets, <em>Removal_ctl_sf_lt</em>).</p> <p>We start by delimiting the spatio-temporal buffer for each row of the removal and control datasets. &nbsp;&nbsp;<br>&nbsp; &nbsp; - We identify the attacks from <em>Attack_sf.RData</em> within each buffer, thanks to the function <em>Buffer_fn</em>, giving the data frames&nbsp;<em>Buffer_X_df</em>&nbsp;(one row per attack) &nbsp;<br>&nbsp; &nbsp; - We select the pastures from <em>Pasture_sf.RData</em> within each buffer, thanks to the function <em>Buffer_pasture_fn</em>, giving the data frames&nbsp;<em>Buffer_X_sf</em>&nbsp;(one row per removal or control event) &nbsp;</p> <p>We calculate the spatial correction:&nbsp;&nbsp;<br>&nbsp; &nbsp; - We spatially slice each buffer into 200 rings with the function <em>Ring_fn</em>, giving the data frame&nbsp;<em>Ring_sf</em>&nbsp;(one row per ring) &nbsp;<br>&nbsp; &nbsp; - We add the total pastoral area of the ring of the attack ("SPATIAL_WEIGHT") with the function <em>Spatial_correction_fn</em>, for each attack of each buffer, within <em>Buffer_X_df</em> &nbsp;&nbsp;</p> <p>We calculate the pastoral correction:&nbsp;&nbsp;<br>&nbsp; &nbsp; - We create the pastoral matrix for each removal or control event with the function <em>Pastoral_matrix_fn</em>, giving a matrix of 200 rows (one for each ring) and 180 columns (one for each day, 90 days before the removal date and 90 day after the removal date), with the total pastoral area in use by sheep for each corresponding cell of the matrix (one element per removal,&nbsp;<em>Pastoral_X_mx_lt.RData</em>) &nbsp;<br>&nbsp; &nbsp; - We simulate, for each removal or control event, the random distribution of the attacks from <em>Buffer_X_df.RData</em> according to <em>Pastoral_X_mx_lt.RData</em>&nbsp;with the function&nbsp;<em>Buffer_sim_fn</em>. The process is done 1000 times (one element per simulation,&nbsp;<em>Buffer_X_sim_lt.RData</em>). &nbsp;&nbsp;</p> <h2>Code 2: file <em>Kernel.R</em> where we estimate the attack intensities &nbsp;</h2> <p>We classified the removals into 2 main datasets and 18 subsets, according to part 2.3.4 of the manuscript (<em>Subset_lt.RData</em>) (one element per set).<br>We compute the jackknife samples for each dataset or subset (<em>Removal_id_jack_lt</em>). &nbsp;<br>We perform the kernel estimations with the function&nbsp;<em>Kernel_fn</em>&nbsp;(<em>Kernel_X_lt</em>). &nbsp;<br>We sum the intensities of attacks before and after the removals or control events, with the function&nbsp;<em>Intensity_fn</em>, giving&nbsp;<em>Int_X_df_lt.RData</em>. &nbsp;&nbsp;</p> <h2>Code 3: file <em>Trend.R</em> where we calculate the trends of attack intensities after removals&nbsp;</h2> <p>&nbsp;We focus on the nested trends first:&nbsp;&nbsp;<br>&nbsp; &nbsp; - We calculate them (<em>Trend_X_df</em>) with function <em>Trend_fn&nbsp;</em><br>&nbsp; &nbsp; - We set the result significance test by observing the overlapping of confidence intervals of removals and control sets (<em>Trend_X_comparison_df</em>) &nbsp;</p> <p>We focus on the spatial shifts (trends for each specific distance):<br>&nbsp; &nbsp; - We calculate them (<em>Trend_X_spatshift_df</em>) with function&nbsp;<em>Trend_fn</em> &nbsp;<br>&nbsp; &nbsp; - We set the result significance test by observing the overlapping of confidence intervals of removals and control sets (<em>Trend_X_comparison_spatshift_df</em>) &nbsp;</p> <h2>- Code 4: file <em>Functions.R</em> where can be found all custom functions called in the other analysis codes &nbsp;&nbsp;</h2> <h2>- Code 5: file <em>Figures.R</em> produces part of the figures from the manuscript</h2> <p>Detailed comments are included in each code.</p> <h1>Support</h1> <p>If you have any question or request, do not hesitate to contact us at: oksana.grente@gmail.com</p> <h1>Authors and acknowledgment</h1> <p>Grente Oksana (CEFE, CNRS), Opitz Thomas (INRAE), Duchamp Christophe (OFB), Drouet-Hoguet Nolwenn (OFB), Chamaill&eacute;-Jammes Simon (CEFE, CNRS) and Gimenez Olivier (CEFE, CNRS). &nbsp;</p> <h1>License</h1> <p>GNU GENERAL PUBLIC LICENSE 3.0</p> <p>&nbsp;</p>

ShareScore

36/100

Overall dataset sharing score

Score breakdown

These five areas show where the dataset supports — or may limit — practical reuse.

Stewardship
8
Harmonization
4
Access
16
Reuse readiness
8
Engagement
0

Topics

ScienceDex for faculty

Your academic CV and NIH biosketch

Make your CV in your school's format and your NIH biosketch from it, then download both as Word files.