tibblify
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
A side-by-side editorial comparison of geobounds and pedbuildr — release velocity, themes, recent moves, and the top alternatives to consider.
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.
pedbuildr reconstructs pedigrees from DNA, and it just got much faster at the search.
pedbuildr infers pedigree structure from marker data by scoring candidate pedigrees against likelihoods. Version 0.4.0 moved reconstruct() to mirai for parallel likelihood computation, deprecated the old numCores argument, and picked up the improved loop breaking from pedtools and pedprobr, which lets many complex looped pedigrees succeed where they previously failed. buildPeds() also got significantly faster in its default configuration where mating between lineally related individuals is disallowed.
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.
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.
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.
pedbuildr infers pedigree structure from marker data by scoring candidate pedigrees against likelihoods. Version 0.4.0 moved reconstruct() to mirai for parallel likelihood computation, deprecated the old numCores argument, and picked up the improved loop breaking from pedtools and pedprobr, which lets many complex looped pedigrees succeed where they previously failed. buildPeds() also got significantly faster in its default configuration where mating between lineally related individuals is disallowed.
The package is bounded by two costs: how many candidate pedigrees it enumerates and how expensive each likelihood is. The recent release attacks both, parallelizing the likelihoods and speeding up enumeration in the common case. The earlier 0.3.0 release worked on the other end, adding inbreeding limits and a proper result class so the output of a large search is manageable. Releases are infrequent, roughly three years apart in this window.
Expect the candidate generation side to receive the same attention the likelihood side just did, since search space size is the remaining bound on what pedbuildr can reconstruct.
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 pedbuildr.
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
reproducible added a windowed read path so remote GeoTiffs never fully download
qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time
After three dormant years, rpymat returned to fix the OpenMP crash that breaks R and conda together
See all geobounds alternatives → · See all pedbuildr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r packages — within Analytics. geobounds and pedbuildr 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. geobounds and pedbuildr 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.
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.
Top pedbuildr alternatives in Analytics are ranked by recent ship velocity. Browse the "pedbuildr alternatives" section above for the current picks, or visit /alternatives/pedbuildr for the full list with editorial commentary on each.