← Back to home
Comparison · DevOps

rerddap vs zarr-python

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

rerddap vs zarr-python: at a glance

Featurererddapzarr-python
SectorDevOpsDevOps
Velocity score0.06.3
Sparks · 30d01
Top themesoceanographic-data, r-package, api-client, parquetpackage split, array storage, type system, release tooling
Last editorial update1h ago15h ago
WebsiteVisit →Visit →

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 →

What is zarr-python?

Zarr's monorepo split keeps spinning out standalone packages, each with its own release cadence.

Zarr-python has decomposed into independently versioned packages — zarr-metadata, zarr-indexing, zarr-http-server — each shipping on its own clock inside one repository. The http server was the point where the split stopped being a refactor and produced a capability Zarr did not have. The most recent releases are the boring half of that work: docs builds, changelog tooling, and type-alias widening that only matters to downstream annotators.

Read the full zarr-python trajectory →

rerddap vs zarr-python: editorial side-by-side

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.

Z6.3

Zarr's monorepo split keeps spinning out standalone packages, each with its own release cadence.

◆ Current state

Zarr-python has decomposed into independently versioned packages — zarr-metadata, zarr-indexing, zarr-http-server — each shipping on its own clock inside one repository. The http server was the point where the split stopped being a refactor and produced a capability Zarr did not have. The most recent releases are the boring half of that work: docs builds, changelog tooling, and type-alias widening that only matters to downstream annotators.

◆ Where it's heading

The split is being taken seriously as a distribution decision, not just a directory layout: each package gets its own docs site, its own towncrier changelog, and its own release notes discipline. That implies more packages will follow, and that the core zarr-python distribution is heading toward being a thin composition over them. Type-level changes in zarr-metadata are already being versioned as minor releases because they change what consumers can annotate against.

◆ Prediction

Expect further subpackages carved out of zarr-python along the same pattern, and zarr-indexing's LazyArray to gain the transform surface that TensorStore already exposes. A 3.2.0 final following the rc is the other open thread.

Alternatives to rerddap and zarr-python

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 rerddap or zarr-python.

See all rerddap alternatives → · See all zarr-python alternatives →

Recent activity from rerddap and zarr-python

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

  1. 1d agozarr-pythonzarr-metadata 0.5.0: JSONValue widened to Sequence, old constant spellings removed
  2. 2d agozarr-pythonSubpackage docs now build from the package directory
  3. 3d agozarr-pythonzarr-indexing 0.2.0: LazyArray brings lazy indexing to the array API
  4. 3d agozarr-pythonzarr_http_server-v0.1.0: HTTP server that exposes stores, arrays, groups (#3732)
  5. 15d agozarr-pythonzarr-indexing 0.1.0: TensorStore-style index transforms as a standalone package
  6. 16d agozarr-pythonzarr-metadata 0.4.0: model-layer changes and a standalone docs site
  7. 1mo agorerddapParquet output for griddap and pre-request size estimates
  8. 5mo agorerddapFix for parquet output in tabledap
  9. 6mo agorerddapInteractive plotting docs and clearer error messages
  10. 1y agorerddapGraceful failure when ERDDAP servers are unavailable
  11. 1y agorerddapParquet downloads and units attributes for tabledap
  12. 2y agorerddaptabledap returns types matching the server dds

Frequently asked questions

What is the difference between rerddap and zarr-python?

They serve adjacent needs but don't currently overlap on shipped themes. zarr-python is currently shipping more aggressively (velocity 6.3 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 rerddap better than zarr-python?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. zarr-python is currently shipping more aggressively (velocity 6.3 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 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.

What are the best alternatives to zarr-python?

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