Describe the bug
Calling read_geotiff_dask() directly on a .vrt path silently drops several kwargs. The defensive .vrt route forwards dtype, name, and chunks, but it drops window, band, and max_pixels.
Expected behavior
Direct read_geotiff_dask(vrt_path, ...) should either reject VRTs with a clear message or forward supported kwargs to read_vrt() so behavior matches open_geotiff(vrt_path, ...).
Screenshots
Not applicable.
Desktop
Not applicable.
Smartphone
Not applicable.
Additional context
This is a backend-dispatch parity issue in xrspatial/geotiff/__init__.py.
Describe the bug
Calling
read_geotiff_dask()directly on a.vrtpath silently drops several kwargs. The defensive.vrtroute forwardsdtype,name, andchunks, but it dropswindow,band, andmax_pixels.Expected behavior
Direct
read_geotiff_dask(vrt_path, ...)should either reject VRTs with a clear message or forward supported kwargs toread_vrt()so behavior matchesopen_geotiff(vrt_path, ...).Screenshots
Not applicable.
Desktop
Not applicable.
Smartphone
Not applicable.
Additional context
This is a backend-dispatch parity issue in
xrspatial/geotiff/__init__.py.