← Back to home
Comparison · Infra & APIs

coga vs usmap

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

coga vs usmap: at a glance

Featurecogausmap
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesprobability-distributions, gamma-convolution, rcpp, maintenance-modecartography, sf, data-packaging, fips
Last editorial update6h ago50m ago
WebsiteVisit →Visit →

What is coga?

A gamma-convolution density package that reached completion in 2018 and has coasted since.

coga computes densities, distribution functions and random numbers for convolutions of gamma distributions, with the numerical work in C++ through Rcpp. It has been feature-complete since 1.0.0 in 2018, and every release in the seven years since has been maintenance: a documentation alias for CRAN, a compiler warning, a maintainer email change, and an Rcpp update requiring Rf_error calls to be guarded. The one functional addition in that period, in 1.1.0, was an unexported function added explicitly for research use.

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

coga vs usmap: editorial side-by-side

C
coga
INFRA · APIS
0.0

A gamma-convolution density package that reached completion in 2018 and has coasted since.

◆ Current state

coga computes densities, distribution functions and random numbers for convolutions of gamma distributions, with the numerical work in C++ through Rcpp. It has been feature-complete since 1.0.0 in 2018, and every release in the seven years since has been maintenance: a documentation alias for CRAN, a compiler warning, a maintainer email change, and an Rcpp update requiring Rf_error calls to be guarded. The one functional addition in that period, in 1.1.0, was an unexported function added explicitly for research use.

◆ Where it's heading

This is a finished package being kept alive rather than developed. The releases track external pressure exactly: CRAN documentation requirements, compiler warnings, Rcpp API changes. Its maintenance is visibly shared with smam, the same maintainer's animal-movement package, which received the same email update, the same format-security fix and the same Rcpp guard within a minute or twenty of coga each time. Neither package is being extended; both are being kept installable.

◆ Prediction

Expect nothing but CRAN and toolchain maintenance, arriving whenever Rcpp or R's check requirements change, and arriving alongside smam. There is no signal in these entries of planned functional work.

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

See all coga alternatives → · See all usmap alternatives →

Recent activity from coga and usmap

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

  1. 5mo agocogaRcpp attributes regenerated; email updated
  2. 11mo agousmapPuerto Rico added across every usmap function and map year
  3. 1y agousmapdata_year parameter threaded through the plotting functions
  4. 2y agousmapPopulation and poverty data refreshed; ggplot2 3.5 legend fix
  5. 2y agousmapMap data becomes sf; usmap_transform() returns geometry
  6. 2y agocogaMaintainer email updated
  7. 2y agousmapDocumentation links updated
  8. 2y agousmapMap data extracted to a companion usmapdata package
  9. 2y agocogaCompiler format-security warning resolved
  10. 3y agocogaPackage documentation alias added for CRAN
  11. 6y agocogaUnexported density variant added for research use
  12. 8y agocoga1.0.0 declares the package complete and documented

Frequently asked questions

What is the difference between coga and usmap?

They serve adjacent needs but don't currently overlap on shipped themes. coga 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 coga better than usmap?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. coga 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 coga?

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