metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of FedData and teal.modules.hermes — release velocity, themes, recent moves, and the top alternatives to consider.
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.
teal.modules.hermes stopped publishing release notes before it stopped releasing.
All three recent tags are automation output: a bump from 0.1.3.9017 to 0.1.4, a pre-release merge whose body is a list of file-path updates and co-author trailers, and an empty commit. The most recent is from October 2022.
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.
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.
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.
All three recent tags are automation output: a bump from 0.1.3.9017 to 0.1.4, a pre-release merge whose body is a list of file-path updates and co-author trailers, and an empty commit. The most recent is from October 2022.
The tags share the insightsengineering date-stamp and [skip vbump] convention, so the feed reports pipeline events rather than package changes — the one package-relevant line across all three is scda moving to Suggests. Nothing here indicates ongoing development.
There is nothing in these entries to project from; the package's actual state would have to be read from its NEWS file or commit history.
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 teal.modules.hermes.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
See all FedData alternatives → · See all teal.modules.hermes alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. FedData and teal.modules.hermes 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. FedData and teal.modules.hermes 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.
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.
Top teal.modules.hermes alternatives in Analytics are ranked by recent ship velocity. Browse the "teal.modules.hermes alternatives" section above for the current picks, or visit /alternatives/teal-modules-hermes for the full list with editorial commentary on each.