LpiQcMissingPoints: Check for missing LPI points

In nationalparkservice/mojn-sv-rpackage: QC, Analysis, and Visualization of Spring Vegetation Data

Description

Check for missing LPI points

Usage

LpiQcMissingPoints(conn, path.to.data, park, spring, field.season,
  data.source = "database", points = seq(0.5, 15, 0.5))

Arguments

conn	Database connection generated from call to OpenDatabaseConnection(). Ignored if data.source is "local".
path.to.data	The directory containing the csv data exports generated from SaveDataToCsv(). Ignored if data.source is "database".
park	Optional. Four-letter park code to filter on, e.g. "MOJA".
spring	Optional. Spring code to filter on, e.g. "LAKE_P_BLUE0".
field.season	Optional. Field season name to filter on, e.g. "2019".
data.source	Character string indicating whether to access data in the spring veg database ("database", default) or to use data saved locally ("local"). In order to access the most up-to-date data, it is recommended that you select "database" unless you are working offline or your code will be shared with someone who doesn't have access to the database.
points	Vector representing the expected points on a transect. Defaults to seq(0.5, 15, 0.5) (a 15m transect sampled every 0.5m and starting at 0.5m).

Value

A tibble with columns Park, SpringCode, SpringName, VisitType, FieldSeason, StartDate, TransectNumber, LocationOnTape_m. Note that LocationOnTape_m is a comma-separated list of missing points.

Examples

## Not run: 
    conn <- OpenDatabaseConnection()
    LpiQcMissingPoints(conn, park = "LAKE")
    LpiQcMissingPoints(conn, spring = "LAKE_P_BLUE0", field.season = "2019")
    LpiQcMissingPoints(path.to.data = "path/to/data", data.source = "local")
    CloseDatabaseConnection(conn)

## End(Not run)

nationalparkservice/mojn-sv-rpackage documentation built on Oct. 29, 2021, 7:13 p.m.