← Back to home
Comparison · Infra & APIs

prospectr vs usmap

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

prospectr vs usmap: at a glance

Featureprospectrusmap
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesspectroscopy, signal-processing, preprocessing, calibration-samplingcartography, sf, data-packaging, fips
Last editorial update4h ago1h ago
WebsiteVisit →Visit →

What is prospectr?

prospectr spent its biggest release in years fixing spectra it had been quietly mangling.

prospectr provides the signal-processing layer for near-infrared and visible spectroscopy in R — Savitzky-Golay and gap-segment derivatives, standard normal variate, detrending, continuum removal, splice correction, plus calibration sampling algorithms like Kennard-Stone and DUPLEX and readers for ASD and BUCHI NIRCal instrument files. The May release is the substantial one: a long list of corrections to functions that were returning wrong or missing values rather than failing.

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

prospectr vs usmap: editorial side-by-side

P
prospectr
INFRA · APIS
0.0

prospectr spent its biggest release in years fixing spectra it had been quietly mangling.

◆ Current state

prospectr provides the signal-processing layer for near-infrared and visible spectroscopy in R — Savitzky-Golay and gap-segment derivatives, standard normal variate, detrending, continuum removal, splice correction, plus calibration sampling algorithms like Kennard-Stone and DUPLEX and readers for ASD and BUCHI NIRCal instrument files. The May release is the substantial one: a long list of corrections to functions that were returning wrong or missing values rather than failing.

◆ Where it's heading

The recent work is corrective rather than additive, and several items changed results silently before being caught. continuumRemoval() derived its convex-hull boundary offset from a fixed one-wavelength assumption that broke for fine-resolution spectra or non-nanometre units; cochranTest() passed an invalid argument name to prcomp() and produced incorrect principal component scores; readASD() silently dropped spectra in one branch of its text path. Two file readers were leaking connections. Alongside that runs a smaller thread of decoupling preprocessing steps from each other, most visibly detrend() gaining an snv argument so polynomial detrending can run without the SNV transform that Barnes et al. bundled with it.

◆ Prediction

The detrend() decoupling is the only recent addition and it fits a broader pipeline-composition direction, so similar separation of other bundled preprocessing steps is the plausible next move. The misspelled substraction argument now carries a deprecation warning, which schedules its removal for a future release.

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

See all prospectr alternatives → · See all usmap alternatives →

Recent activity from prospectr and usmap

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

  1. 1mo agoprospectrdetrend() can run without a prior SNV transformation
  2. 2mo agoprospectrContinuum removal, SNV and cochranTest corrected; readers stop leaking
  3. 11mo agousmapPuerto Rico added across every usmap function and map year
  4. 1y agousmapdata_year parameter threaded through the plotting functions
  5. 1y agoprospectrread_nircal() sample ID field fix
  6. 2y agousmapPopulation and poverty data refreshed; ggplot2 3.5 legend fix
  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. 3y agoprospectrNon-UTF8 sample IDs no longer become NA
  11. 4y agoprospectrkenStone() bug fix
  12. 4y agoprospectrread_nircal() execution failure fixed

Frequently asked questions

What is the difference between prospectr and usmap?

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

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

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