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.
The interface package to access data from the 'EpiGraphDB' <https://epigraphdb.org> platform. It provides easy access to the 'EpiGraphDB' platform with functions that query the corresponding REST endpoints on the API <https://api.epigraphdb.org> and return the response data in the 'tibble' data frame format.
| Version: | 0.2.3 |
| Imports: | magrittr, tibble, httr, glue, purrr, jsonlite |
| Suggests: | testthat, roxygen2, knitr, rmarkdown, spelling, devtools, usethis, pkgdown, styler, lintr, covr, igraph, gtools, stringr, dplyr, ggplot2 |
| Published: | 2022-01-14 |
| DOI: | 10.32614/CRAN.package.epigraphdb |
| Author: | Yi Liu [cre, aut], Valeriia Haberland [aut], Marina Vabistsevits [aut], Tom Gaunt [aut], MRC IEU [cph] |
| Maintainer: | Yi Liu <yi6240.liu at bristol.ac.uk> |
| BugReports: | https://github.com/MRCIEU/epigraphdb-r/issues |
| License: | GPL-3 |
| URL: | https://mrcieu.github.io/epigraphdb-r/ |
| NeedsCompilation: | no |
| Language: | en-GB |
| Materials: | README NEWS |
| CRAN checks: | epigraphdb results |
| Reference manual: | epigraphdb.pdf |
| Vignettes: |
About Getting started with EpiGraphDB in R Meta functionalities of the EpiGraphDB platform Options Using EpiGraphDB API Using EpiGraphDB R package |
| Package source: | epigraphdb_0.2.3.tar.gz |
| Windows binaries: | r-devel: epigraphdb_0.2.3.zip, r-release: epigraphdb_0.2.3.zip, r-oldrel: epigraphdb_0.2.3.zip |
| macOS binaries: | r-release (arm64): epigraphdb_0.2.3.tgz, r-oldrel (arm64): epigraphdb_0.2.3.tgz, r-release (x86_64): epigraphdb_0.2.3.tgz, r-oldrel (x86_64): epigraphdb_0.2.3.tgz |
| Old sources: | epigraphdb archive |
Please use the canonical form https://CRAN.R-project.org/package=epigraphdb to link to this page.
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.