The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
Ensure ‘[’ and ’]’ properly encoded in URL
Changed default cacheing behavior and ‘cache_setup()’
server() (to fetch known ERDDAP server URLs) now uses the list maintained by irishmarineinstitute/awesome-erddap on GitHub (#86)griddap(): if no dimension arguments passed, we error saying so (and no http requests made); in addition, if a dataset is passed to griddap(), to which the output of info() was also passed, then we can check if the dataset has griddap data or not, and fail saying so if not (#91)griddap() and tabledap(): if info() output passed to these two funcitons, we will now use the url within that info output, and use a message telling the user we are doing so; now you don’t have to set the url if you pass info output (#92)convert_units test that was failing because remote service had changed the responseerr_handle() for handling http errors - ERDDAP servers changed to some weird JSON-ish type format (#85)tibble::as_data_frame/tibble::data_frame to tibble::as_tibble (#79)info() gains new element in its output list, base_url, the base url for the ERDDAP server under consideration (#80)griddap() with respect to what’s returned from the function (#81)griddap() to account for cases when min and max are reversed from the order they should be in (#78)griddap() to parse additioanl dimensions returned; previously we were only returning time, lat, and lon, plus one more (#82) thanks @afredstonhermannCaching section to package level manual file (?rerddap) about caching (#52)httr with crul (#54)vcr (#76)read parameter in griddap() (#47)eurl(); used as default in main functions; set default url with env vars, see ?eurl (#41)griddap(): when nc format gridded datasets have latitude and longitude we “melt” them into a data.frame for easy downstream consumption. When nc format gridded datasets do not have latitude and longitude components, we do not read in the data, throw a warning saying so. You can readin the nc file yourself with the file path (#74)griddap() to support cases in wihch lat/lon runs north to south and south to north (#68)memory() usage in griddap() wasn’t working. fixed now (#77)hoardr to manage caching paths and such (#60). Also now asking users where they want to cache files, either in a rappdirs user cache dir or a temp directory. Now on tests and examples we use temp dirs.cache_info() to get cache path and number of cached files, and cache_setup() to set cache path.cache_details(), cache_list(), and cache_delete() lose their cache_path parameter - now cache path is set package wide and we use the same cache path, so no need to set in the fxn call.griddap() and tabledap() examples to use datasets that still exist (previous examples used datasets that are no gone)info() function gains new attribute url with the base url for the ERDDAP server used (#42)tibble package (#45)servers() function (#49)http to https (#50)griddap() and tabledap() for how to best deal with 500 server errors (#48)dplyr::rbind_all uses with dplyr::bind_rows (#46)ncdf package, which has been taken off CRAN. Using ncdf4 now for all NetCDF file manipulation. (#35)file.info()$size instead of file.size() to be backwards compatible with R versions < 3.2griddap() and tabledap() so that the user can easily see cache details or delete the file from the cache without having to manually get the file name. (#30)importFrom so we only import functions we need instead of their global namespaces.griddap() function (#28)servers() function (#21)query parmaeter in httr::GET() caused an error (#23)httr::write_disk() (#24)last is a value accepted by ERDDAP servers, but internal functions weren’t checking correctly, fixed now. (#25)as.info() wasn’t passing on the url parameter to the info() function. fixed now. (#26)These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.