metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
Comparison · Analytics
admiraldev vs FedData
A side-by-side editorial comparison of admiraldev and FedData — release velocity, themes, recent moves, and the top alternatives to consider.
admiraldev vs FedData: at a glance
What is admiraldev?
The admiral family's toolbox package keeps absorbing infrastructure the main package used to carry.
admiraldev is the developer-facing utility layer beneath the {admiral} clinical-programming family: assertions, custom roxygen roclets, linter configuration and deprecation helpers. Recent releases have pulled shared machinery out of {admiral} itself, most recently the roxygen helper functions in 1.5.0. Its users are other package authors, not clinical programmers.
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.
admiraldev vs FedData: editorial side-by-side
admiraldev
0.0ANALYTICS
The admiral family's toolbox package keeps absorbing infrastructure the main package used to carry.
◆ Current state
admiraldev is the developer-facing utility layer beneath the {admiral} clinical-programming family: assertions, custom roxygen roclets, linter configuration and deprecation helpers. Recent releases have pulled shared machinery out of {admiral} itself, most recently the roxygen helper functions in 1.5.0. Its users are other package authors, not clinical programmers.
◆ Where it's heading
The arc is consolidation — each release moves one more piece of cross-package tooling into a single place and tightens the standards it enforces. 1.4.0 added an admiral_linters() configuration mandating cli::cli_abort() over stop() across the family, and 1.1.0 had already migrated the assertion layer to {cli} messaging. Breaking changes are routine here and are managed through an explicit four-phase deprecation process.
◆ Prediction
Expect further extraction of shared helpers from {admiral} into this package, and continued roxygen2 8.0.0 follow-through in the documentation tooling.
FedData
0.0ANALYTICS
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 admiraldev 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 admiraldev or FedData.
marquee
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
logrx
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
lobstr
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
GSODR
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
giscoR
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
See all admiraldev alternatives → · See all FedData alternatives →
Recent activity from admiraldev and FedData
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agoadmiraldevRoxygen helpers move out of admiral; date validation gains a real-date check
- 2mo agoadmiraldevMaintainer handover to Edoardo Mancini
- 7mo agoadmiraldevFamily-wide linter config lands; custom join wrappers removed
- 1y agoadmiraldevrdx_roclet extends roxygen with permitted/default and example tags
- 1y agoFedDataget_padus() updated to PAD-US 4.0
- 1y agoadmiraldevdeprecate_inform() wrapper and more flexible assertion arguments
- 1y agoFedDataAnnual NLCD access added; get_nass() retired
- 2y agoadmiraldevError and warning messaging migrates to cli
- 2y agoFedDatasp and raster dropped; everything returns terra or sf ⚡
- 3y agoFedDataGHCN moves to https; NHD handles empty and odd geometries
- 3y agoFedDataAll raster writing moves to terra
- 3y agoFedDataVersion 3 rebuilds on sf and cloud-optimised GeoTIFFs ⚡
Frequently asked questions
What is the difference between admiraldev and FedData?
They serve adjacent needs but don't currently overlap on shipped themes. admiraldev 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 admiraldev better than FedData?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. admiraldev 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 admiraldev?
Top admiraldev alternatives in Analytics are ranked by recent ship velocity. Browse the "admiraldev alternatives" section above for the current picks, or visit /alternatives/admiraldev 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.