Releases: ropensci/nasapower
v4.2.2
Bug fixes
Minor changes
-
Fix typo thanks, @kguidonimartins!
-
Fix another typo in documentation.
-
Code and Roxygen linting.
v4.2.1
nasapower v4.2.0
Minor Changes
-
Two new functions are added:
-
query_surfaces()
: Query the POWER API for Detailed Information on Wind Type Surfaces -
query_groupings()
: Query the POWER API for Detailed Information on Available Parameter Groupings
-
-
query_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.
Bug fixes
- Fixes a bug that allowed users to send requests to the API for hourly data over a region.
The API does not support this and this client now provides a user-friendly error when it is attempted.
nasapower 4.0.11
Bug fixes
-
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.
Minor changes
-
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 thanpaste
where possible. -
Update {vcr} configuration and infrastructure to use .json cassettes.
v4.0.9
-
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 thanskip_on_cran()
for tests.
v4.0.8
-
Redoc package to align with CRAN policies on well-formed HTML.
-
Update list of allowed parameters for querying the API, (18e4495e0ca2e9f14006260c019ac878a3023843).
-
Updated test infrastructure
v4.0.7
v4.0.6
nasapower 4.0.6
This release Includes 4.0.5, which was briefly released on CRAN and changes for 4.0.6 as documented here.
Bug fixes
-
Fixes bug when requesting
site_elevation
.
Thanks to @daniel_althoff for reporting this bug Issue 69. -
Fixes bug where
wind_elevation
andwind_surface
were not properly passed along to the API.
Minor changes
- Fixes redundant and broken tests by removing or updating new tests.
nasapower 4.0.5
Bug fixes
- Fixes bug when requesting
site_elevation
corrected data.
Thanks to @daniel_althoff for reporting this bug Issue 69.
v4.0.4
nasapower 4.0.4
Bug fixes
- Fixes message when importing data using vroom >= 1.5.0,
The
fileargument of
vroom()must use
I()for literal data as of vroom 1.5.0.
. Thanks to @palderman for the fix in Pull Request 67.
Minor changes
- Sets minimum version of tibble necessary for use with nasapower.
v4.0.3
This release includes two unreleased version changes, v4.0.1 and v4.0.2 as detailed below.
nasapower 4.0.3
Minor changes
- Fixes tests that should use vcr or be skipped on CRAN.
nasapower 4.0.2
Minor changes
-
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.
nasapower 4.0.1 (unreleased on CRAN)
Bug fixes
- Fixes a bug in where
NA
values were improperly handled.
Thanks to @femiguez for the Pull Request with the fix.
Minor changes
-
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.