Taher Chegini

I am the developer of [Py3DEP](https://github.com/cheginit/py3dep) package. It gets topography data from The National Map's [3DEP](https://www.usgs.gov/3d-elevation-program) at a given resolution. It returns the data as an `xarray.Dataset` (or `xarray.DataArray`). It...

The workaround is simple enough, thanks! I agree that direct `xarray` support is much better. Py3DEP returns the results as parallelized datasets (with `dask`) which combined with `numba` version of...

NASA's EarthData uses `netrc` for their service. I looked at EarthExplorer's API but it seems that they need passing the user/pass directly to its web service. I think following a...

Great! The latest conda version of my package already has `attrs

Great. Thank you!

The issue with `osx-arm64` can be solved following the instruction [here](https://conda-forge.org/blog/posts/2020-10-29-macos-arm64/#how-to-add-a-osx-arm64-build-to-a-feedstock). Essentially, [this](https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/main/recipe/migrations/osx_arm64.txt) file needs to be edited by adding `pysheds` to the list, which then triggers a bot to...

For some reason, it's working fine now. I created a fresh env to get ready for a PR and noticed that it's working correctly now. I don't know what was...

OK, I figured out the issue using `rioxarray`'s source code. It gets the wrong order depending on the sign of the resolution that you get from the affine. I will...

I couldn't reproduce your error. This works without any warning or error: Can you please show the output of `pygeohydro.show_versions()`.

I just created a new environment just to make sure, I am using the same version as yours, and it ran without any issue again. This is how created the...