What happened?
Just a heads up for both the users and maintainers of this package -- the THREDDS API:
https://github.com/hyriver/pydaymet/blob/main/src/pydaymet/pydaymet.py#L39
is going away in the next few days. I've been looking into alternatives (see, e.g. https://forum.earthdata.nasa.gov/viewtopic.php?t=7091 ) but haven't had a lot of success. I'll respond to this issue if I come up with something reliable -- we've been using more of your packages in https://github.com/environmental-modeling-workflows/watershed-workflow/ so just wanted to give you a heads up! Note that DayMet isn't going away, just the THREDDS API. I'm not sure about the single pixel API but can ask if it would be useful.
What did you expect to happen?
No response
Minimal Complete Verifiable Example
MVCE confirmation
Relevant log output
Anything else we need to know?
No response
Environment
Details
What happened?
Just a heads up for both the users and maintainers of this package -- the THREDDS API:
https://github.com/hyriver/pydaymet/blob/main/src/pydaymet/pydaymet.py#L39
is going away in the next few days. I've been looking into alternatives (see, e.g. https://forum.earthdata.nasa.gov/viewtopic.php?t=7091 ) but haven't had a lot of success. I'll respond to this issue if I come up with something reliable -- we've been using more of your packages in https://github.com/environmental-modeling-workflows/watershed-workflow/ so just wanted to give you a heads up! Note that DayMet isn't going away, just the THREDDS API. I'm not sure about the single pixel API but can ask if it would be useful.
What did you expect to happen?
No response
Minimal Complete Verifiable Example
MVCE confirmation
Relevant log output
Anything else we need to know?
No response
Environment
Details