← Back to home
Comparison · Analytics

geobounds vs ribd

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

geobounds vs ribd: at a glance

Featuregeoboundsribd
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themesgeospatial, administrative boundaries, licensing, r packagesstatistical-genetics, pedigree-analysis, relatedness-coefficients, r-packages
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is geobounds?

geobounds relicensed to MIT and drew a line between its code and the data it downloads.

geobounds is an R client for the geoBoundaries administrative boundary database. Version 1.0.0 relicensed the package itself from CC BY 4.0 to MIT while documenting that downloaded boundaries keep their own terms, including differing gbOpen licenses, UN OCHA conditions, and the non-commercial restriction on UN SALB data. The functional groundwork came in 0.1.0, which renamed the download functions to object_verb() form, switched the source files from GeoJSON to shapefiles, and added retry handling.

Read the full geobounds trajectory →

What is ribd?

The pedsuite's coefficient engine: broadening what it computes, then making the plots publishable.

ribd computes relatedness coefficients from pedigrees, covering kinship, inbreeding, kappa, condensed and detailed identity coefficients, and two-locus versions of several of these, in autosomal and X-chromosomal form. The IBD triangle is now drawable in base graphics, ggplot2 or plotly, with an optional inset pedigree, and custom relationships can be placed on it. The most recent release is dominated by correctness work, fixing pair ordering and row alignment in coefficient tables and edge cases for pedigree lists, unrelated individuals and self-pairs.

Read the full ribd trajectory →

geobounds vs ribd: editorial side-by-side

G
geobounds
ANALYTICS
0.0

geobounds relicensed to MIT and drew a line between its code and the data it downloads.

◆ Current state

geobounds is an R client for the geoBoundaries administrative boundary database. Version 1.0.0 relicensed the package itself from CC BY 4.0 to MIT while documenting that downloaded boundaries keep their own terms, including differing gbOpen licenses, UN OCHA conditions, and the non-commercial restriction on UN SALB data. The functional groundwork came in 0.1.0, which renamed the download functions to object_verb() form, switched the source files from GeoJSON to shapefiles, and added retry handling.

◆ Where it's heading

The package is following rOpenSci conventions closely: the function renaming cited the developer guide directly, and 1.0.0 pairs a permissive code license with explicit, per-source attribution guidance rather than a blanket statement. That distinction matters for a client whose value is entirely in redistributing third-party geodata. Feature work has slowed since 0.1.0 in favor of licensing, documentation, and test isolation.

◆ Prediction

With licensing settled and the API renamed, the next releases most likely track upstream geoBoundaries data releases and boundary coverage rather than changing the interface again.

R
ribd
ANALYTICS
2.5

The pedsuite's coefficient engine: broadening what it computes, then making the plots publishable.

◆ Current state

ribd computes relatedness coefficients from pedigrees, covering kinship, inbreeding, kappa, condensed and detailed identity coefficients, and two-locus versions of several of these, in autosomal and X-chromosomal form. The IBD triangle is now drawable in base graphics, ggplot2 or plotly, with an optional inset pedigree, and custom relationships can be placed on it. The most recent release is dominated by correctness work, fixing pair ordering and row alignment in coefficient tables and edge cases for pedigree lists, unrelated individuals and self-pairs.

◆ Where it's heading

The arc runs from generality to presentation to precision. Early releases replaced narrow functions with general ones, most visibly when gKinship() absorbed generalisedKinship() and identityCoefs() superseded the separate autosomal and X-chromosomal identity functions in favour of an Xchrom argument. The middle stretch turned the IBD triangle into a proper plotting surface across three graphics systems. The current phase reads as consolidation, with the newest release listing six bug fixes against four features, several of them alignment errors in output tables, which is where a coefficient library most needs to be exactly right.

◆ Prediction

The two new internal functions in the latest release, inbreedingContributions() and ancestralKinship(), are the kind of thing that surfaces publicly a release or two later, so expect them to become exported decomposition tools. The correctness push through pedigree lists and edge cases suggests the near-term focus stays on hardening rather than new coefficient families.

Alternatives to geobounds and ribd

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 geobounds or ribd.

See all geobounds alternatives → · See all ribd alternatives →

Recent activity from geobounds and ribd

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

  1. 12d agoribdCustom relationships on the IBD triangle; six alignment and edge-case fixes
  2. 1mo agogeoboundsPackage relicensed to MIT with per-source data terms
  3. 2mo agogeoboundsDocumentation terminology review
  4. 4mo agogeoboundsDocumentation moved to Quarto
  5. 6mo agogeoboundsDownload functions renamed and switched to shapefiles
  6. 9mo agogeoboundsInitial release
  7. 1y agoribdkappaIBD() can skip across-component pairs on large pedigrees
  8. 2y agoribdIBD triangle plots gain ggplot2 and plotly backends, plus inset pedigrees
  9. 3y agoribdTriangle line clipping, automatic plot margins, citation info
  10. 3y agoribdTwo-locus functions overhauled; twoLocusInbreeding and ELR added
  11. 4y agoribdIdentity coefficients unified behind identityCoefs() and an Xchrom argument

Frequently asked questions

What is the difference between geobounds and ribd?

They serve adjacent needs but don't currently overlap on shipped themes. ribd is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 geobounds better than ribd?

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

What are the best alternatives to geobounds?

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

What are the best alternatives to ribd?

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