← Back to home
Comparison · Analytics

crul vs FedData

A side-by-side editorial comparison of crul and FedData — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:ropensci

crul vs FedData: at a glance

FeaturecrulFedData
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themeshttp-client, async, mocking, ropensciropensci, geospatial, r-package, open-data
Last editorial update1h ago5h ago
WebsiteVisit →Visit →

What is crul?

crul took mocking back from webmockr and made it a property of the client itself

crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.

Read the full crul trajectory →

What is FedData?

FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.

FedData downloads and standardises US federal geospatial datasets — NLCD, NHD, NED, SSURGO, Daymet, GHCN, PAD-US, NASS — into consistent R objects. Two breaking majors define the current package: 3.0.0 moved returns to sf and raster and pulled data from cloud-optimised GeoTIFFs, and 4.0.0 finished the job by dropping sp and raster entirely for terra and sf. Recent releases are dataset refreshes, most recently PAD-US 4.0.

Read the full FedData trajectory →

crul vs FedData: editorial side-by-side

C
crul
ANALYTICS
0.0

crul took mocking back from webmockr and made it a property of the client itself

◆ Current state

crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.

◆ Where it's heading

The async surface has been the growth area for years — retries reached Async, AsyncVaried, AsyncQueue and HttpRequest in 1.4, AsyncQueue gained the response accessors in 1.2, and 1.5.0 wired async requests up to webmockr. The 1.6.0 change reverses that direction of dependency, and it landed within a minute of webmockr's own release severing its tie to vcr. Read together, the rOpenSci HTTP stack is being deliberately untangled so each package can be used without the others.

◆ Prediction

With mock() deprecated rather than removed, the next major release is the likely point of deletion. Expect the remaining work to follow the same decoupling theme rather than adding request features.

F
FedData
ANALYTICS
0.0

FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.

◆ Current state

FedData downloads and standardises US federal geospatial datasets — NLCD, NHD, NED, SSURGO, Daymet, GHCN, PAD-US, NASS — into consistent R objects. Two breaking majors define the current package: 3.0.0 moved returns to sf and raster and pulled data from cloud-optimised GeoTIFFs, and 4.0.0 finished the job by dropping sp and raster entirely for terra and sf. Recent releases are dataset refreshes, most recently PAD-US 4.0.

◆ Where it's heading

The package tracks two moving targets at once: the R spatial stack, which it has now fully migrated onto terra and sf, and the federal agencies whose URLs, file naming and hosting keep shifting. With the dependency migration finished, releases have shrunk to single-dataset updates such as annual NLCD and PAD-US 4.0, which suggests the structural work is done and the ongoing cost is data-source maintenance.

◆ Prediction

Expect continued small releases pinned to new vintages of the underlying federal datasets, plus fixes when an agency moves or reformats a source; no further dependency-level upheaval is visible in these entries.

Alternatives to crul and FedData

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 crul or FedData.

See all crul alternatives → · See all FedData alternatives →

Recent activity from crul and FedData

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1y agocrulMocking becomes a client parameter, independent of webmockr
  2. 1y agoFedDataget_padus() updated to PAD-US 4.0
  3. 1y agoFedDataAnnual NLCD access added; get_nass() retired
  4. 2y agocrulAsync requests become mockable through webmockr
  5. 2y agocrulDocumentation fixes and test helper tweak
  6. 2y agoFedDatasp and raster dropped; everything returns terra or sf
  7. 3y agoFedDataGHCN moves to https; NHD handles empty and odd geometries
  8. 3y agocrulHTTP retries reach the async classes
  9. 3y agoFedDataAll raster writing moves to terra
  10. 3y agocrulClearer error for mismatched urls and disk lengths
  11. 3y agoFedDataVersion 3 rebuilds on sf and cloud-optimised GeoTIFFs
  12. 4y agocrulAsyncQueue gains response accessors; results print as a summary

Frequently asked questions

What is the difference between crul and FedData?

Both compete on the same themes — ropensci — within Analytics. crul and FedData 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.

Is crul better than FedData?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. crul and FedData 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.

What are the best alternatives to crul?

Top crul alternatives in Analytics are ranked by recent ship velocity. Browse the "crul alternatives" section above for the current picks, or visit /alternatives/crul for the full list with editorial commentary on each.

What are the best alternatives to FedData?

Top FedData alternatives in Analytics are ranked by recent ship velocity. Browse the "FedData alternatives" section above for the current picks, or visit /alternatives/feddata for the full list with editorial commentary on each.