Since this package does the 'dirty work' I'd propose a download.GSOD that immediately saves the downloaded data.frame as netcdf CF. Should be a quick and easy function to write.
Ironically, what will be harder will be to add the GSOD sites to the database (site group?) and alter the web code to detect if we've selected a site with GSOD met.
Eventually it would also be good to search for met towers within some radius and to begin to support spatial downscaling / interpolation, but that's definitely not required for this issue (and would equally apply to other local met we already have, such as Ameriflux and FLUXNET).
As with Ameriflux and FLUXNET, we'll also run into the issue that the current workflow doesn't check the dates of available met -- I think the R package supports that, but we have no step in the workflow (preferably within the web interface, not workflow.R) to check date ranges prior to download (the workflow DOES check dates for already downloaded Inputs).
Description
Now that we've almost got met downscaling, we're getting close to being able to support the wider range of local met data out there. One such database is NOAA's Global Surface Summary of the Day (GSOD) https://data.noaa.gov/dataset/global-surface-summary-of-the-day-gsod
Possible Implementation
There is an Ropen Sci package, gsodr, that supports download of this data and returns a data.frame. Here's a blog about it's use: http://ropensci.org/blog/blog/2017/04/04/gsodr
Since this package does the 'dirty work' I'd propose a download.GSOD that immediately saves the downloaded data.frame as netcdf CF. Should be a quick and easy function to write.
Ironically, what will be harder will be to add the GSOD sites to the database (site group?) and alter the web code to detect if we've selected a site with GSOD met.
Eventually it would also be good to search for met towers within some radius and to begin to support spatial downscaling / interpolation, but that's definitely not required for this issue (and would equally apply to other local met we already have, such as Ameriflux and FLUXNET).
As with Ameriflux and FLUXNET, we'll also run into the issue that the current workflow doesn't check the dates of available met -- I think the R package supports that, but we have no step in the workflow (preferably within the web interface, not workflow.R) to check date ranges prior to download (the workflow DOES check dates for already downloaded Inputs).