qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
Comparison · Analytics
austraits vs Fulcrum
A side-by-side editorial comparison of austraits and Fulcrum — release velocity, themes, recent moves, and the top alternatives to consider.
austraits vs Fulcrum: at a glance
| Feature | austraits | Fulcrum |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 0 |
| Top themes | plant-traits, open-data, ecology, zenodo | gis, esri-migration, offline-maps, field-data-capture |
| Last editorial update | 1h ago | 17h ago |
| Website | Visit → | — |
What is austraits?
The R client for AusTraits spends its releases chasing the dataset it reads.
austraits is the R access layer for the AusTraits plant trait database, and its release history is almost entirely a record of keeping pace with two upstream systems it does not control: the austraits.build data releases and the Zenodo archive that hosts them. The most recent release adds a version-dispatch layer so the same package can read both v4.x and v5.0.0 data. Three of the four visible tags were backfilled to GitHub within 23 minutes of each other, so version order and publication order do not agree.
What is Fulcrum?
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Fulcrum is a field data collection platform, and nearly every entry in the last month touches mapping. The web app ships weekly fix batches for layer rendering (KML/KMZ, MBTiles, ArcGIS Feature Services), while iOS and Android push near-weekly builds against the ArcGIS SDK. Feature work is thin right now; the visible surface is stabilization around a mapping engine migration already in flight.
austraits vs Fulcrum: editorial side-by-side
austraits
0.0ANALYTICS
The R client for AusTraits spends its releases chasing the dataset it reads.
◆ Current state
austraits is the R access layer for the AusTraits plant trait database, and its release history is almost entirely a record of keeping pace with two upstream systems it does not control: the austraits.build data releases and the Zenodo archive that hosts them. The most recent release adds a version-dispatch layer so the same package can read both v4.x and v5.0.0 data. Three of the four visible tags were backfilled to GitHub within 23 minutes of each other, so version order and publication order do not agree.
◆ Where it's heading
The package is converging on a stable public vocabulary and a versioned internal. Sites became locations across every join, plot and extract function; the extract_ and print family filled out at 1.0.0; and by 2.2.2 the core functions each carry a switch on the detected data version rather than assuming one schema. The visible cost of that is dependency churn — plotting packages moved to Suggests, which the notes admit can leave core functions unable to run.
◆ Prediction
Given that every release so far has been triggered by an upstream austraits.build or Zenodo change, the next one most likely follows the next data release rather than any independent roadmap. The entries do not indicate new analysis capability being planned in the client itself.
Fulcrum
6.3ANALYTICS
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
◆ Current state
Fulcrum is a field data collection platform, and nearly every entry in the last month touches mapping. The web app ships weekly fix batches for layer rendering (KML/KMZ, MBTiles, ArcGIS Feature Services), while iOS and Android push near-weekly builds against the ArcGIS SDK. Feature work is thin right now; the visible surface is stabilization around a mapping engine migration already in flight.
◆ Where it's heading
The direction is a full consolidation onto Esri. The legacy Google Maps engine is being retired on September 1 with automatic migration for anyone who hasn't switched, and Esri now carries Google's satellite and street basemaps so the imagery argument is neutralized. Underneath, the mobile SDK moved to ArcGIS 300.0.0 and ONNX on-device inference was dropped for a new INFERENCE format with labels.txt support. Offline is the second thread: downloadable layers can now be updated in place rather than deleted and recreated.
◆ Prediction
Expect the weeks before September 1 to stay dominated by migration-shaped fixes and Esri feature parity work, with the MMPK layer and Photo FastFill early-access programs the most likely to graduate to general availability next.
Alternatives to austraits and Fulcrum
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 austraits or Fulcrum.
constants
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
ggdemetra
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
fossilsim
A fossil-record simulator that quietly grew a trait-evolution engine.
tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
tern.mmrm
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
See all austraits alternatives → · See all Fulcrum alternatives →
Recent activity from austraits and Fulcrum
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoFulcrumWeb fixes: shared-view exports, MBTiles popups, KML and ArcGIS layers
- 3d agoFulcrumAndroid: update offline map layers in place, non-blocking Photo FastFill
- 4d agoFulcrumiOS fix: slow location resolution blocked record saves
- 9d agoFulcrumWeb: SSO email wording and ArcGIS/deck.gl version bumps
- 10d agoFulcrumAndroid fixes: ArcGIS stability, signature button, photo markup
- 10d agoFulcrumiOS fixes: basemap loading and black map screen
- 2y agoaustraitsSupport for AusTraits 5.0.0 data and the rebuilt Zenodo API
- 3y agoaustraitsextract_taxa, lookup_trait and print methods arrive
- 3y agoaustraitsVignette build and extract_ function polish
- 3y agoaustraitssite becomes location across the API; AusTraits 3.0.2+ support
Frequently asked questions
What is the difference between austraits and Fulcrum?
They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 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 austraits better than Fulcrum?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fulcrum is currently shipping more aggressively (velocity 6.3 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 austraits?
Top austraits alternatives in Analytics are ranked by recent ship velocity. Browse the "austraits alternatives" section above for the current picks, or visit /alternatives/austraits-r for the full list with editorial commentary on each.
What are the best alternatives to Fulcrum?
Top Fulcrum alternatives in Analytics are ranked by recent ship velocity. Browse the "Fulcrum alternatives" section above for the current picks, or visit /alternatives/fulcrum for the full list with editorial commentary on each.