Description Usage Arguments Details Author(s) References See Also Examples
Build a directed metadata graph describing a data source. This is usually the initial step to build METACLIP graphs
1 2 3 |
Dataset.name |
Name (label) of the Dataset. There is a number of already known Datasets, pertaining to the User Data Gateway
Public datasets of the climate4R Framework (see References). Type |
Dataset.subclass |
A character string indicating the Dataset subclass. The only (and disjoint) possible values
are |
DataProvider |
A Character string indicating the data provider of the Dataset (e.g. |
ModellingCenter |
Optional character vector, e.g. |
DataProvider.URL |
Optional: The URL from which the data was accessed. |
Project |
Optional: Character string indicating the Project leading to the generatrion of the Dataset (e.g. |
RCM |
Optional. Character string (length one). Simulation RCM model prducing the dataset (e.g. |
GCM |
Optional. Character string (length one). GCM producing the dataset
See |
Run |
Optional. When relevant, a character string (length one) indicating the model run (e.g. |
This function takes as reference the semantics defined in the Data Source and Transformation ontology
defined in the Metaclip Framework (http://metaclip.predictia.es/).
Many of the classes represented have individuals defined that can be directly instantiated instead of the Class itself. This has the advantage
of providing further annotations relevant for provenance description (e.g. references, relevant URLs, comments etc.).
This is automatically handled by the function when there is perfect match between the argument value and the known individual name.
To ensure consistency, the use of the helper function knownClassIndividuals
is recommended.
D. San MartÃn, J. Bedia
Visual schema of the data transformation ontology
Climate4R page at University of Cantabria
Other transformation: metaclip.graph.Command
,
metaclipR.Aggregation
,
metaclipR.AnomalyCalculation
,
metaclipR.Climatology
,
metaclipR.Ensemble
,
metaclipR.Regridding
,
metaclipR.etccdi
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 | # showUDGDatasources() will display all the known datasets from the User Data Gateway.
# With just indicating the dataset name (and the provider, which is not assumed to be UDG,
# so dataset metadata can be reused if accessed through other providers), the rest of metadata
# will be appennded. Further annotations are included inside the nodes (e.g. access URL,
# model run etc. Not shown by the i-graph plot display)
# A GCM
dataset <- "CMIP5_CNRM-CERFACS-CNRM-CM5_historical"
gcm.dataset <- metaclipR.Dataset(Dataset.name = dataset, DataProvider = "UDG")
plot(gcm.dataset$graph)
# An RCM (note the hadDrivingGCM property)
dataset <- "EUROCORDEX11_MOHC-HadGEM2-ES_r1i1p1_RCA4_v1_rcp45"
rcm.dataset <- metaclipR.Dataset(Dataset.name = dataset,
DataProvider = "UDG")
plot(rcm.dataset$graph)
# When dealing with known Individuals, the node is kept fix whenever it is necessary to refer to it:
metadata <- metaclipR.Dataset(Dataset.name = "E-OBS_v14_0.25regular",
DataProvider = "KNMI")
plot(metadata$graph)
|
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.