vanishBearing: Sample motus detection data filtered to remove ambiguities

In MotusWTS/motusdata: Data package containing sample motus data

Description

Flat data file of motus sample data that has been filtered to remove ambiguious tags belonging to other projects.

Usage

vanishBearing

Format

A data frame with 50917 rows and 68 variables:

ts

timestamp, in seconds since 1 Jan, 1970 GMT; precision: 0.1 ms (SG); 2.5 ms (Lotek).

sig

signal strength in "native units"; for SG: dB (max) (logarithmic, 0 = max possible, -10 = 0.1 * max, etc.); for Lotek: raw value (0...255)

motusTagID

Motus tag ID - unique to each individual tag registered

tagDeployID

Motus tag deployment ID - unique to each individual tag deployment

tagBI

burst interval of tag, in seconds (e.g., 5.8984)

pulseLen

tag pulse length (milliseconds), if applicable. This value is only assigned based on the sample recording of the tag.

port

antenna code (for sensorgnomes, USB port number; for Lotek, whatever they use, usually numeric, but can be e.g. AH0)

mfgID

manufacturer ID

recvDeployID

Motus receiver deployment ID - unique to each individual receiver deployment

recvLat

Latitude associated with a receiver deployment, (degrees North)

recvLon

Longitude associated with a receiver deployment, (degrees East)

recvSiteName

name assigned to a site by the project manager (e.g. location name). This field is optional, and the same label can be used for multiple deployments.

antType

character; antenna type, e.g. "9-element Yagi", "Omni"

antBearing

numeric; compass direction antenna main axis is pointing at (degrees clockwise from local magnetic North 0-360)

antHeight

numeric; height (meters) of antenna main axis above ground

speciesEN

species English (common) name

Source

sample data provided by the Morbey et. al. (2017)

MotusWTS/motusdata documentation built on May 28, 2019, 1:54 p.m.