rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
Comparison · Analytics
Fulcrum vs tidytransit
A side-by-side editorial comparison of Fulcrum and tidytransit — release velocity, themes, recent moves, and the top alternatives to consider.
Fulcrum vs tidytransit: at a glance
| Feature | Fulcrum | tidytransit |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | gis, esri-migration, offline-maps, field-data-capture | r, transit, gtfs, routing |
| Last editorial update | 13h ago | 1h ago |
| Website | — | Visit → |
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.
What is tidytransit?
tidytransit tracks the GTFS spec as it grows, one reader and one router feature at a time.
tidytransit reads GTFS transit feeds into tidy data frames and computes travel times using a RAPTOR implementation. Recent work splits between the reader keeping pace with the spec — locations.geojson in 1.7.0, empty strings parsed as NA in 1.8.0 — and the router gaining realism, most recently in-seat transfers. Feed specifications are now pulled from the automatically parsed GTFS reference rather than maintained by hand.
Fulcrum vs tidytransit: editorial side-by-side
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.
tidytransit
0.0ANALYTICS
tidytransit tracks the GTFS spec as it grows, one reader and one router feature at a time.
◆ Current state
tidytransit reads GTFS transit feeds into tidy data frames and computes travel times using a RAPTOR implementation. Recent work splits between the reader keeping pace with the spec — locations.geojson in 1.7.0, empty strings parsed as NA in 1.8.0 — and the router gaining realism, most recently in-seat transfers. Feed specifications are now pulled from the automatically parsed GTFS reference rather than maintained by hand.
◆ Where it's heading
The package has settled into tracking an external standard, which is why the changelog reads as a sequence of spec conformance items rather than a roadmap. Parsing responsibility keeps shifting outward to gtfsio, and data sources have moved with the ecosystem, from the retired transitfeeds API to MobilityData. Router changes are rarer than reader changes but land in the same releases.
◆ Prediction
Further GTFS spec features are the safest expectation, with GTFS-Flex the likeliest area now that locations.geojson reading is in place.
Alternatives to Fulcrum and tidytransit
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 Fulcrum or tidytransit.
epikit
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
mutagen
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
broman
A statistician's personal toolbox, growing one plotting utility at a time
qtl
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
See all Fulcrum alternatives → · See all tidytransit alternatives →
Recent activity from Fulcrum and tidytransit
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 22h 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
- 8d 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
- 6mo agotidytransitIn-seat transfers supported in raptor() and travel_times()
- 11mo agotidytransitstop_group_distances() no longer ignores the by parameter
- 1y agotidytransitlocations.geojson reading; specs parsed from the GTFS reference
- 2y agotidytransitfare_media_id added to fare_products spec
- 3y agotidytransitinterpolate_stop_times() added; router updated
- 3y agotidytransitDuplicated primary key check improved
Frequently asked questions
What is the difference between Fulcrum and tidytransit?
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 Fulcrum better than tidytransit?
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 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.
What are the best alternatives to tidytransit?
Top tidytransit alternatives in Analytics are ranked by recent ship velocity. Browse the "tidytransit alternatives" section above for the current picks, or visit /alternatives/tidytransit-r for the full list with editorial commentary on each.