Skip to contents

Events record occurrences such as mortality, health observations, drop-offs, or depredation. For GPS position data, use telem_create_positions() instead.

Usage

telem_create_events(data, dry_run = FALSE, verbosity = 0)

Arguments

data

A tibble with columns: device_id, type, source. project_id is also required by the API, but it is filled in automatically from the session, so callers need not supply it. Optional columns: status, date, place, payload, notes, and two that anticipate pending API changes: deployment_id, which links the event to a deployment and therefore to an animal, and cause/predator, a cause and predator of death (see telem_mortality_causes()). None of those three is a schema field yet — deployment_id is dropped with a warning, and cause/predator are folded into notes. All three are still accepted here so that callers need not change when the API catches up.

dry_run

Logical. If TRUE, prints the request without sending it.

verbosity

Integer. How much information to print (0 = silent, 1 = headers, 2 = headers + body, 3 = full).

Value

A tibble of created events with their assigned IDs.