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.

ctOpenData: A Lightweight Interface to Connecticut Open Data APIs

Provides a unified set of helper functions to access datasets from the Connecticut Open Data platform <https://data.ct.gov/>. Functions return results as tidy tibbles and support optional filtering, sorting, and row limits via the Socrata API. The package provides a consistent interface for discovering and downloading datasets from the Connecticut Open Data Portal using human-readable dataset keys or official Socrata dataset identifiers.

Version: 0.1.1
Depends: R (≥ 4.1.0)
Imports: curl, dplyr, httr, janitor, jsonlite, rlang, tibble
Suggests: ggplot2, knitr, rmarkdown, scales, testthat (≥ 3.0.0), tidyr, vcr (≥ 0.6.0), webmockr
Published: 2026-09-05
DOI: 10.32614/CRAN.package.ctOpenData
Author: Shelby Lyn Gomes [aut] (GitHub: gomes-sh), Christian Martinez ORCID iD [aut, cre] (GitHub: martinezc1)
Maintainer: Christian Martinez <c.martinez0 at outlook.com>
BugReports: https://github.com/gomes-sh/ctOpenData/issues
License: MIT + file LICENSE
URL: https://github.com/gomes-sh/ctOpenData
NeedsCompilation: no
Materials: README, NEWS
CRAN checks: ctOpenData results

Documentation:

Reference manual: ctOpenData.html , ctOpenData.pdf
Vignettes: Getting Started with Connecticut Open Data (source)

Downloads:

Package source: ctOpenData_0.1.1.tar.gz
Windows binaries: r-devel: ctOpenData_0.1.1.zip, r-release: ctOpenData_0.1.1.zip, r-oldrel: ctOpenData_0.1.1.zip
macOS binaries: r-release (arm64): not available, r-oldrel (arm64): ctOpenData_0.1.1.tgz, r-release (x86_64): ctOpenData_0.1.1.tgz, r-oldrel (x86_64): ctOpenData_0.1.1.tgz

Linking:

Please use the canonical form https://CRAN.R-project.org/package=ctOpenData 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.