Releases: MazamaScience/MazamaLocationUtils
Releases · MazamaScience/MazamaLocationUtils
0.4.4
0.4.3
MazamaLocationUtils 0.4.3
- Updated
location_getSingleElevation_USGS()
to use new USGS API.
0.4.2
MazamaLocationUtils 0.4.2
- Add uniqueness of
locationID
tovalidateLocationTable()
. table_save()
now supports a vector ofoutputType
formats and will save
the location table in multiple formats.
0.4.1
MazamaLocationUtils 0.4.1
- Documentation fixes for CRAN submission.
MazamaLocationUtils 0.4.0
- Added
clusterByDistance()
andtable_addClustering()
functions. - Renamed
zip
topostalCode
in the core metadata. location_createID()
now defaults to the"geohash"
algorithm.- Renamed
mazama_initialize()
toinitializeMazamaSpatialUtils()
. - Updated example data to October, 2023.
- Added "Developer Style Guide" vignette.
- Improved documentation.
0.3.11
MazamaLocationUtils 0.3.11
- Added
algorithm argument
to location_createID() to select between "digest"
and "geohash". - Addressed CRAN package documentation issue.
0.3.10
MazamaLocationUtils 0.3.10
- Added
na.rm = TRUE
to all calls toany(...)
in varioustable_~()
functions.
0.3.9
MazamaLocationUtils 0.3.9
- Updated
location_getSingleElevation_USGS()
to use the new web service at
https://apps.nationalmap.gov/pqs/.
0.3.8
MazamaLocationUtils 0.3.8
- Updated documentation in
location_getSingleElevation_USGS()
.
0.3.7
MazamaLocationUtils 0.3.7
- Updated
table_updateColumn()
to ignore incominglocationIDs
that are not
found in thelocationTbl
.
0.3.6
MazamaLocationUtils 0.3.6
- Added
table_getDistanceFromTarget()
and edited the description of other
distance functions to make clear what each does.
MazamaLocationUtils 0.3.5
- Removed
validateMazamaSpatialUtils()
test fromtable_addCoreMetadata()
as
this function just adds empty columns and does not need any spatial data.
MazamaLocationUtils 0.3.4
- Updated
table_addOpenCageInfo()
to handle address components that are
missing from the openCage results.