ggpointless
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
Comparison · Infra & APIs
remap vs usmapdata
A side-by-side editorial comparison of remap and usmapdata — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-packages
remap vs usmapdata: at a glance
What is remap?
A regional-model smoother in long-term maintenance, four years past its last real feature.
remap fits separate models to geographic regions and blends their predictions into a continuous surface, using the min_n nearest observations so region boundaries do not show as discontinuities. The methodological work is finished — the last behavioural change landed in 2022, and everything since has been unit handling, compiler warnings, dependency compatibility and citation updates. The July release is one such patch.
What is usmapdata?
usmapdata ships its 2025 shapefiles on the year-indexed model it adopted in 0.4.0.
usmapdata supplies the boundary data behind usmap's plotting functions. Since 0.4.0 it has been year-indexed: us_map(data_year = ) selects a vintage, and each Census release is added as its own year with older ones still reachable. 1.1.0 adds 2025. 1.0.0 closed the package's longest-standing gap by adding Puerto Rico, retroactively across every vintage.
remap vs usmapdata: editorial side-by-side
remap
0.0INFRA · APIS
A regional-model smoother in long-term maintenance, four years past its last real feature.
◆ Current state
remap fits separate models to geographic regions and blends their predictions into a continuous surface, using the min_n nearest observations so region boundaries do not show as discontinuities. The methodological work is finished — the last behavioural change landed in 2022, and everything since has been unit handling, compiler warnings, dependency compatibility and citation updates. The July release is one such patch.
◆ Where it's heading
This is a stable academic package tracking its ecosystem rather than growing. The visible pattern is reactive maintenance: sf's 1.0.0 transition, ggplot2's size-to-linewidth rename, a gcc-UBSAN error on zero-point distance calculations, and now a check that distance matrices passed to remap() and predict() are converted to kilometres. Note that the feed's timestamps invert the version order — 0.3.1 is stamped seconds after 0.3.2 despite being the earlier release, so recency in this feed is not a reliable guide to sequence.
◆ Prediction
Nothing in these entries points to new capability. The realistic expectation is more of the same: a patch whenever sf, ggplot2 or a CRAN check surfaces an incompatibility, at roughly the observed cadence of one release every year or two.
usmapdata
2.5INFRA · APIS
usmapdata ships its 2025 shapefiles on the year-indexed model it adopted in 0.4.0.
◆ Current state
usmapdata supplies the boundary data behind usmap's plotting functions. Since 0.4.0 it has been year-indexed: us_map(data_year = ) selects a vintage, and each Census release is added as its own year with older ones still reachable. 1.1.0 adds 2025. 1.0.0 closed the package's longest-standing gap by adding Puerto Rico, retroactively across every vintage.
◆ Where it's heading
The package has settled into a predictable rhythm — one shapefile vintage per year, with structural change rare and clustered. The two changes that mattered were data_year in 0.4.0, which turned a single-vintage dataset into a time series, and the tibble-to-data-frame switch in 0.6.0 that reduced what downstream callers have to depend on.
◆ Prediction
The stated policy — each year added going forward, previous years reachable through data_year — points to a 2026 vintage as the next release. Nothing in these notes suggests further change to the data model.
Alternatives to remap and usmapdata
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 remap or usmapdata.
mpactr
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
surveytidy
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveycore
surveycore declared its API stable with every survey design type covered.
PEIMAN2
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
prospectr
prospectr spent its biggest release in years fixing spectra it had been quietly mangling.
See all remap alternatives → · See all usmapdata alternatives →
Recent activity from remap and usmapdata
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23d agousmapdata2025 Census shapefiles added
- 1mo agoremapDistance matrices now converted to kilometres automatically
- 0y agousmapdataPuerto Rico added across every map vintage
- 1y agousmapdataus_map() returns a data frame instead of a tibble
- 1y agousmapdata2024 Census shapefiles added
- 1y agousmapdatadata_year turns the package into a multi-vintage archive ⚡
- 1y agoremapCitation updated to the R Journal article
- 1y agoremapUBSAN fix, parallel patch and sf search-path independence
- 2y agousmapdataMap data moves to 2023 shapefiles
- 3y agoremappredict() can return an upper bound on combined standard errors
- 5y agoremapRegions without observations no longer break the prediction surface
Frequently asked questions
What is the difference between remap and usmapdata?
Both compete on the same themes — r-packages — within Infra & APIs. usmapdata is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is remap better than usmapdata?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. usmapdata is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to remap?
Top remap alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "remap alternatives" section above for the current picks, or visit /alternatives/remap for the full list with editorial commentary on each.
What are the best alternatives to usmapdata?
Top usmapdata alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "usmapdata alternatives" section above for the current picks, or visit /alternatives/usmapdata for the full list with editorial commentary on each.