The new code produces bootstrapping data where the x and y coordinate values differ from the requested extent. They appear to align instead to the somewhat random coordinates of the NE corner of the clip_box prior to reprojection, which depend on the original grid, and the user-input extent.
This is a problem as data from different sources will project to different grids (e.g. bootstrapping and atmospheric data). I think the workaround is to provide ds.rio.reproject directly with a transform argument instead of crs and resolution.
The new code produces bootstrapping data where the x and y coordinate values differ from the requested extent. They appear to align instead to the somewhat random coordinates of the NE corner of the
clip_boxprior to reprojection, which depend on the original grid, and the user-input extent.This is a problem as data from different sources will project to different grids (e.g. bootstrapping and atmospheric data). I think the workaround is to provide
ds.rio.reprojectdirectly with atransformargument instead ofcrsandresolution.