← Back to home
Comparison · Infra & APIs

usmapdata vs valr

A side-by-side editorial comparison of usmapdata and valr — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-packages

usmapdata vs valr: at a glance

Featureusmapdatavalr
SectorInfra & APIsInfra & APIs
Velocity score2.50.0
Sparks · 30d00
Top themesr-packages, geospatial, census-data, cartographygenomics, interval-arithmetic, bioinformatics, bigwig
Last editorial update2h ago1h ago
WebsiteVisit →Visit →

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.

Read the full usmapdata trajectory →

What is valr?

valr's interval verbs now read genomic files in place instead of demanding a loaded tibble.

valr reimplements bedtools-style genome interval arithmetic as tidyverse verbs backed by C++. Its long project has been closing the behavioural gap with bedtools — the book-ended interval semantics finally match in 0.10.0, three releases after the deprecation began. The July release also ends the assumption that intervals must be in memory: bed_map(), bed_intersect(), bed_subtract(), bed_coverage() and bed_window() accept a bigWig or bigBed path or URL where an interval table used to go.

Read the full valr trajectory →

usmapdata vs valr: editorial side-by-side

U
usmapdata
INFRA · APIS
2.5

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.

V
valr
INFRA · APIS
0.0

valr's interval verbs now read genomic files in place instead of demanding a loaded tibble.

◆ Current state

valr reimplements bedtools-style genome interval arithmetic as tidyverse verbs backed by C++. Its long project has been closing the behavioural gap with bedtools — the book-ended interval semantics finally match in 0.10.0, three releases after the deprecation began. The July release also ends the assumption that intervals must be in memory: bed_map(), bed_intersect(), bed_subtract(), bed_coverage() and bed_window() accept a bigWig or bigBed path or URL where an interval table used to go.

◆ Where it's heading

Two arcs converge here. One is compatibility: min_overlap arrived with a deprecation warning in 0.9.0 and its default flipped from 0 to 1 in 0.10.0, so book-ended intervals are excluded by default as bedtools does, with the internal calculations in bed_closest() and friends deliberately left counting them. The other is the file-backed path, which grew out of the cpp11bigwig dependency adopted in 0.8.3 for read_bigwig() and re-exported in 0.9.0 — reading a file became querying one. Underneath, the C++ base keeps getting lighter: Rcpp swapped for cpp11, rlang cut to a single function, per-group memory copies removed from three verbs.

◆ Prediction

Only five verbs take a file argument today and bed_closest(), bed_glyph() and the statistical verbs do not, so extending the file-backed path across the rest of the API is the obvious follow-up. The deprecated tibble re-exports and the now-defunct n_fields argument suggest continued removal of the compatibility layer in the next minor release.

Alternatives to usmapdata and valr

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 usmapdata or valr.

See all usmapdata alternatives → · See all valr alternatives →

Recent activity from usmapdata and valr

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 23d agousmapdata2025 Census shapefiles added
  2. 1mo agovalrInterval verbs read bigWig and bigBed files directly
  3. 7mo agovalrbed_slop() and bed_flank() preserve input row order
  4. 8mo agovalrmin_overlap introduced; C++ backend moves from Rcpp to cpp11
  5. 0y agousmapdataPuerto Rico added across every map vintage
  6. 1y agovalrTest updated for ggplot2 3.6.0
  7. 1y agousmapdataus_map() returns a data frame instead of a tibble
  8. 1y agousmapdata2024 Census shapefiles added
  9. 1y agousmapdatadata_year turns the package into a multi-vintage archive
  10. 1y agovalrread_bigwig() switches to cpp11bigwig; read_gtf() deprecated
  11. 1y agovalrCRAN Rd link NOTE and maintainer email change
  12. 2y agousmapdataMap data moves to 2023 shapefiles

Frequently asked questions

What is the difference between usmapdata and valr?

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 usmapdata better than valr?

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 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.

What are the best alternatives to valr?

Top valr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "valr alternatives" section above for the current picks, or visit /alternatives/valr for the full list with editorial commentary on each.