← Back to home
Comparison · Analytics

FedData vs pkglite

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

FedData vs pkglite: at a glance

FeatureFedDatapkglite
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesropensci, geospatial, r-package, open-datar-packages, pharma-submissions, packaging, file-handling
Last editorial update4h ago1h ago
WebsiteVisit →Visit →

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 →

What is pkglite?

pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.

pkglite packs an R package into a single plain-text file and unpacks it again, the mechanism pharmaceutical submissions use to move source through systems that accept text but not archives. The API settled at 0.2.0 with file specification templates, `merge()` and `prune()`. Every release since has improved the same thing: the dictionary that decides whether a file is text or binary, most recently rebuilt from the file extensions found across 21,369 CRAN packages.

Read the full pkglite trajectory →

FedData vs pkglite: editorial side-by-side

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.

P
pkglite
ANALYTICS
0.0

pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.

◆ Current state

pkglite packs an R package into a single plain-text file and unpacks it again, the mechanism pharmaceutical submissions use to move source through systems that accept text but not archives. The API settled at 0.2.0 with file specification templates, `merge()` and `prune()`. Every release since has improved the same thing: the dictionary that decides whether a file is text or binary, most recently rebuilt from the file extensions found across 21,369 CRAN packages.

◆ Where it's heading

The failure mode this package cares about is silent — misclassify a binary file as text and the round trip corrupts it, misclassify text as binary and it bloats or drops. So the work is empirical rather than architectural: mine real packages for what extensions actually appear, then widen coverage where specific ecosystems break the pattern. Stan interfaces via rstan brought `src/Makevars` and `src/Makefile` handling; machine learning frameworks brought their own binary formats. Dependencies have gone the other way, with cli removed and replaced by internal equivalents.

◆ Prediction

Expect the next substantive release to widen file specification coverage again for whatever package family the maintainers find breaking the default discovery, since that has been the content of every non-maintenance release for four years.

Alternatives to FedData and pkglite

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

See all FedData alternatives → · See all pkglite alternatives →

Recent activity from FedData and pkglite

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

  1. 5mo agopkgliteMaintainer email and CI workflow updates
  2. 1y agoFedDataget_padus() updated to PAD-US 4.0
  3. 1y agoFedDataAnnual NLCD access added; get_nass() retired
  4. 1y agopkgliteHandles Stan-interfacing packages and ML binary formats
  5. 1y agopkgliteExtension dictionary rebuilt from 21,369 CRAN packages
  6. 2y agopkgliteTest helpers moved to helper.R
  7. 2y agoFedDatasp and raster dropped; everything returns terra or sf
  8. 3y agoFedDataGHCN moves to https; NHD handles empty and odd geometries
  9. 3y agoFedDataAll raster writing moves to terra
  10. 3y agoFedDataVersion 3 rebuilds on sf and cloud-optimised GeoTIFFs
  11. 3y agopkgliteMore file types recognised; cli dependency dropped
  12. 5y agopkgliteFile collections gain merge, prune, and a tests template

Frequently asked questions

What is the difference between FedData and pkglite?

They serve adjacent needs but don't currently overlap on shipped themes. FedData and pkglite 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 FedData better than pkglite?

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

What are the best alternatives to pkglite?

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