get_power() printed encoding
messagespars that are not valid returned a
cryptic error message as seen here, https://stackoverflow.com/questions/78416035/issue-with-nasapower-r-libraryFix typo thanks, @kguidonimartins!
Fix another typo in documentation.
Code and Roxygen linting.
Two new functions are added:
query_surfaces(): Query the POWER API for Detailed
Information on Wind Type Surfacesquery_groupings(): Query the POWER API for Detailed
Information on Available Parameter Groupingsquery_parameters now allows you to retrieve rich
metadata for the parameters.
Error, warning and other informational messages are now all formatted with {cli} for more attractive and informative messages.
The username passed along to the POWER API is now “nasapower4r” to support other packages built on {nasapower} that could use {vcr} in tests. Previously the user agent string took the version of {nasapower} and appended it, e.g., “nasapower410” for v4.1.0. Doing so breaks tests in packages relying on {nasapower} due to incompatibilities in cassettes, while not affecting functionality.
Fix formula in documentation that didn’t display properly in HTML.
Fix non-functional link in documentation.
Fix code coverage badging.
Use {cli} and {rlang} for clear messages for end users.
Use argument matching for function arguments where practical.
The temporal_api argument of
get_power() now defaults to “daily”, previously it had no
default value.
The temporal_average argument for
get_power() has now been removed after being deprecated and
issuing a message to users to use temporal_api instead
since release 4.0.0.
Replaces & or | with the proper
&& or ||.
Corrects documentation titles for functions to be title case.
Fixes the CRAN badge in the README.
Updates {vcr} configuration files for testing.
Reorder README to stress that this is not the data source and should not be cited as such.
Tidy up minor bits-n-pieces in documentation to make it nicer,
e.g., grammar corrections, using \dQuote{} rather
than ““” in ROxygen.
Uses sprintf() rather than paste()
where possible.
Update {vcr} configuration and infrastructure to use .json cassettes.
Remove an example that no longer works with the API.
Remove incorrect documentation about rate limiting and include details on how to use rate limiting.
Ensure tests are skipped on CRAN, thanks Maëlle!
Use skip_if_offline() rather than
skip_on_cran() for tests.
Redoc package to align with CRAN policies on well-formed HTML.
Update list of allowed parameters for querying the API, (18e4495e0ca2e9f14006260c019ac878a3023843).
Updated test infrastructure.
Adds new time_standard parameter to
get_power() as requested in ##70.
Updates internal list of accepted POWER parameters.
Fixes bug when requesting site_elevation. Thanks to
@daniel_althoff for reporting this
bug Issue
69.
Fixes bug where wind_elevation and
wind_surface were not properly passed along to the
API.
site_elevation corrected
data. Thanks to @daniel_althoff for reporting this
bug Issue
69.Thefileargument ofvroom()must useI()for literal data as of vroom 1.5.0..
Thanks to @palderman for the fix in Pull Request
67.Update checks for number of parameters requested by user, maximum of 15 for hourly and 20 for all other temporal APIs.
Return API messages to user to assist with troubleshooting when an error occurs server-side, see Issue 55.
The list of POWER parameters that can be queried from the API,
parameters, is now in alphabetical order.
Add paragraph to vignette describing how to work with possible rate limiting by API endpoints using ratelimitr. This is in place of internally rate-limiting due to the way ratelimitr handles function creation and the fact that the rate limits are extremely generous and may change as the project matures.
NA values were improperly handled.
Thanks to @femiguez for the Pull Request with
the fix.Enforces API limits client-side where the API limits unique queries to 30 per 60 seconds as found and reported by @camwur in Issue 57. This can be adjusted in future releases of nasapower if the POWER API changes as has been indicated is possible.
(Re)enables vcr for better unit testing.
More comprehensive unit tests.
Adds support for new NASA POWER API v2.0, which includes new hourly data and other major changes to the API and available data. See https://power.larc.nasa.gov/ for fully detailed changes to the data.
Drops support for the deprecated NASA POWER API V1.0. Previous versions of nasapower are no longer functional.
Adds new function, query_parameters() to fetch
information from the API on individual and all available
community/temporal API combination parameters.
Removes SSE community, replaced with
RE.
Removes global option for geographic coverage as
passed along through the latlon argument of
get_power().
Directly parse data from API response rather than downloading data to disk and importing.
The get_power() arguments are changed:
wind_elevation, andwind_surface,temporal_average argument has been superseded by
temporal_api to align with the terminology used in the
POWER API. The temporal_average argument will still work,
however, a message will be given if a user still uses
temporal_average to alert the user of the change and ask
them to update their scripts.Improved documentation.
Removes internal references to ICASA format files that are no longer supported in this client.
-99.00 value
rather than the proper NA for missing data. Thanks to
Fernando Miguez, https://github.com/femiguez, for the assistance in
isolating the issue.Due to the removal of the CRAN package APSIM from CRAN,
the removal of the create_met() function has been
implemented sooner than expected to keep nasapower on
CRAN.
Deprecates create_met()
create_icasa()Correct any missing or redirecting URLs
Replace deprecated subclass with class
in new_tibble()
Following a UNIX-like philosophy, this release removes
functionality to write APSIM .met and DSSAT ICASA files to disk.
nasapower now will only fetch the appropriate data and return a
tibble() object in-session, please use apsimx or the POWER
web API data access viewer, https://power.larc.nasa.gov/data-access-viewer/, for
fetching and/or writing .met or .icasa files, respectively. Note that
create_icasa() ideally should have been deprecated, but the
server was not responding properly when queried for some time before the
current release of nasapower so the function has been
removed.
Add ability to get_power() to accept a user-provided
site_elevation parameter that is passed to the API. When
this is used it will return a corrected atmospheric pressure value
adjusted to the elevation provided.
Use newest values from POWER team to validate user inputs for API requests, see https://github.com/ropensci/nasapower/issues/48 for more.
Replace raster with terra for examples of converting to spatial data in vignettes
Use vcr for enhanced testing
Refactor the internal handling of temporary files to allow for more efficient use of the future package
Corrects bug when querying the SB or SSE communities resulting in an error
Corrects example in vignette when creating a .met file
Update documentation to use ROxygen 7.0.0
Add new vignette, “Using nasapower with large geographic areas”
Correct URL in BibTeX version of citation
Suppress output in console from
APSIM::createMetFile()
Help file titles are now in sentence case
Fix issues reported in CRAN checks with failing tests. These tests should be skipped on CRAN but were not.
Fixes bug where missing values in POWER data were not properly
replaced with NA in tibble and metFile
outputs
Fixes bug in documentation for create_icasa() where
the parameter for file_out was misidentified as just
file
Fixes bug where .met files were not created properly including where “radn” and “rain” col headers were reversed
Fix
Warning: Must pass a scalar integer as 'nrow' argument to 'new_tibble()'.
Fixes bug where “CLIMATE” could not be requested for a single point
GLOBAL values are requested. This is now
specified in lonlat in conjunction with
temporal_average = CLIMATOLOGY.Adds example of fetching climate for a single point
Refactor code to split internal functions by functionality and add more complete test coverage
Removes internal check for data - community agreement, as all data is available for all communities, only the units change
Update links to latest documentation provided by the POWER team
nasapower until the
POWER team can properly address how pre-query validation should be
performedCorrects an instance where vignette example executed on CRAN but should not
Adds link to POWER website in error message when query fails
Documentation .Rd files are now more readable with better formatting
Flesh out examples using naspower data with
raster to create spatial objects for systems with low-RAM
where the functionality may not work as expected
Standardise formatting of vignette subheadings
Spell check vignette
Updates documentation examples
Provides nicer method of printing data in R console
Updates tests for better coverage and removes non-functional tests
Removes dplyr as an Import
Corrects issue where if() was called with a vector
of length 2 or more
Corrects logical operators && and
|| where they should be & or
|
Removes extra code in create_icasa() and
create_met() that performed a duplicated check of
latlon values
Removes unnecessary checks for latlon in
get_power()
Provides corrections to documentation formatting as per CRAN volunteers’ requests
Provides edits and clarifications in DESCRIPTION’s Description and Title about the package’s uses and capabilities
nasapower is now a part of rOpenSci after peer-review of the code!
Provides access to all three communities, AG, SSE and and SB, not just AG
Uses new ‘POWER’ ‘API’ to download new 1/2 x 1/2 degree data
Adds function get_power() to get weather data and
optionally metadata as well
Adds function create_met() to create ‘APSIM’ met
objects from ‘POWER’ data
Adds function create_icasa() to create a text file
of weather data for use in ‘DSSAT’ crop modelling
Internally, replaces httr package with crul
get_cell and get_region functions are
deprecated in favour of get_power(). The new POWER
interface allows for the specification of single points or regional
areas. Global coverage may be queried for Climatology. See the help for
?get_power() for more details.MONTH,
DAY and YYYY-MM-DD were incorrectly reported
in final data frame. This did not affect the weather data,
YEAR or DOY columns.Fix bug where lon/lat values were improperly assigned internally
due to row names not being ordered correctly in
get_region()
Fix bug reports link in DESCRIPTION file
Correct vignette where it had said, “both of which will which will download”
Correct documentation for get_region(), which
incorrectly stated that it downloaded data for a 1 x 1 degree
cell
Optimise arguments used in utils::read.table() to
ingest weather data in the get_cell() and
get_region() functions more quickly
NEWS now formatted more nicely for easier reading
Add statement about possible performance and memory usage when
using get_region() in the vignette
Add an example of converting the data frame to a spatial object
using raster to create a raster::brick()
Specify in documentation that a range of days to years can be specified for download
get_region() and get_cell() now default
to download all weather vars
Add a check to see if POWER website is responding before making request for data. If not, stop and return error message to user.
get_region() with multiple dates. https://github.com/ropensci/nasapower/issues/1Enhanced documentation
Superfluous function, .onLoad(), removed from
zzz.R
Tidied up startup message
Clean up vignette
Build vignette faster
Remove DATE from DESCRIPTION
Add new functionality to download regions in addition to single cells
Add static documentation website, https://docs.ropensci.org/nasapower/
Add startup message
Added a NEWS.md file to track changes to the
package.
First release, no changes to report yet
Need a high-speed mirror for your open-source project?
Contact our mirror admin team at info@clientvps.com.
This archive is provided as a free public service to the community.
Proudly supported by infrastructure from VPSPulse , RxServers , BuyNumber , UnitVPS , OffshoreName and secure payment technology by ArionPay.