tibblify
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
Comparison · Analytics
geobounds vs glyanno
A side-by-side editorial comparison of geobounds and glyanno — release velocity, themes, recent moves, and the top alternatives to consider.
geobounds vs glyanno: at a glance
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.
What is glyanno?
Glycan annotation stops depending on the database having seen the structure before.
glyanno resolves mass spectrometry observations into glycan compositions and structures, converting between m/z, composition and structure, filling in missing detail on partial structures, and mapping results to GlyTouCan accessions. The newest release adds de novo reconstruction of topological N-glycans, falling back to the topological database only when reconstruction is not possible. Batch performance was reworked at the same time, with vector inputs reusing prepared databases and direct lookups instead of repeating setup per element.
geobounds vs glyanno: editorial side-by-side
geobounds
0.0ANALYTICS
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.
glyanno
3.8ANALYTICS
Glycan annotation stops depending on the database having seen the structure before.
◆ Current state
glyanno resolves mass spectrometry observations into glycan compositions and structures, converting between m/z, composition and structure, filling in missing detail on partial structures, and mapping results to GlyTouCan accessions. The newest release adds de novo reconstruction of topological N-glycans, falling back to the topological database only when reconstruction is not possible. Batch performance was reworked at the same time, with vector inputs reusing prepared databases and direct lookups instead of repeating setup per element.
◆ Where it's heading
The consistent theme is making ambiguous results honest and predictable. return_best moved from returning a shortened tibble to a vector aligned with the input, with NA for unmatched glycans; matching concrete compositions against a generic database now errors instead of silently returning nothing; zero-length database arguments are rejected. Alongside that, functions belonging elsewhere have been pushed down into glyrepr rather than duplicated, which is the same boundary discipline visible across this cohort. Version churn is largely driven by upstream: two of the last six entries exist to absorb breaking changes in glyrepr.
◆ Prediction
De novo reconstruction currently covers topological N-glycans only, so extending it to other structure levels or to O-glycans is the natural next step. The performance work suggests batch annotation of full experiments is now the primary use being optimised for.
Alternatives to geobounds and glyanno
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 glyanno.
spsurvey
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
StreamCatTools
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
reproducible
reproducible added a windowed read path so remote GeoTiffs never fully download
qcTAF
qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time
rpymat
After three dormant years, rpymat returned to fix the OpenMP crash that breaks R and conda together
See all geobounds alternatives → · See all glyanno alternatives →
Recent activity from geobounds and glyanno
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 24d agoglyannoDe novo reconstruction of topological N-glycans, with database fallback ⚡
- 1mo agogeoboundsPackage relicensed to MIT with per-source data terms
- 2mo agogeoboundsDocumentation terminology review
- 3mo agoglyannoGlyTouCan accession mapping and anomeric position filling
- 3mo agoglyannoFixes an enhance_struc() break from glyrepr 0.11.0
- 4mo agoglyannoExplicit empty return from com_to_struc()
- 4mo agoglyannoreturn_best output aligns with input length; silent empty matches now error
- 4mo agogeoboundsDocumentation moved to Quarto
- 5mo agoglyannoto_level parameter removed from enhance_struc()
- 6mo agogeoboundsDownload functions renamed and switched to shapefiles
- 9mo agogeoboundsInitial release
Frequently asked questions
What is the difference between geobounds and glyanno?
They serve adjacent needs but don't currently overlap on shipped themes. glyanno is currently shipping more aggressively (velocity 3.8 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 geobounds better than glyanno?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. glyanno is currently shipping more aggressively (velocity 3.8 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 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 glyanno?
Top glyanno alternatives in Analytics are ranked by recent ship velocity. Browse the "glyanno alternatives" section above for the current picks, or visit /alternatives/glyanno for the full list with editorial commentary on each.