You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
returns a tbl_df with tbl_df$datetime_last = "2023-10-29"
So, it effectively builds a URL of: https://api.azmet.arizona.edu/v1/observations/hueto/az07/2023-10-29T00:00/P1DT0H
when we'd want this, instead: https://api.azmet.arizona.edu/v1/observations/hueto/az07/2023-10-29T00:00/P1DT24H
The URL: https://api.azmet.arizona.edu/v1/observations/hueto/az07/2023-10-29T00:00/P1D
which I think is what the code actually builds, returns the same data as the former URL, above. Do we need to specify "T0H" at the end of the currently constructed URL?
Note: I'm looking at code from the date-input-flex branch.
The text was updated successfully, but these errors were encountered:
It doesn't appeary to have anything to do with whether time is specified or not. P2D also gets data with "2023-10-30" for datetime_last. I think this is more likely a quirk with how dates are interpreted by the API. I'll do a little investigating and open a PR with a proposed fix.
It should return data to
date - 1
. I suspect it involves code inparse_params.R
that builds the URL of the data request for the API.For example, at present
returns a
tbl_df
withtbl_df$datetime_last
= "2023-10-29"So, it effectively builds a URL of:
https://api.azmet.arizona.edu/v1/observations/hueto/az07/2023-10-29T00:00/P1DT0H
when we'd want this, instead:
https://api.azmet.arizona.edu/v1/observations/hueto/az07/2023-10-29T00:00/P1DT24H
The URL:
https://api.azmet.arizona.edu/v1/observations/hueto/az07/2023-10-29T00:00/P1D
which I think is what the code actually builds, returns the same data as the former URL, above. Do we need to specify "T0H" at the end of the currently constructed URL?
Note: I'm looking at code from the
date-input-flex
branch.The text was updated successfully, but these errors were encountered: