inbodb
inbodb is plumbing — it exists to survive INBO's database migrations without breaking user code
A side-by-side editorial comparison of r311 and rerddap — release velocity, themes, recent moves, and the top alternatives to consider.
r311 curates a catalogue of Open311 endpoints and now marks the dead ones explicitly.
r311 wraps Open311 civic-issue APIs behind one R interface, with a bundled list of municipal endpoints. Recent releases are dominated by keeping that list current — Helsinki added in 0.4.4, Espoo and Oulu in 0.4.3, with Ottawa, Siegburg, Northfield and Annaberg-Buchholz deprecated. Version 0.4.3 added the machinery to record that decay: questioned and deprecated keys that make o311_api() warn or abort.
An ERDDAP client steadily lowering the cost of pulling large oceanographic extracts
rerddap fetches gridded and tabular data from ERDDAP servers into R. The recent releases follow one practical thread — making large extracts cheaper to move — alongside routine robustness work on error messages and failure modes. 1.3.0 brings parquet output to `griddap()` and adds a function that estimates a download's size before the request is made.
r311 wraps Open311 civic-issue APIs behind one R interface, with a bundled list of municipal endpoints. Recent releases are dominated by keeping that list current — Helsinki added in 0.4.4, Espoo and Oulu in 0.4.3, with Ottawa, Siegburg, Northfield and Annaberg-Buchholz deprecated. Version 0.4.3 added the machinery to record that decay: questioned and deprecated keys that make o311_api() warn or abort.
The package's real work is curation, and it has started treating endpoint rot as a first-class state rather than letting requests fail silently. Error handling and condition objects were hardened in the same release, which fits a client whose dominant failure mode is a city's server going away. Releases are small and roughly annual.
Expect the next release to be another catalogue pass — a city or two added, more moved to questioned or deprecated — rather than new API surface.
rerddap fetches gridded and tabular data from ERDDAP servers into R. The recent releases follow one practical thread — making large extracts cheaper to move — alongside routine robustness work on error messages and failure modes. 1.3.0 brings parquet output to `griddap()` and adds a function that estimates a download's size before the request is made.
Parquet support has propagated across the package one function at a time: introduced for `tabledap()` in 1.2.0 where the maintainer reports up to 90% smaller files for large extracts, patched in 1.2.3, and extended to `griddap()` in 1.3.0. The size-estimation function added alongside it addresses the same problem from the other end, letting a user find out what a request will cost before committing to it. Around this, the package has absorbed the usual CRAN-driven hardening, notably making all external resource requests fail gracefully.
Expect the remaining data-access paths to converge on the same parquet-plus-pre-flight-estimate pattern, since that is how the last three feature releases have each extended it. The entries do not indicate work beyond data retrieval.
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either r311 or rerddap.
inbodb is plumbing — it exists to survive INBO's database migrations without breaking user code
secretbase quietly grew from a hashing package into a serialization toolkit
ducksemantics puts ontology grounding and late-interaction retrieval inside DuckDB, from R
frictionless turns its internals into a public extension surface for Data Package readers
GitHub is shipping models into Copilot weekly while quietly modernizing the OAuth platform underneath
Manticore's 29.0 line finally makes native sharded tables something you can operate, not just create
See all r311 alternatives → · See all rerddap alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. r311 and rerddap are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. r311 and rerddap are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top r311 alternatives in DevOps are ranked by recent ship velocity. Browse the "r311 alternatives" section above for the current picks, or visit /alternatives/r311 for the full list with editorial commentary on each.
Top rerddap alternatives in DevOps are ranked by recent ship velocity. Browse the "rerddap alternatives" section above for the current picks, or visit /alternatives/rerddap for the full list with editorial commentary on each.