Pause - ERDDAP #1113
Description
Hi Eric,
We have proposed the idea of creating an ERDDAP by the organization PacIOOS who I've been collaborating on a few projects. The definition of ERDDAP is: "The Environmental Research Division Data Access Program (ERDDAP™) is a visualization and data conversion tool that can incorporate multiple data subsets from different sources into a single workspace. It can convert disparate data types into a common format. ERDDAP was developed at the former Environment Research Division of NOAA's Southwest Fisheries Science Center."
Seth, who set up PacIOOS' Backyard Buoys project is in a email thread with you and me, Eric. The thread is called "ERDDAP" and Seth said:
"I wanted to follow up and share a link to the GitHub repository that I've recently set up. This has the code that we use to build out the datasets that we have on our ERDDAP server, including pulling the data from the Backyard Buoys database, running data QC tests, and writing it into netCDF files.
In the "backyardbuoys_dataccess.py" script, it does include a version of the functions that we had used to pull data via the sofar API, although I haven't tested them recently. They likely would need some polish, but there is a start there.
https://github.com/BackyardBuoys/backyardbuoys_erddap
Let me know if you have any issues, or if there are any questions with the files. Hopefully, this can be helpful to you all."
An ERDDAP would be useful for us because it's easy for users to extract all the data that we have gathered. For example, The Hong Kong university that wants to do a research project with all of our data has still not been able to extract it. An ERDDAP would make it easier for people to use and extract our data, which is basically the end goal of Aqualink. If an ERDDAP is the best way for us to achieve this, then it might be worth building one using Seth's code and instructions.