webchem
Adding chemical databases with one hand while public ones close programmatic access with the other.
A side-by-side editorial comparison of admiralophtha and FedData — release velocity, themes, recent moves, and the top alternatives to consider.
Ophthalmology ADaM support is migrating its derivations upstream into admiral core.
admiralophtha supplies ophthalmology-specific ADaM templates and vignettes — ADBCVA, ADOE, ADVFQ — on top of admiral. Releases arrive roughly twice a year and are dominated by template and vignette modernisation plus a long, deliberate deprecation of the package's own criterion-flag helper in favour of admiral::derive_vars_crit_flag(). The 1.5.0 release advances that deprecation to its warning phase and adds a template explorer.
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.
admiralophtha supplies ophthalmology-specific ADaM templates and vignettes — ADBCVA, ADOE, ADVFQ — on top of admiral. Releases arrive roughly twice a year and are dominated by template and vignette modernisation plus a long, deliberate deprecation of the package's own criterion-flag helper in favour of admiral::derive_vars_crit_flag(). The 1.5.0 release advances that deprecation to its warning phase and adds a template explorer.
The arc is consolidation: functions the package invented are being retired as admiral core grows generic equivalents, leaving admiralophtha as the place where ophthalmology conventions are documented. Recent releases spend their weight on templates and vignettes — VFQ guidance alignment, IOP parameter mapping, subject-key options — rather than new exported code. Deprecations are run on a fixed six-month, one-release-per-phase clock, which makes the migration path unusually legible.
derive_var_bcvacritxfl() should reach its error phase and then removal over the next two releases, with the accompanying work being ADBCVA vignette and template edits rather than new functions.
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.
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 admiralophtha or FedData.
Adding chemical databases with one hand while public ones close programmatic access with the other.
The spatiotemporal companion to sf, moving at the pace of the packages around it.
An interface to Europe's long-term ecosystem research network that went quiet after 2.0.
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.
Went from estimating felling dates to doing the crossdating that produces them.
See all admiralophtha alternatives → · See all FedData alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. admiralophtha 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. admiralophtha 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.
Top admiralophtha alternatives in Analytics are ranked by recent ship velocity. Browse the "admiralophtha alternatives" section above for the current picks, or visit /alternatives/admiralophtha for the full list with editorial commentary on each.
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.