← Back to home
Comparison · Infra & APIs

discretetests vs gpkg

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

Shared themes:r-package

discretetests vs gpkg: at a glance

Featurediscretetestsgpkg
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesstatistical-testing, exact-tests, nonparametric, r-packagegeospatial, geopackage, r-package, gdal
Last editorial update3h ago45m ago
WebsiteVisit →Visit →

What is discretetests?

Four years of releases land in four minutes as the changelog gets backfilled to GitHub

DiscreteTests computes exact p-values and their full support for discrete statistical tests, returning results as a class that carries the observations, the test statistic and the null distribution. All four visible releases were tagged within four minutes of each other on a single day in May 2026, in reverse order — 0.4.1 carries the earliest timestamp and 0.4.0 the latest — so this is a historical changelog being pushed to GitHub at once, not four days of work.

Read the full discretetests trajectory →

What is gpkg?

An R interface to GeoPackage that keeps sanding down its own API

gpkg gives R users a direct handle on GeoPackage files — the SQLite-based OGC container for vector and raster layers — through lazy table access, OGR/SQLite dialect queries and terra integration. Recent releases center on raster write ergonomics: automatic NoData selection via auto_nodata and an exported gpkg_default_nodata() following GDAL and terra conventions. Release bodies are cumulative, folding two or three versions into one entry.

Read the full gpkg trajectory →

discretetests vs gpkg: editorial side-by-side

D
discretetests
INFRA · APIS
0.0

Four years of releases land in four minutes as the changelog gets backfilled to GitHub

◆ Current state

DiscreteTests computes exact p-values and their full support for discrete statistical tests, returning results as a class that carries the observations, the test statistic and the null distribution. All four visible releases were tagged within four minutes of each other on a single day in May 2026, in reverse order — 0.4.1 carries the earliest timestamp and 0.4.0 the latest — so this is a historical changelog being pushed to GitHub at once, not four days of work.

◆ Where it's heading

Read by version rather than by timestamp, the package grew from binomial, Fisher, McNemar and Poisson tests into rank-based and resampling territory: Wilcoxon signed rank and rank sum, Mann-Whitney U, a conditional homogeneity test, then sign tests and a general permutation test with several built-in statistics. Alongside that the result class was extended to hold ragged observation lists and computational detail, the print output was rewritten on cli, and the old dot-separated function names were made defunct.

◆ Prediction

The permutation test with pluggable statistics is the most open-ended addition here, and adding further built-in statistics to it is the cheapest way to extend the package from where it now stands.

G
gpkg
INFRA · APIS
0.0

An R interface to GeoPackage that keeps sanding down its own API

◆ Current state

gpkg gives R users a direct handle on GeoPackage files — the SQLite-based OGC container for vector and raster layers — through lazy table access, OGR/SQLite dialect queries and terra integration. Recent releases center on raster write ergonomics: automatic NoData selection via auto_nodata and an exported gpkg_default_nodata() following GDAL and terra conventions. Release bodies are cumulative, folding two or three versions into one entry.

◆ Where it's heading

The package is still finding its interface shape, and most releases pair a small capability with a deprecation or signature change — destfile giving way to y, gpkg_create_dummy_features deprecated, vapour swapped out for gdalraster. The consistent direction is deferring to GDAL and terra conventions rather than inventing gpkg-specific behaviour, and pushing connection management out of users' hands. Cadence is roughly one release a year with dependency automation now in CI.

◆ Prediction

Expect further alignment of write-path defaults with GDAL conventions and continued deprecation-with-replacement of early argument names, with an ogr2ogr-style path for out-of-memory vector data flagged as a possibility rather than a commitment.

Alternatives to discretetests and gpkg

Other Infra & APIs 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 discretetests or gpkg.

See all discretetests alternatives → · See all gpkg alternatives →

Recent activity from discretetests and gpkg

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

  1. 2mo agodiscretetestsSign tests and a pluggable permutation test
  2. 2mo agodiscretetestsInput observation names carried through results
  3. 2mo agodiscretetestsWilcoxon, Mann-Whitney and homogeneity tests join the package
  4. 2mo agodiscretetestsmacOS compilation fix
  5. 4mo agogpkgAutomatic NoData selection for raster writes
  6. 1y agogpkgConnection handling reworked; table access via [ and [[
  7. 2y agogpkgSpatial views: dynamic layers that read as static ones
  8. 2y agogpkgInitial CRAN release, with OGR query support

Frequently asked questions

What is the difference between discretetests and gpkg?

Both compete on the same themes — r-package — within Infra & APIs. discretetests and gpkg 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.

Is discretetests better than gpkg?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. discretetests and gpkg 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to discretetests?

Top discretetests alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "discretetests alternatives" section above for the current picks, or visit /alternatives/discretetests for the full list with editorial commentary on each.

What are the best alternatives to gpkg?

Top gpkg alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "gpkg alternatives" section above for the current picks, or visit /alternatives/gpkg for the full list with editorial commentary on each.