query_ebird_db: Extract records from local eBird SQLite database that occur...

Description Usage Arguments Value

Description

This function is called from geo_ebird and is thus not intended to be called outside of that functionality.

Usage

1
2
query_ebird_db(query_polys, ebird_sqlite = "../Data/SE_eBird.sqlite",
  buffer = 2, table_name = NULL, SPDF = TRUE)

Arguments

query_polys

SpatialPolygonsDataFrame-class within and around which the user wishes to extract eBird records. It should also work, but is untested, with SpatialPointsDataFrame-class or SpatialLinesDataFrame-class) if a buffer is provided. The buffer settings currently assume that input query_polys are in a geographic (i.e., latitude and longitude) projection.

ebird_sqlite

character string file path to local eBird SQLite (.sqlite) database file

buffer

Approximate distance (km) from query_polys to include in the search for eBird records. A numeric vector of length 1. Negative values are allowed.

table_name

character string naming the table within ebird_sqlite that contains the relevant eBird data. If not specified, defaults to the first table in ebird_sqlite

SPDF

logical (default = TRUE) indicating whether the output should be converted into a SpatialPointsDataFrame-class. If TRUE, the returned SpatialPointsDataFrame-class is in the same projection as query_polys

Value

a data.frame of eBird records in the counties represented in the input polygons (and an associated buffer)


adamdsmith/geobird documentation built on May 10, 2019, 5:13 a.m.