← Back to home
Comparison · Infra & APIs

ShortForm vs usmapdata

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

ShortForm vs usmapdata: at a glance

FeatureShortFormusmapdata
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themespsychometrics, scale-construction, optimization-algorithms, lavaanr-packages, geospatial, census-data, cartography
Last editorial update2h ago39m ago
WebsiteVisit →Visit →

What is ShortForm?

Automated scale shortening with lavaan, spending its releases repairing its own search algorithms.

ShortForm automates the creation of short-form psychometric scales by searching for well-fitting subsets of items, using ant colony optimization, simulated annealing and Tabu search over lavaan models. The recent releases are corrective: 0.5.7 fixed the ant colony algorithm failing to update its best model and the simulated annealing routine mis-specifying models containing factor relationships or outcome variables, and 0.5.8 fixed Tabu search under parallel workflows and with multidimensional models. Each release note carries an explicit roadmap listing refactoring for 0.6.0 and input standardisation for 0.7.0, neither of which has shipped.

Read the full ShortForm 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 →

ShortForm vs usmapdata: editorial side-by-side

S
ShortForm
INFRA · APIS
0.0

Automated scale shortening with lavaan, spending its releases repairing its own search algorithms.

◆ Current state

ShortForm automates the creation of short-form psychometric scales by searching for well-fitting subsets of items, using ant colony optimization, simulated annealing and Tabu search over lavaan models. The recent releases are corrective: 0.5.7 fixed the ant colony algorithm failing to update its best model and the simulated annealing routine mis-specifying models containing factor relationships or outcome variables, and 0.5.8 fixed Tabu search under parallel workflows and with multidimensional models. Each release note carries an explicit roadmap listing refactoring for 0.6.0 and input standardisation for 0.7.0, neither of which has shipped.

◆ Where it's heading

The defects being fixed are in the search itself rather than around it. An optimizer that does not correctly retain its best candidate, and a search that mis-specifies models after the first iteration, both produce plausible-looking short forms that are not the ones the method should have found, which is a harder class of problem to notice than a crash. Alongside that the package is shedding dependencies, with ggplot2, ggrepel and tidyr dropped from the plotting methods in 0.5.8. The stated intent to refactor the major functions and standardise their arguments suggests the maintainer regards the current interface as the obstacle to further work.

◆ Prediction

The roadmap repeated across these notes points to a 0.6.0 focused on refactoring the major functions, with argument and output standardisation deferred to 0.7.0. On the evidence of this window, more unit tests and further algorithm-level fixes are likelier to arrive first than either milestone.

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

See all ShortForm alternatives → · See all usmapdata alternatives →

Recent activity from ShortForm and usmapdata

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

  1. 23d agousmapdata2025 Census shapefiles added
  2. 3mo agoShortFormTabu search fixed for parallel and multidimensional models
  3. 3mo agoShortFormAnt colony search failed to retain its best model
  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 agousmapdatadata_year turns the package into a multi-vintage archive
  8. 1y agoShortFormlavaan model specification defaults made forgiving
  9. 2y agoShortFormCompatibility fixes for a new lavaan release
  10. 2y agoShortFormAdapted to changed lavaan error and warning messages
  11. 2y agousmapdataMap data moves to 2023 shapefiles
  12. 2y agoShortFormDefault specification tweaks and documentation fixes

Frequently asked questions

What is the difference between ShortForm 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 ShortForm 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 ShortForm?

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