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.

mobdb: Access the 'Mobility Database' API to Discover Transit Feeds

Search and access transit feed data from the 'Mobility Database' <https://mobilitydatabase.org>. The package wraps the 'Mobility Database' API, allowing users to discover 'GTFS' (General Transit Feed Specification) and 'GBFS' (General Bikeshare Feed Specification) feeds from agencies worldwide. Functions are designed to integrate seamlessly with packages like 'tidytransit' and 'gtfstools' for subsequent feed analysis.

Version: 1.0.1
Depends: R (≥ 4.1.0)
Imports: curl, httr2 (≥ 1.0.0), cli (≥ 3.0.0), rlang (≥ 1.0.0), tibble (≥ 3.0.0), dplyr (≥ 1.0.0), lifecycle, digest
Suggests: testthat (≥ 3.0.0), withr (≥ 2.0.0), httptest2, knitr, rmarkdown, tidytransit, gtfsio, keyring, sf, gbfs, zip, hms
Published: 2026-08-07
DOI: 10.32614/CRAN.package.mobdb (may not be active yet)
Author: Jason Adle [aut, cre, cph]
Maintainer: Jason Adle <developer at jasonadle.dev>
BugReports: https://github.com/jasonad123/mobdb/issues
License: MIT + file LICENSE
URL: https://mobdb.jasonadle.dev, https://github.com/jasonad123/mobdb
NeedsCompilation: no
Materials: README, NEWS
CRAN checks: mobdb results

Documentation:

Reference manual: mobdb.html , mobdb.pdf
Vignettes: Working with GTFS-Realtime and GBFS (source, R code)
Introduction to mobdb (source, R code)

Downloads:

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

Linking:

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