Releases: uace-azmet/azmetr
Releases · uace-azmet/azmetr
azmetr 0.3.0
az_hourly()
now accepts dates forstart_date_time
andend_date_time
- Improved messages regarding what date/time ranges are being queried and returned by data retrieval functions.
az_hourly()
now returns data from the previous hour whenstart_date_time
andend_date_time
are not supplied rather than returning the previous day of hourly data.azmet
is now much more verbose, printing messages about which data are requested and which data are returned.- Added an option
"azmet.print_api_call"
which, when set toTRUE
prints the HTTP request sent to the API—for debugging purposes. - Fixed a bug that caused an error when data was requested from all stations but some stations didn't have data for all variables.
- Requests for data before January 1, 2021 now error, since these data are not on the AZMet API (yet).
azmetr 0.2.1
az_daily()
andaz_hourly()
now print a warning if there is any missing data for the combination of dates and stations requested- Transferred maintenance of package to Jeremy Weiss
- Timestamp for hourly and daily maximum two-minute sustained wind speeds,
wind_2min_timestamp
now appears in downloaded data - Variable type for hourly and daily
wind_2min_timestamp
now is date-time instead of character with correct time zone,tzone = "America/Phoenix"
- Values for hourly
date_datetime
variable now havetzone = "America/Phoenix"
assigned - The
station_info
dataset now includes elevation
azmetr v0.2.0—adds ratelimit and units for new variables
What's Changed
azmetr
now uses thehttr2
package instead ofhttr
for API requests. This change allowed for easier rate limiting- There is now a rate limit of 4 requests per second to the API. This shouldn't cause noticible slowdowns except when using the
station_id
argument maybe az_add_units()
now adds units to newwind_2min_*
variables recently added to the API
Initial release of `azmetr`
This is the initial "official" release of the azmetr
package.