table_addCoreMetadata

An existing table will be amended to guarantee that it includes
the following core metadata columns.
<ul>
<li>locationID</li>
<li>locationName</li>
<li>longitude</li>
<li>latitude</li>
<li>elevation</li>
<li>countryCode</li>
<li>stateCode</li>
<li>countyName</li>
<li>timezone</li>
<li>houseNumber</li>
<li>street</li>
<li>city</li>
<li>postalCode</li>
</ul>The <code>longitude</code> and <code>latitude</code> columns are required to exist in the
incoming tibble but all others are optional.
If any of these core metadata columns are found, they will be retained.
The <code>locationID</code> will be generated (anew if already found) from existing
longitude and latitude data.
Other core metadata columns will be filled with <code>NA</code> values of the
proper type.
The result is a tibble with all of the core metadata columns. Theses columns
must then be filled in to create a usable "known locations" table.

Utility functions for discovering and managing metadata
associated with spatially unique "known locations". Applications include
all fields of environmental monitoring (e.g. air and water quality) where
data are collected at stationary sites.

Jonathan Callahan

MazamaLocationUtils

Manage Spatial Metadata for Known Locations

Eli Grosman

Oliver Fogelin

table_addCoreMetadata function

<dl><dt>locationTbl</dt>
<dd>Tibble of known locations. This input tibble need not be a
standardized "known location" with all required columns. They will be added.</dd>
<dt>precision</dt>
<dd><code>precision</code> argument passed on to location_createID.</dd></dl>

Arguments

An existing table will be amended to guarantee that it includes
the following core metadata columns.
<ul>
<li>locationID</li>
<li>locationName</li>
<li>longitude</li>
<li>latitude</li>
<li>elevation</li>
<li>countryCode</li>
<li>stateCode</li>
<li>countyName</li>
<li>timezone</li>
<li>houseNumber</li>
<li>street</li>
<li>city</li>
<li>postalCode</li>
</ul>

The <code>longitude</code> and <code>latitude</code> columns are required to exist in the
incoming tibble but all others are optional.
If any of these core metadata columns are found, they will be retained.
The <code>locationID</code> will be generated (anew if already found) from existing
longitude and latitude data.
Other core metadata columns will be filled with <code>NA</code> values of the
proper type.
The result is a tibble with all of the core metadata columns. Theses columns
must then be filled in to create a usable "known locations" table.

Add missing core metadata columns to a known location table — table_addCoreMetadata

<dl>

<dt>locationTbl</dt>
<dd>Tibble of known locations. This input tibble need not be a
standardized "known location" with all required columns. They will be added.</dd>


<dt>precision</dt>
<dd><code>precision</code> argument passed on to location_createID.</dd>

</dl>

table_addCoreMetadata: Add missing core metadata columns to a known location table

Description

Usage

Value

Arguments