Currently running odc-geo == 0.5.0rc1.
I'm passing a Path object as destination to store a COG and it's raising an error in this line:
|
parsed_url = urlparse(dst) |
I believe it would be useful and definitely pythonic to support this input type, but I'm not sure how to proceed to PR it myself.
It is reproducible just by:
from pathlib import Path
from odc.geo.cog import save_cog_with_dask
dst = Path("test.tiff")
...
d = save_cog_with_dask(xx, dst)
AttributeError: 'PosixPath' object has no attribute 'decode'
Maybe checking the type of the argument before calling urlparse could be a solution, but I'm wondering what implications can it have if we allow as well S3Path, UPath and other kinds of Path objects that extend python Path.
Currently running
odc-geo == 0.5.0rc1.I'm passing a
Pathobject as destination to store a COG and it's raising an error in this line:odc-geo/odc/geo/cog/_tifffile.py
Line 780 in 9804d5b
I believe it would be useful and definitely pythonic to support this input type, but I'm not sure how to proceed to PR it myself.
It is reproducible just by:
Maybe checking the type of the argument before calling
urlparsecould be a solution, but I'm wondering what implications can it have if we allow as wellS3Path,UPathand other kinds ofPathobjects that extend pythonPath.