← Back to home
Comparison · Infra & APIs

nzilbb.vowels vs usmapdata

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

nzilbb.vowels vs usmapdata: at a glance

Featurenzilbb.vowelsusmapdata
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themessociophonetics, linguistics, pca, r-packager-packages, geospatial, census-data, cartography
Last editorial update1h ago4h ago
WebsiteVisit →Visit →

What is nzilbb.vowels?

A vowel-analysis package trimming dependencies after an email address got it archived.

nzilbb.vowels supports sociophonetic vowel analysis — principal component analysis over vowel measurements, Procrustes comparison of loadings, and the plotting that goes with them. Three releases are visible, all in the 0.4.x line and all small. The substantive thread is dependency removal: vegan and gghalves have both been dropped in favour of code the package controls.

Read the full nzilbb.vowels trajectory →

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 →

nzilbb.vowels vs usmapdata: editorial side-by-side

N
nzilbb.vowels
INFRA · APIS
0.0

A vowel-analysis package trimming dependencies after an email address got it archived.

◆ Current state

nzilbb.vowels supports sociophonetic vowel analysis — principal component analysis over vowel measurements, Procrustes comparison of loadings, and the plotting that goes with them. Three releases are visible, all in the 0.4.x line and all small. The substantive thread is dependency removal: vegan and gghalves have both been dropped in favour of code the package controls.

◆ Where it's heading

The package is reducing what it relies on, and paying for it in small interface breaks — plot_correlation_counts() lost its half_violin argument and gained a points argument in the same move. The 0.4.2 notes also record that version 0.4.1 was archived by CRAN because the maintainer's email had become unreliable, prompting a switch to an institutional address. That is administrative rather than technical, but it explains why three closely spaced patches exist at all.

◆ Prediction

With the two external plotting and ordination dependencies gone and the maintainer address stabilised, the visible pressure that produced these releases is resolved. Nothing in the entries indicates what comes next, and the history is too short to read a feature direction from.

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.

Alternatives to nzilbb.vowels 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 nzilbb.vowels or usmapdata.

See all nzilbb.vowels alternatives → · See all usmapdata alternatives →

Recent activity from nzilbb.vowels and usmapdata

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

  1. 23d agousmapdata2025 Census shapefiles added
  2. 8mo agonzilbb.vowelsnzilbb.vowels 0.4.3
  3. 8mo agonzilbb.vowelsnzilbb.vowels 0.4.2
  4. 0y agousmapdataPuerto Rico added across every map vintage
  5. 1y agousmapdataus_map() returns a data frame instead of a tibble
  6. 1y agousmapdata2024 Census shapefiles added
  7. 1y agonzilbb.vowelsnzilbb.vowels 0.4.1
  8. 1y agousmapdatadata_year turns the package into a multi-vintage archive
  9. 2y agousmapdataMap data moves to 2023 shapefiles

Frequently asked questions

What is the difference between nzilbb.vowels and usmapdata?

They serve adjacent needs but don't currently overlap on shipped themes. 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 nzilbb.vowels 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 nzilbb.vowels?

Top nzilbb.vowels alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "nzilbb.vowels alternatives" section above for the current picks, or visit /alternatives/nzilbb-vowels 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.