dwp (version 1.1)

initLayout: Create a Data Structure or Map for the Site Layout

Description

Read plot layout data and perform premliminary error-checking and formatting. Search plot layout data can come in any of several different formats, including shape files for search area polygons and turbine locations, R polygons, (x, y) coordinates, or simple description of search plot type for each turbine (square, circular, road & pad). A vector of distances along with a search radius is also accommodated by dwp, but these can be directly processed in prepRing without preprocessing in initLayout.

Usage

initLayout(
  data_layout,
  dataType = "simple",
  unitCol = "turbine",
  file_turbine = NULL,
  radCol = "radius",
  shapeCol = "shape",
  padCol = "padrad",
  roadwidCol = "roadwidth",
  nRoadCol = "n_road",
  xCol = "x",
  yCol = "y",
  ncarcCol = "ncarc",
  scCol = NULL,
  notSearched = NULL,
  quiet = FALSE
)

Value

A list or data frame with components appropriate to the type of data imported. The data structure is returned as an S3 class object, which other functions in dwp can recognize and properly process. There is minimal processing on the data after importing, but the structures are lightly error-checked and formatted for more thorough processing, depending on data type and analysis objectives. Typically, the layout data will be later processed by a call to

prepRing to create a characterization of the searched area at the site by "rings", with tallies of searched area, search classes, and fraction of area searched in concentric, 1 meter rings around each turbine. The format of the output depends on the format of the input. There are several possibilities, including, each of which is an S3 object with characteristics specific to the imported data:

shapeLayout

List with elements:

• $layout = turbine search area configurations (polygons and multipolygons) from data_layout shape file as an sf object.

• $layoutAdj = polygons from $layout but recentered at (0, 0)

• $turbines = turbine data (as sf object)

• $unitCol = name of the column with turbine IDs (character string)

• $tset = turbine names (vector of character strings)

• $tcenter = locations of turbine centers (nturb by 2 array) with UTMs of turbine locations, extracted and simplified from $turbines. Column names are X and Y, measuring meters from a reference point. Row names are the names of the turbines.

simpleLayout

Data frame with columns:

• turbine = turbine IDs (syntactically valid R names)

• radius = search radius. If shape = "square", then radius is 1/2 the width of the square.

• shape = general descriptor of the shape of the search plot as "square", "circular", or "RP" (for roads and pads search).

• padrad = radius of the turbine pad (assumed circular)

• roadwidth = width of the access road(s)

• n_road = number of access roads

polygonLayout

List of polygons, one for each turbine. The maximum search radius at any turbine is assigned as an attribute (attr(, "rad")).

xyLayout

List with elements:

• xydat = data frame with columns for turbine names, x and y coordinates of 1m grid centers spanning the searched area, number of carcasses found in each grid cell, and optional covariates.

• tcenter = matrix giving turbine locations (x, y), with row names = turbine names.

• ncarc = vector giving the number of carcasses found at each turbine.

• unitCol = name of the column where turbine IDs are stored in xydat.

• tset = names of the searched turbines

Arguments

data_layout

Either the name of a shape file (polygons or multipolygons) that delineates areas searched at each turbine; a .csv file with R polygons, (x, y) coordinates, or simple descriptions of search parameters at each turbine; or a data frame with r polygons, (x, y) coordinates, or simple plot layout descriptions. See "Details" for details.

dataType

An identifier for the type of data to be imported: "shape", "polygon", "xy", or "simple". If data_layout is the name of a shape file, the dataType = "shape" identifier is optional.

unitCol

Column name for turbine IDs. If data_layout is the name of a shape file, then file_turbine must also be provided, giving turbine locations. The unitCol must be present in data_layout and in file_turbine (if provided). Turbine IDs in the unitCol must be syntactically valid R names (see Details below).

file_turbine

The name of a shape file (points) giving the turbine locations for turbines listed in the unitCol column in the data_layout if data_layout is a shape file. If dataType = "xy" and the grids in data_layout are all centered at (0, 0) with their turbines at the center, then file_turbine is not necessary and is ignored. Otherwise, if the grid coordinates are UTMs, file_turbine is either (1) a data frame with turbine names (in `unitCol`) and the location of turbines in `x` and `y`, or (2) the name of a .csv file with turbine locations (`unitCol`, `x`, and `y`). file_turbine is not required (and is ignored) for other data types.

radCol

for dataType = "simple" layouts: the name of the column in data_layout that gives the search radius for each turbine

shapeCol

for dataType = "simple" layouts: the name of the column in data_layout that gives the plot shape for each turbine.

padCol

for dataType = "simple" layouts: the name of the column in data_layout that gives the radius of the turbine pad

roadwidCol

for dataType = "simple" layouts: the name of the column in data_layout that gives the width of the turbine access road(s)

nRoadCol

for dataType = "simple" layouts: the name of the column in data_layout that gives the number of turbine access roads at each turbine

xCol

for dataType = "xy" or dataType = "polygon" layouts: the name of the column in data_layout that gives x coordinates on the grid (for dataType = "xy") or x coordinates of search area polygon (for dataType = "polygon")

yCol

for dataType = "xy" or dataType = "polygon" layouts: the name of the column in data_layout that gives y coordinates on the grid (for dataType = "yy") or y coordinates of search area polygon (for dataType = "polygon")

ncarcCol

for dataType = "xy" layouts: the name of the column with carcass counts in each grid cell. The column is required but may be all zeros with carcasses added from a matrix of carcass locations later

scCol

for dataType = "xy" layouts: the name of column in data_layout with names of search classes. This is used for excluding unsearched areas from the grid data (x, y). It is used ONLY with dataType = "xy" and used to remove rows with x[, scCol] == notSearched, where x is the search grid data frame.

notSearched

for dataType = "xy" layouts: the name(s) of search class(es) in scCol that are not searched (optional). Ignored for data types other than xy.

quiet

boolean for controlling whether progress of calculations and other notes are printed to the console as the function runs

Details

All the layout types (except for vector, which is addressed elsewhere) can accommodate patterns of seached and not searched areas. If the searched areas are subdivided into different search classes with different detection probabilities, then search plot layout data must be input either from shape files with non-intersecting polgons delineating the search classes or from x-y grid data. If there is more than one search class variable (for example, ground cover and search schedule), then the covariates may be entered in separate columns if the layout files give grid coordinates or may be combined into one column in the shape files. For example, ground visibility may be easy or difficult and search schedule may be 1-day or 14-day. These can be combined into a single column with values of, say, easy1, easy14, difficult1, and difficult14.

There must be a turbine ID column (unitCol) in each of the files. The individual turbine ID's must be syntactically valid R names, i.e., contain combinations of letters, numbers, dot ( . ), and underscores ( _ ) only and not begin with a number or a dot followed by a number. Other characters are not allowed: no spaces, hyphens, parentheses, etc.

If shape files are to be imported, both shape files (search area polygons and turbine locations) must have their three standard, mandatory component files (.shp, .shx, .dbf) stored in the same folder. Only the name of the .shp should be entered in the function call. Other components are automatically searched for and processed if available.

Examples

data(layout_simple)
# converts properly formatted dataframe to 'simpleLayout' object
initLayout(layout_simple) 

data(layout_xy)
initLayout(layout_xy, dataType = "xy")

data(layout_polygon)
initLayout(layout_polygon, dataType = "polygon", unitCol = "turbine")