-
Notifications
You must be signed in to change notification settings - Fork 234
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
WIP: Thredds download function #2458
base: develop
Are you sure you want to change the base?
Conversation
@ankurdesai I had to remove the earlier PR I made last week with the SDA file changes attached. this is the new PR for the same Thredds function, but without non-related file changes. |
Turns out there was already a branch named thredds that was messing up my pr....... :/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see that this is still WIP so I hope my review isn't premature, but a few interface-level comments that are probably easier to address sooner rather than later.
Might also be useful to add a fully updated example that can double as a test case while you're working on the details.
run_parallel = TRUE) { | ||
# require("XML") | ||
# require("RCurl") | ||
require("foreach") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Functions should never explicitly load other packages. If it's not possible to call everything in namespaced form (foreach::fn_name(...)
), consider formally importing the functions you need from foreach
.
Once merged this will close #2415, correct? |
@infotroph, @ashiklom or @mdietze. What is the standard way to code in warnings. For example, I want a warning to pop up and kill data extraction if the user puts in a date range that the data doesn't exist during. |
Warning, errors, and logs should be handled through the logger functions in the PEcAn.utils package |
This PR is stale because it has been open 365 days with no activity. |
This function is the start of a general function that should be able to download data from THREDDS.
Description
The user can download any THREDDS datasets as long as they have site information, dates, and the base URLS needed to grab the datasets. Base URLS need the dataset name, but not the dates or locations. There will likely be issues pulling data sets in the future since they are not all stored in similarly structured directory formats like AVHRR LAI (which this function is based on). Updates to the function will occur as we start playing with more datasets from THREDDS.
Motivation and Context
We need an easy way to grab more datasets and THREDDS has many already, and is a great place to store future datasets that we can use.
Review Time Estimate
Types of changes
Checklist: