pr2database
The protist reference database keeps widening past the rRNA gene it was built on.
Comparison · Infra & APIs
sdcMicro vs usmap
A side-by-side editorial comparison of sdcMicro and usmap — release velocity, themes, recent moves, and the top alternatives to consider.
sdcMicro vs usmap: at a glance
What is sdcMicro?
A 20-year anonymization toolbox now has a language model inside its refinement loop.
sdcMicro is the reference R implementation of statistical disclosure control — k-anonymity, local suppression, PRAM, microaggregation, record swapping — used by national statistical offices, with a Shiny GUI (sdcApp) as its second face. The feed shows a long GUI-maintenance era through 2018-2022 and then a gap, and the package that reappears in 5.8.2 has an AI_applyAnonymization() workflow and a query_llm() helper that the older entries know nothing about. The July release tunes that loop rather than introducing it.
What is usmap?
Ten years in, US mapping splits its data out and finally adds Puerto Rico.
usmap plots US state and county maps in an Alaska- and Hawaii-inset projection and joins user data to them by FIPS code. Over the last two years it has been rebuilt underneath: the map data moved out to a companion usmapdata package, the geometry became sf, and a data_year parameter lets a plot match the vintage of the data being plotted. Version 1.0.0 marks ten years of the project and adds Puerto Rico across every function.
sdcMicro vs usmap: editorial side-by-side
sdcMicro
0.0INFRA · APIS
A 20-year anonymization toolbox now has a language model inside its refinement loop.
◆ Current state
sdcMicro is the reference R implementation of statistical disclosure control — k-anonymity, local suppression, PRAM, microaggregation, record swapping — used by national statistical offices, with a Shiny GUI (sdcApp) as its second face. The feed shows a long GUI-maintenance era through 2018-2022 and then a gap, and the package that reappears in 5.8.2 has an AI_applyAnonymization() workflow and a query_llm() helper that the older entries know nothing about. The July release tunes that loop rather than introducing it.
◆ Where it's heading
Two threads run in parallel. The visible one is the LLM-assisted anonymization path maturing: 5.8.2 gives its refinement loop early stopping via tol and patience so it stops when the combined utility score plateaus instead of burning all max_iter rounds, and teaches query_llm() to drop the temperature parameter for reasoning models that reject it. The other is unglamorous statistical correctness — a distinct l-diversity computation fixed for NAs in key variables, with the C++ simplified and tests added. The release also ships reproducibility scripts for a SoftwareX paper, which suggests the AI path is being written up rather than quietly trialled.
◆ Prediction
The provider-compatibility fix is reactive — a parameter dropped because one model family rejected it — so expect more of the same as query_llm() meets other backends. Given tol and patience were added to stop wasted iterations, cost or runtime of the refinement loop is the live concern, and further controls on it are the likeliest next move.
usmap
0.0INFRA · APIS
Ten years in, US mapping splits its data out and finally adds Puerto Rico.
◆ Current state
usmap plots US state and county maps in an Alaska- and Hawaii-inset projection and joins user data to them by FIPS code. Over the last two years it has been rebuilt underneath: the map data moved out to a companion usmapdata package, the geometry became sf, and a data_year parameter lets a plot match the vintage of the data being plotted. Version 1.0.0 marks ten years of the project and adds Puerto Rico across every function.
◆ Where it's heading
The package has separated what it draws from how it draws, and that separation is what makes the recent releases possible: annual map vintages ship in usmapdata without touching usmap, and Puerto Rico could be backfilled into every existing year at once. The remaining work is coverage and defaults rather than architecture, and the Puerto Rico exclusion default is already governed by an environment variable rather than a code change.
◆ Prediction
Expect the annual map vintage to keep arriving through usmapdata, with usmap itself changing only where a new territory or a projection default needs handling.
Alternatives to sdcMicro and usmap
Other Infra & APIs 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 sdcMicro or usmap.
ggalign
Composable aligned layouts, rebuilt on S7 while ggplot2 4.0 lands underneath.
prioritizr
Conservation planning absorbs the literature's target-setting rules as code.
jSDM
Joint species distribution models in Gibbs-sampled C++, quiet since 2023.
rsofun
An ecosystem model starts tracking carbon isotopes and land-use change.
trackeR
Fitness-tracking analysis in slow maintenance, still absorbing upstream breakage.
See all sdcMicro alternatives → · See all usmap alternatives →
Recent activity from sdcMicro and usmap
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agosdcMicroEarly stopping for the AI anonymization loop, plus GPT-5.x support
- 11mo agousmapPuerto Rico added across every usmap function and map year
- 1y agousmapdata_year parameter threaded through the plotting functions
- 2y agousmapPopulation and poverty data refreshed; ggplot2 3.5 legend fix
- 2y agousmapMap data becomes sf; usmap_transform() returns geometry ⚡
- 2y agousmapDocumentation links updated
- 2y agousmapMap data extracted to a companion usmapdata package ⚡
- 4y agosdcMicrorecordSwap() adds targeted record swapping
- 5y agosdcMicroTwo new information-loss measures and a run of sdcApp fixes
- 5y agosdcMicroCompatibility fixes for R 4.1 sorting and rsconnect deployment
- 8y agosdcMicroMinor release, mostly GUI work
- 8y agosdcMicrodUtility() corrected so IL1 and IL1s can be distinguished
Frequently asked questions
What is the difference between sdcMicro and usmap?
They serve adjacent needs but don't currently overlap on shipped themes. sdcMicro and usmap 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 sdcMicro better than usmap?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. sdcMicro and usmap 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to sdcMicro?
Top sdcMicro alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "sdcMicro alternatives" section above for the current picks, or visit /alternatives/sdcmicro for the full list with editorial commentary on each.
What are the best alternatives to usmap?
Top usmap alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "usmap alternatives" section above for the current picks, or visit /alternatives/usmap for the full list with editorial commentary on each.