Closed anguswg-ucsb closed 11 months ago
with new code:
library(climateR)
daymet <- climateR::getDaymet(
AOI = AOI::aoi_get(state = "CA", county = "San Luis Obispo"),
varname = "tmax",
startDate = "2018-01-01",
endDate = "2018-01-02",
verbose = TRUE
)
#> source: https://thredds.daac.ornl.gov/thredds/dodsC/daymet-v4-agg/na...
#> varname(s):
#> > tmax [degrees C] (daily maximum temperature)
#> ==================================================
#> diminsions: 149, 135, 2 (names: x,y,time)
#> resolution: 1000, 1000, 1 days
#> extent: -1843750, -1694750, -608500, -473500 (xmin, xmax, ymin, ymax)
#> crs: +proj=lcc +lat_1=25 +lat_2=60 +x_0=0 +y_0=0 +units...
#> time: 2018-01-01 12:00:00 to 2018-01-02 12:00:00
#> ==================================================
#> values: 40,230 (vars*X*Y*T)
terra::plot(daymet[[1]])
Created on 2023-08-21 by the reprex package (v2.0.1)
@anguswg-ucsb please see these last changes and if they need to be addressed in climatePy. Thanks!
It looks like
getDaymet()
returns data that is off by one for any given date range. If this is the expected behavior, this issue can be closed. Here is an example of what I am describing: