← Back to home
Comparison · Infra & APIs

JointFPM vs usmap

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

JointFPM vs usmap: at a glance

FeatureJointFPMusmap
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, recurrent-events, parametric-models, api-stabilitycartography, sf, data-packaging, fips
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is JointFPM?

Recurrent-event modelling settles, with mean_no() promoted to stable.

JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.

Read the full JointFPM trajectory →

What is usmap?

Ten years in, US mapping splits its data out and finally adds Puerto Rico.

usmap plots US state and county maps in an Alaska- and Hawaii-inset projection and joins user data to them by FIPS code. Over the last two years it has been rebuilt underneath: the map data moved out to a companion usmapdata package, the geometry became sf, and a data_year parameter lets a plot match the vintage of the data being plotted. Version 1.0.0 marks ten years of the project and adds Puerto Rico across every function.

Read the full usmap trajectory →

JointFPM vs usmap: editorial side-by-side

J
JointFPM
INFRA · APIS
0.0

Recurrent-event modelling settles, with mean_no() promoted to stable.

◆ Current state

JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.

◆ Where it's heading

The arc runs from a working estimator toward a usable one: input validation and error messages first, then control over the numerical integration, then a summary method and pass-through arguments to the underlying rstpm2 fit. The latest release adds no code so much as a stability commitment to a function users were already calling.

◆ Prediction

With mean_no() stable, the next work most likely targets the prediction and standardization paths rather than the model fit itself.

U
usmap
INFRA · APIS
0.0

Ten years in, US mapping splits its data out and finally adds Puerto Rico.

◆ Current state

usmap plots US state and county maps in an Alaska- and Hawaii-inset projection and joins user data to them by FIPS code. Over the last two years it has been rebuilt underneath: the map data moved out to a companion usmapdata package, the geometry became sf, and a data_year parameter lets a plot match the vintage of the data being plotted. Version 1.0.0 marks ten years of the project and adds Puerto Rico across every function.

◆ Where it's heading

The package has separated what it draws from how it draws, and that separation is what makes the recent releases possible: annual map vintages ship in usmapdata without touching usmap, and Puerto Rico could be backfilled into every existing year at once. The remaining work is coverage and defaults rather than architecture, and the Puerto Rico exclusion default is already governed by an environment variable rather than a code change.

◆ Prediction

Expect the annual map vintage to keep arriving through usmapdata, with usmap itself changing only where a new territory or a projection default needs handling.

Alternatives to JointFPM and usmap

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 JointFPM or usmap.

See all JointFPM alternatives → · See all usmap alternatives →

Recent activity from JointFPM and usmap

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

  1. 11mo agousmapPuerto Rico added across every usmap function and map year
  2. 1y agoJointFPMmean_no() promoted to a stable interface
  3. 1y agousmapdata_year parameter threaded through the plotting functions
  4. 2y agoJointFPMsummary() method and control arguments passed to rstpm2
  5. 2y agousmapPopulation and poverty data refreshed; ggplot2 3.5 legend fix
  6. 2y agoJointFPMGaussian quadrature option for the mean-events integration
  7. 2y agousmapMap data becomes sf; usmap_transform() returns geometry
  8. 2y agousmapDocumentation links updated
  9. 2y agousmapMap data extracted to a companion usmapdata package
  10. 2y agoJointFPMStandardized marginal estimates plus input validation
  11. 2y agoJointFPMBug fixes for differences between mean-event functions

Frequently asked questions

What is the difference between JointFPM and usmap?

They serve adjacent needs but don't currently overlap on shipped themes. JointFPM and usmap are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is JointFPM better than usmap?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. JointFPM and usmap are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to JointFPM?

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

What are the best alternatives to usmap?

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