← Back to home
Comparison · DevOps

frictionless-r vs rerddap

A side-by-side editorial comparison of frictionless-r and rerddap — release velocity, themes, recent moves, and the top alternatives to consider.

frictionless-r vs rerddap: at a glance

Featurefrictionless-rrerddap
SectorDevOpsDevOps
Velocity score3.80.0
Sparks · 30d10
Top themesdata packages, r, standards, extension apioceanographic-data, r-package, api-client, parquet
Last editorial update1h ago3h ago
WebsiteVisit →Visit →

What is frictionless-r?

frictionless turns its internals into a public extension surface for Data Package readers

frictionless is the R reference implementation of the Frictionless Data Package standard: read, edit and write datapackage.json plus its CSV resources. The 1.3.0 release is the first to make the package aware of which standard version a file targets, and the first to expose resource objects as a documented public API rather than an internal detail. Its release history arrives in irregular archive bursts rather than a steady cadence, and version numbers in the feed are not monotonic.

Read the full frictionless-r trajectory →

What is rerddap?

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.

Read the full rerddap trajectory →

frictionless-r vs rerddap: editorial side-by-side

F3.8

frictionless turns its internals into a public extension surface for Data Package readers

◆ Current state

frictionless is the R reference implementation of the Frictionless Data Package standard: read, edit and write datapackage.json plus its CSV resources. The 1.3.0 release is the first to make the package aware of which standard version a file targets, and the first to expose resource objects as a documented public API rather than an internal detail. Its release history arrives in irregular archive bursts rather than a steady cadence, and version numbers in the feed are not monotonic.

◆ Where it's heading

The work has shifted from covering the standard to letting other packages build on top of it. Making resource() public, adding resource()<- for in-place overwrites, and moving package$directory and resource$read_from to attributes all separate the package's own state from the standard's properties, which is what downstream implementers need to add readers frictionless does not ship. The soft-deprecations of resources() and get_schema() point the same direction: a smaller, more deliberate public vocabulary.

◆ Prediction

The version() plumbing and the explicit warning on non-1.0 datapackage.json files read as groundwork for Data Package v2 support; expect the next substantive release to start reading v2 files rather than only detecting them.

R
rerddap
DEVOPS
0.0

An ERDDAP client steadily lowering the cost of pulling large oceanographic extracts

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to frictionless-r and rerddap

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 frictionless-r or rerddap.

See all frictionless-r alternatives → · See all rerddap alternatives →

Recent activity from frictionless-r and rerddap

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 15d agofrictionless-rfrictionless 1.3.0 makes resource objects a public API
  2. 1mo agorerddapParquet output for griddap and pre-request size estimates
  3. 5mo agorerddapFix for parquet output in tabledap
  4. 5mo agofrictionless-rfrictionless 1.2.1
  5. 6mo agorerddapInteractive plotting docs and clearer error messages
  6. 10mo agofrictionless-rfrictionless 0.11.0
  7. 10mo agofrictionless-rfrictionless 1.1.0
  8. 10mo agofrictionless-rfrictionless 1.2.0
  9. 1y agorerddapGraceful failure when ERDDAP servers are unavailable
  10. 1y agorerddapParquet downloads and units attributes for tabledap
  11. 2y agofrictionless-rfrictionless 1.0.3
  12. 2y agorerddaptabledap returns types matching the server dds

Frequently asked questions

What is the difference between frictionless-r and rerddap?

They serve adjacent needs but don't currently overlap on shipped themes. frictionless-r is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is frictionless-r better than rerddap?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. frictionless-r is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.

What are the best alternatives to frictionless-r?

Top frictionless-r alternatives in DevOps are ranked by recent ship velocity. Browse the "frictionless-r alternatives" section above for the current picks, or visit /alternatives/frictionless-r for the full list with editorial commentary on each.

What are the best alternatives to rerddap?

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.