← Back to home
Comparison · Infra & APIs

formr vs usmapdata

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

Shared themes:r-packages

formr vs usmapdata: at a glance

Featureformrusmapdata
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themessurvey-research, rest-api, cran-release, opencpur-packages, geospatial, census-data, cartography
Last editorial update44m ago1h ago
WebsiteVisit →Visit →

What is formr?

formr's R client reached CRAN and moved its recommended path to the v1 REST API.

formr is the R-side client for formr.org, the open study framework used to run longitudinal and experience-sampling questionnaires. In May it reached CRAN for the first time, released in step with formr.org server v1.0.0, and the formr_api_* family built on the server's RESTful surface became the supported entry point. The three releases since have been repair work on the paths that move rendered output and API results.

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

formr vs usmapdata: editorial side-by-side

F
formr
INFRA · APIS
0.0

formr's R client reached CRAN and moved its recommended path to the v1 REST API.

◆ Current state

formr is the R-side client for formr.org, the open study framework used to run longitudinal and experience-sampling questionnaires. In May it reached CRAN for the first time, released in step with formr.org server v1.0.0, and the formr_api_* family built on the server's RESTful surface became the supported entry point. The three releases since have been repair work on the paths that move rendered output and API results.

◆ Where it's heading

The direction is consolidation around the v1 API while the legacy Classic path is left running but demoted in the vignette. The complication is that CRAN's requirements and the OpenCPU server's requirements pull against each other: CRAN review pushed rendering into tempdir() with random filenames, which broke rforms.org because the server fetches a fixed knit.html, and 1.1.2 had to put it back. The 1.2.0 note describes the same write-directory problem being solved in an OpenCPU-aware way rather than reverted, alongside making dependencies installable under WASM.

◆ Prediction

Two of the last three releases were regressions in the render path, so the OpenCPU-aware write directory in 1.2.0 is the change most likely to need follow-up. The Classic formr_results() path remains in the package with no removal date announced, and nothing in these entries indicates when that ends.

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

See all formr alternatives → · See all usmapdata alternatives →

Recent activity from formr and usmapdata

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

  1. 23d agousmapdata2025 Census shapefiles added
  2. 1mo agoformrOpenCPU-aware render directory and WASM-installable dependencies
  3. 2mo agoformrHotfix: rendered output returns to knit.html
  4. 2mo agoformrcalculate items no longer coerced to NA by as.numeric()
  5. 2mo agoformrv1.0.0 — first CRAN release
  6. 0y agousmapdataPuerto Rico added across every map vintage
  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. 2y agousmapdataMap data moves to 2023 shapefiles

Frequently asked questions

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

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