Skip to content

Releases: ropensci/nasapower

v4.2.1

21 May 02:23
92686a6
Compare
Choose a tag to compare

nasapower 4.2.1

Bug Fixes

  • Fixes Issue where querying all parameters failed.

nasapower v4.2.0

02 Feb 06:49
f1271c1
Compare
Choose a tag to compare

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

20 Aug 00:25
3eb851c
Compare
Choose a tag to compare

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 than paste where possible.

  • Update {vcr} configuration and infrastructure to use .json cassettes.

v4.0.9

05 Jan 23:53
fbc890e
Compare
Choose a tag to compare
  • 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.

v4.0.8

13 Aug 06:40
900dfef
Compare
Choose a tag to compare

v4.0.7

10 Apr 02:06
Compare
Choose a tag to compare

Minor changes

  • Adds new time_standard parameter to get_power() as requested in #70.

  • Updates internal list of accepted POWER parameters.

v4.0.6

03 Mar 09:51
Compare
Choose a tag to compare

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 and wind_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

02 Feb 00:45
Compare
Choose a tag to compare

nasapower 4.0.4

Bug fixes

  • Fixes message when importing data using vroom >= 1.5.0, The fileargument ofvroom()must useI() 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

19 Dec 00:45
a7041ed
Compare
Choose a tag to compare

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

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.

v4.0.0

23 Aug 11:58
Compare
Choose a tag to compare

nasapower 4.0.0

Major changes

  • 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:

    • two new arguments are added,
      • wind_elevation, and
      • wind_surface,
    • the 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.