Title: | Calculate Fetch and Wave Energy |
---|---|
Description: | Functions for calculating the fetch (length of open water distance along given directions) and estimating wave energy from wind and wave monitoring data. |
Authors: | Philippe Marchand [aut, cre], David Gill [aut] |
Maintainer: | Philippe Marchand <[email protected]> |
License: | GPL-3 |
Version: | 0.3.0 |
Built: | 2024-10-18 03:14:26 UTC |
Source: | https://github.com/pmarchand1/waver |
Given a point, a shoreline layer and a vector of wind directions (bearings),
fetch_len
calculates the distance from point to shore for each bearing.
fetch_len( p, bearings, shoreline, dmax, spread = 0, projected = FALSE, check_inputs = TRUE )
fetch_len( p, bearings, shoreline, dmax, spread = 0, projected = FALSE, check_inputs = TRUE )
p |
Simple feature (sf or sfc) object representing a single point. |
bearings |
Vector of bearings, in degrees. |
shoreline |
Simple feature (sf or sfc) object representing the shoreline, in either line or polygon format. |
dmax |
Maximum value of fetch length, returned if there is no land
within a distance of |
spread |
Vector of relative bearings (in degrees) for which to calculate fetch around each main bearing (see details). |
projected |
Deprecated argument, kept for backwards compatibility. |
check_inputs |
Should the validity of inputs be checked? It is recommended to keep this TRUE, unless this function is called repeatedly from another function that already checks inputs. |
The fetch length (or fetch) is the distance of open water over which the wind can blow in a specific direction. Note that bearings represent the direction from where the wind originates.
The optional spread
argument defines relative directions that are
added to each main bearing to produce a set of sub-bearings. The fetch lengths
calculated for each sub-bearing are averaged with weights proportional to
cos(spread)
. By default, spread = 0
and fetch length is
calculated for the main bearings only.
The input data can be in either geographic (long, lat) or projected coordinates,
but p
and shoreline
must share the same coordinate system. Distances
are calculated using the st_distance
function from the sf package
and expressed in the units of the coordinate system used, or in meters if using
geographic coordinates. For geographic coordinates, we recommend setting
sf_use_s2(FALSE)
, which results in st_distance
using the ellipsoid
distance calculation (requires the lwgeom package), instead of the less precise
spherical distance calculation. For projected coordinates, the Euclidean distance
is calculated.
If the shoreline layer is composed of polygons rather than lines, the function
verifies that the input point is outside all polygons (i.e. in water). If this is
not the case, it issues a warning and returns a vector of NA
.
A named vector representing the fetch length for each direction
given in bearings
.
fetch_len_multi
for an efficient alternative when
computing fetch length for multiple points.
pt <- st_sfc(st_point(c(0, 0)), crs = st_crs(4326)) # Shoreline is a rectangle from (-0.2, 0.25) to (0.3, 0.5) rect <- st_polygon(list(cbind(c(rep(-0.2, 2), rep(0.3, 2), -0.2), c(0.25, rep(0.3, 2), rep(0.25, 2))))) land <- st_sfc(rect, crs = st_crs(4326)) fetch_len(pt, bearings = c(0, 45, 225, 315), land, dmax = 50000, spread = c(-10, 0, 10))
pt <- st_sfc(st_point(c(0, 0)), crs = st_crs(4326)) # Shoreline is a rectangle from (-0.2, 0.25) to (0.3, 0.5) rect <- st_polygon(list(cbind(c(rep(-0.2, 2), rep(0.3, 2), -0.2), c(0.25, rep(0.3, 2), rep(0.25, 2))))) land <- st_sfc(rect, crs = st_crs(4326)) fetch_len(pt, bearings = c(0, 45, 225, 315), land, dmax = 50000, spread = c(-10, 0, 10))
fetch_len_multi
provides two methods to efficiently compute fetch length
for multiple points.
fetch_len_multi( pts, bearings, shoreline, dmax, spread = 0, method = "btree", projected = FALSE )
fetch_len_multi( pts, bearings, shoreline, dmax, spread = 0, method = "btree", projected = FALSE )
pts |
Simple features (sf or sfc) object containing point data. |
bearings |
Vector of bearings, in degrees. |
shoreline |
Simple feature (sf or sfc) object representing the shoreline, in either line or polygon format. |
dmax |
Maximum value of fetch length, returned if there is no land
within a distance of |
spread |
Vector of relative bearings (in degrees) for which to calculate fetch around each main bearing. |
method |
Whether to use the "btree" (default) or "clip" method. See below for more details. |
projected |
Deprecated argument, kept for backwards compatibility. |
With method = "btree"
(default), the fetch calculation for each point only uses
the geometries within the shoreline
layer that intersect with a rectangular
buffer of size dmax
around that point. (The name is based on a previous version
of the function that implemented this method using the gBinarySTRtreeQuery
function
from the rgeos package.)
With method = "clip"
, the shoreline
is clipped to its intersection
with a polygon formed by the union of all the individual points' rectangular buffers.
In both cases, fetch_len
is then applied to each point,
using only the necessary portion of the shoreline.
Generally, the "clip" method will produce the biggest time savings when
points are clustered within distances less than dmax
(so their
clipping rectangles overlap), whereas the "btree" method will be more
efficient when the shoreline is composed of multiple geometrical objects
and points are distant from each other.
A matrix of fetch lengths, with one row by point in pts
and
one column by bearing in bearings
.
fetch_len
for details on the fetch length computation.
Calculates the wave energy flux (power per meter of wave crest) given either (1) the significant wave height and peak period or (2) the wind speed at 10m, fetch length and (optionally) water depth.
wave_energy(height = NA, period = NA, wind = NA, fetch = NA, depth = NA)
wave_energy(height = NA, period = NA, wind = NA, fetch = NA, depth = NA)
height |
Significant wave height, in meters. |
period |
Peak wave period, in seconds. |
wind |
Wind speed at 10m, in m/s. |
fetch |
Fetch length, in meters. |
depth |
Water depth, in meters. |
Given the significant height (H) and peak period (T), the wave energy flux is calculated as:
,
where is the density of water (998 kg/m^3) and g is the
acceleration of gravity (9.81 m/s^2).
If both height
and period
are missing, they are estimated from
on the wind speed at 10m () and the fetch length (F) as
described in Resio et al. (2003):
(friction velocity)
If the depth (d) is specified, it imposes a limit on the peak period:
(in seconds)
Wave energy flux, in kW/m.
Resio, D.T., Bratos, S.M., and Thompson, E.F. (2003). Meteorology and Wave Climate, Chapter II-2. Coastal Engineering Manual. US Army Corps of Engineers, Washington DC, 72pp.
# With height and period arguments wave_energy(8, 1) # With wind, fetch and depth arguments (must be named) wave_energy(wind = 12, fetch = 15000, depth = 10)
# With height and period arguments wave_energy(8, 1) # With wind, fetch and depth arguments (must be named) wave_energy(wind = 12, fetch = 15000, depth = 10)