GetDODSModelRunInfo: Get model coverage and data information for models on...

Description Usage Arguments Details Value Note Author(s) See Also Examples

View source: R/GetDODS.R

Description

Given a URL from GetDODSDates and a model run from GetDODSModelRuns, get information on the model domain, levels, and variables.

Usage

1
GetDODSModelRunInfo(model.url, model.run, download.file=TRUE)

Arguments

model.url

A URL for a model on the GrADS - DODS system, probably returned by GetDODSDates.

model.run

A specific model run, probably returned by GetDODSModelRuns

download.file

If TRUE, download the DODS .info file and read it in. If FALSE, try and read the .info file directly from the Internet.

Details

This routine grabs information about the latitude, longitude, and time coverage of a specific model instance. It also finds data about levels (if present) and lists all the available variables (though they may not have data in them). The user can refer to this information to construct calls to the DODS system via DODSGrab. Note that the XML package has trouble interpreting https from time to time; this can be circumvented by keeping download.file=TRUE.

Value

model.info

Information provided by the GrADS - DODS system about the given model instance.

Note

This function is very helpful in figuring out what's inside poorly documented models.

Author(s)

Daniel C. Bowman daniel.bowman@unc.edu

See Also

GetDODSDates, GetDODSModelRuns, DODSGrab

Examples

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
#An example for the Global Forecast System 0.5 degree model

#Get some information about the latest model url and date, real time server
abbrev <- "gfs_0p50"
## Not run: 
urls.out <- GetDODSDates(abbrev)
model.url <- tail(urls.out$url, 1)
model.runs <- GetDODSModelRuns(model.url)
model.info <- GetDODSModelRunInfo(model.url, tail(model.runs$model.run, 1))
print(model.info)

## End(Not run)


rNOMADS documentation built on May 19, 2017, 12:38 p.m.
Search within the rNOMADS package
Search all R packages, documentation and source code

Questions? Problems? Suggestions? Tweet to @rdrrHQ or email at ian@mutexlabs.com.

Please suggest features or report bugs in the GitHub issue tracker.

All documentation is copyright its authors; we didn't write any of that.