← Back to home
Comparison · Analytics

duckspatial vs pedprobr

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

duckspatial vs pedprobr: at a glance

Featureduckspatialpedprobr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr, duckdb, geospatial, lazy evaluationpedigree analysis, likelihood computation, peeling algorithm, allele lumping
Last editorial update14m ago1h ago
WebsiteVisit →Visit →

What is duckspatial?

duckspatial rebuilt itself around a lazy DuckDB class, then spent four releases filling in the geometry surface

duckspatial exposes DuckDB's spatial extension to R. In March 2026 it stopped being an sf convenience wrapper: 1.0.0 made duckspatial_df the primary class, a lazy table-like object that stays in DuckDB until explicitly materialized. Every function accepts and returns it by default, with mode = 'sf' as the opt-out. The four releases since have added roughly forty geometry functions on top of that foundation.

Read the full duckspatial trajectory →

What is pedprobr?

pedprobr is the likelihood engine, and it keeps finding ways to compute what it previously could not.

pedprobr computes pedigree likelihoods for the ped suite. Version 1.1.0 updated its loop handling to match pedtools 2.11.0, including founder and repeated loop breakers, and improved the peeling algorithm with single-child shortcuts and lower memory use. Version 1.0.0 was the other expansion: special lumping lets markers with mutation models that are un-lumpable in the Kemeny-Snell sense be lumped anyway in certain cases, with alleleLimit as a fallback for the rest.

Read the full pedprobr trajectory →

duckspatial vs pedprobr: editorial side-by-side

D
duckspatial
ANALYTICS
0.0

duckspatial rebuilt itself around a lazy DuckDB class, then spent four releases filling in the geometry surface

◆ Current state

duckspatial exposes DuckDB's spatial extension to R. In March 2026 it stopped being an sf convenience wrapper: 1.0.0 made duckspatial_df the primary class, a lazy table-like object that stays in DuckDB until explicitly materialized. Every function accepts and returns it by default, with mode = 'sf' as the opt-out. The four releases since have added roughly forty geometry functions on top of that foundation.

◆ Where it's heading

The direction is to keep work inside DuckDB and make R the orchestration layer rather than the compute layer. 1.1.0 added macros so duckspatial functions work inside dplyr verbs; 1.1.1 moved the default to DuckDB v1.5.0 native spatial storage so CRS metadata persists in GEOMETRY columns; 1.2.0 added vector-tile output via ddbs_write_mbtiles() and the full family of geometry deserializers. Feature velocity has been high and consistent since the rewrite.

◆ Prediction

The remaining gaps are in PostGIS parity — the deserializers and tile writers landed in 1.2.0, so raster support or spatial indexing are the plausible next targets. 1.2.1 being a single message-capture fix suggests the 1.2.x line is now stabilizing.

P
pedprobr
ANALYTICS
0.0

pedprobr is the likelihood engine, and it keeps finding ways to compute what it previously could not.

◆ Current state

pedprobr computes pedigree likelihoods for the ped suite. Version 1.1.0 updated its loop handling to match pedtools 2.11.0, including founder and repeated loop breakers, and improved the peeling algorithm with single-child shortcuts and lower memory use. Version 1.0.0 was the other expansion: special lumping lets markers with mutation models that are un-lumpable in the Kemeny-Snell sense be lumped anyway in certain cases, with alleleLimit as a fallback for the rest.

◆ Where it's heading

Every significant release here removes a class of computation that used to be infeasible, either by making a marker lumpable or by making a loop breakable. The rest is steady peeling-algorithm optimization, which has been reducing memory footprint release after release since 0.9.2. The newly added .diagnostics option suggests the peeling internals are now complex enough that the maintainer needs to inspect them.

◆ Prediction

Since special lumping is documented as covering only some cases so far, expect further lumping situations to be implemented as pedmut adds them.

Alternatives to duckspatial and pedprobr

Other Analytics 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 duckspatial or pedprobr.

See all duckspatial alternatives → · See all pedprobr alternatives →

Recent activity from duckspatial and pedprobr

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

  1. 1mo agoduckspatialCapture install and load output messages
  2. 1mo agoduckspatialVector-tile output, geometry parsers and precision control
  3. 1mo agoduckspatialShortest-line, azimuth, vertex and coordinate-extreme functions
  4. 1mo agopedprobrLoop handling updated for pedtools' new loop breakers
  5. 2mo agoduckspatialNative spatial storage becomes the default connection format
  6. 2mo agoduckspatialduckspatial macros usable inside dplyr verbs
  7. 4mo agoduckspatialduckspatial_df replaces sf as the default class
  8. 1y agopedprobrCRAN example rounding fix
  9. 1y agopedprobrSpecial lumping for previously un-lumpable mutation models
  10. 1y agopedprobrGenotype distributions gain sparse and table output
  11. 2y agopedprobrPeeling order bug fix
  12. 2y agopedprobrPartial genotype fix for singletons

Frequently asked questions

What is the difference between duckspatial and pedprobr?

They serve adjacent needs but don't currently overlap on shipped themes. duckspatial and pedprobr 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 duckspatial better than pedprobr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. duckspatial and pedprobr 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 Analytics products to evaluate alongside.

What are the best alternatives to duckspatial?

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

What are the best alternatives to pedprobr?

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