Open mdietze opened 9 years ago
data dynamically rather than storing a copy of everything in the INPUTS table.
I don't think we need to store the data locally, but would be good if we can use the inputs table as pointers to the client, package / object, date of acquisition.
Also, once we come up with a proposal, we should ask for feedback from the DataOne and Ropensci groups for feedback.
This has been tackled in the following PRs (and possibly a few others around the same time): #1554, #1578, #1647, #1648, #1666.
@mdietze Not sure about the status of completeness, so you should check if this can be closed?
Far from complete. Should be a high-priority GSOC option.
This issue is stale because it has been open 365 days with no activity.
support for DataOne is in the PEcAn 2 proposal and, as noted in the email from Ankur (below) from June, there's lots of useful data there and an R client
This task will probably need to be broken down into a number of sub-tasks, and eventually we'll want to work with data dynamically rather than storing a copy of everything in the INPUTS table.
Probably the first step is to support downloading a dataset with known name / identifier
or
From there we can move to searching (by variable, time, and location), and eventually to the capacity to upload PEcAn projects to repositories