table_findAdjacentLocations() to only only return unique locations and to ensure they are returned in order of separation distance.jitter = 0 in table_leaflet() and table_leafletAdd().table_filterByDistance().location_getOpenCageInfo() to get OpenCage information for a single location.location_getCensusBlock() to add censusYear argument.table_addOpenCageInfo() with support for reverse geocoding using tidygeocoder.mazama_initialize() now only loads the high resolution datasets used in location_initialize().match.arg().table_load() looks for .rda and then .csv versions.table_save() to avoid deprecated arguments to readr::write_csv().table_load() and table_save().table_export(). Use table_save() instead.~APIKey() functionality. Now importing this from MazamaCoreUtils 0.4.10.table_getLocationID() and table_getNearestDistance() by only calculating distance for unique locations. This helps tremendously when longitude and latitude come from “tidy” dataframes.table_initializeExisting().table_leaflet() and table_leafletAdd() with improved defaults and more flexibility.county to countyName. (This change more closely matches spatial metadata found in other systems and fits with the pattern of ~Code/~Name pairs in MazamaSpatialUtils as is the case with countryCode/CountryName and stateCode/stateName.)table_findAdjacentDistances() when only two locations are adjacent.table_updateColumn() now ignores NA values in locationID.validateLonLat(), validateLonsLats(), createLocationID().Version 0.2.x focuses on usability improvements after initial work with the package.
radius to distanceThreshold throughout for clarity.table_initializeExisting() to only perform spatial searches where data are missing in the incoming table. This greatly speeds up performance.table_leafletAdd() function to make it easier to compare “known locations” tables."table_addCoreMetadata() function adds columns of NA values for any missing core metadata but does not perform any spatial calculations.table_findAdjacentLocations() function returns a tibble of all locations that are too close (i.e. separated by < distanceThreshold).table_findOverlappingLocations() renamed to table_findAdjacentDistances().measure argument to table_findAdjacentLocations(), table_findAdjacentDistances(), table_getLocationID() and table_getNearestDistance().na.rm argument to validateLonsLats().table_~() functions.locationTbl whenever an incoming table includes longitude and latitude variables.table_leaflet() function to display locations and metadata.location_getSingleAddress_Photon() to remove revgeo dependency.geodist::geodist() is now always called with measure = "geodesic" to avoid warning messages from geodist() about inaccuracies with measure = "cheap" (the geodist() default).mazama_initialize() now installs required datasets if they are missing.table_findOverlappingLocations().table_initializeExisting() for fast conversion of an existing table of spatial metadata into a standardized “known location” table.table_findOverlappingLocations() to help choose an appropriate radius when initializing from an existing metadata table.addressService argument to table_addLocation(), table_addSingleLocation() andlocation_initialize()` to skip the address step that requires web services.location_getCensusBlock() function.location_getSingleAddress_TexasAM() function.setAPIKey() and getAPIKey().getLoations()getLocationID() and getNearestLocation()