Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
A side-by-side editorial comparison of delaporte and Fulcrum — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | delaporte | Fulcrum |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 0 |
| Top themes | probability-distributions, count-data, fortran, openmp | gis, esri-migration, offline-maps, field-data-capture |
| Last editorial update | 2d ago | 16h ago |
| Website | Visit → | — |
A Fortran-backed Delaporte distribution package where every release is compiler and CRAN weather.
Delaporte supplies the density, distribution, quantile and random-generation functions for the Delaporte distribution — a Poisson-negative-binomial convolution used for overdispersed count data — implemented in Fortran and called through C. The only user-facing addition in the visible history is explicit OpenMP thread control via getDelapThreads() and setDelapThreads() at 8.2.0.
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. The newest iOS build turns to app-level responsiveness - database queries moved off the main path and the record editor kept interactive while Photo FastFill works in the background.
Delaporte supplies the density, distribution, quantile and random-generation functions for the Delaporte distribution — a Poisson-negative-binomial convolution used for overdispersed count data — implemented in Fortran and called through C. The only user-facing addition in the visible history is explicit OpenMP thread control via getDelapThreads() and setDelapThreads() at 8.2.0.
The maintenance burden here is portability, not statistics. Recent entries track a Fortran suffix change for Intel compiler compatibility, architecture-specific test tolerances, type-safety corrections on values crossing the C-to-Fortran boundary, and a thread-count variable relocated from R options to an environment variable to follow an upstream R commit. The distribution functions themselves are settled; what changes is how the compiled code is built and checked across CRAN's platform matrix.
Expect the next release to follow another CRAN toolchain or Writing R Extensions policy change, as the last several have. Two of the four visible entries carry no notes at all, so this feed will keep understating what actually shipped.
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. The newest iOS build turns to app-level responsiveness - database queries moved off the main path and the record editor kept interactive while Photo FastFill works in the background.
The direction is a full consolidation onto Esri. The legacy Google Maps engine retires on September 1 with automatic migration for anyone who has not 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 gave way to a new INFERENCE format. Two capabilities are visibly staged behind early access rather than shipped: Photo FastFill, and a GPS integration still described as Alpha.
Expect the weeks before September 1 to stay dominated by migration-shaped fixes and Esri parity work, with Photo FastFill the nearer of the two early-access programs to general availability given it is already running in shipped builds.
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 delaporte or Fulcrum.
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
A 4.4.0 tag appears, but the feed carries only its release plumbing
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
See all delaporte alternatives → · See all Fulcrum alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
Top delaporte alternatives in Analytics are ranked by recent ship velocity. Browse the "delaporte alternatives" section above for the current picks, or visit /alternatives/delaporte for the full list with editorial commentary on each.
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.