prep_general_inputs | R Documentation |
prep_general_inputs
loads and prepares input data that is common to all
scenarios to be evaluated, like existing infrastructure layers, relative
estimated undiscovered oil, and the land/water cost map.
prep_general_inputs(
rd.exist.file,
pad.exist.file,
oil.av.file,
cost.map.file,
d2cpf = 35000,
wd.loc,
path.in,
proj.info
)
rd.exist.file |
Character string specifying the file name for the shapefile depicting existing roads as lines. |
pad.exist.file |
Character string specifying the file name for the shapefile depicting existing central processing facility (CPF) and satellite pads as points. |
oil.av.file |
Character string specifying the file name for the relative estimated undiscovered oil raster. |
cost.map.file |
Character string specifying the file name for the cost map raster, which has all water areas coded as 0 and all land as 1. |
d2cpf |
Numeric value indicating the minimum allowed distance (m) between two central processing facilities (CPFs). Defaults to 35,000 m. |
wd.loc |
Character string identifying the base directory containing both input and output data folders. |
path.in |
Character string identifying the relative path from the base
directory ( |
proj.info |
Desired projection string in EPSG code format ( |
List containing input data used for infrastructure simulation across
all scenarios. This includes the land/water RasterLayer (cost_map
),
road resistance RasterLayer that makes development across water possible
(cost_water
), RasterLayer indicating relative estimated undiscovered
oil (oil_av
), RasterLayer depicting the infrastructure exclusion zone
around the Willow CPF (willow_cpf_ras
), SpatialPolygonsDataFrame of
existing CPF and satellite gravel pads (pad_exist
), SpatialLinesDataFrame
of existing roads (rd_exist
), data.frame with xy coordinates of existing
infrastructure (exist_coords
), and SpatialPointsDataFrame depicting
the Willow CPF location (willow_spdf
). Many of these feed into
prep_scenario_inputs
.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.