-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Agrometeorology packages #83
Comments
Hi @adriancorrendo, I haven't added {nasapower}, {chirps} or {GSODR} partly because I've written or contributed to them and I may just be being modest but they're already in hydrology CTVs. But I certainly have written them with agrometeorology in mind. In fact, {GSODR} has the capability to fetch only station data between -60 -- 60 latitude for global agrometeorology work. I don't really have a clear handle on the CRAN or CTV policies where packages have a good bit of overlap between CTVs, TBH, @jpiaskowski do you have any thoughts? |
We did discuss this previously. The concern was that this task view was getting a bit too broad. If I recall, the thinking was to have genera weather retrieval packages in the hydrology TV and only include agrometeorology packages in the Agriculture TV is the package did additional data transformation that was useful to ag audiences. We don't want to have to track all weather retrieval packages. |
Thanks, @jpiaskowski, that's why I had that idea about the specificity apparently. Short memory. 😆 |
Thank you very much for the explanation. No changes then on the agrometeorology section of the CTV. Cheers, |
Hi there @adamhsparks , @jpiaskowski
I just realized there are a few packages/APIs related to accessing weather data that are worth it (I think) to be included as part of the "Agrometeorology" section of this CTV.
These packages are:
I use them myself, and used them for publishing a code to use these APIs (https://github.com/adriancorrendo/AgrometR, https://doi.org/10.1186/s13104-021-05622-8)
Also, Adam, I've checked on this other one based on one of your linkedin posts...but I haven't used it. Do you think this ctv would be appropriate? I believe so, but I'd like your opinion being the developer.
Thanks,
Adrian
The text was updated successfully, but these errors were encountered: