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
I was wondering if it'd make sense to add an option to output the downscaled variables as a spatial object instead of a data.table. Perhaps a vector object?
I only foresee one issue at this point, which is the lat of projection/spatial metadata info in the xyz input object. A solution would be to add bbox as an optional argument (from which we'd extract spatial metadata) or a CRS argument.
Thoughts?
The text was updated successfully, but these errors were encountered:
That would probably make sense - would we use sf or terra? So far I've found sf is faster for vector data than terra, but would require adding another dependency. Also - would this be related to providing optional raster output for downscaled variables?
Re: crs, it's required that the input is in epsg:4326, so I think we can just output in that projection.
I was wondering if it'd make sense to add an option to output the downscaled variables as a spatial object instead of a
data.table
. Perhaps a vector object?I only foresee one issue at this point, which is the lat of projection/spatial metadata info in the
xyz
input object. A solution would be to addbbox
as an optional argument (from which we'd extract spatial metadata) or a CRS argument.Thoughts?
The text was updated successfully, but these errors were encountered: