← Back to home
Comparison · Infra & APIs

hereR vs PEIMAN2

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

hereR vs PEIMAN2: at a glance

FeaturehereRPEIMAN2
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesgeospatial, routing, api-client, r-packageproteomics, post-translational-modification, enrichment-analysis, reproducibility
Last editorial update1h ago6h ago
WebsiteVisit →Visit →

What is hereR?

An R client for HERE's location APIs, shaped almost entirely by what the vendor exposes next.

hereR wraps HERE's routing, isoline, traffic, weather and geocoding endpoints for R, returning sf objects. Development is steady and reactive: each release either adopts a transport mode, parameter or API version HERE has newly made available, or corrects a rate limit that was producing 429 errors in practice. The current release adds speed-limit control and five more isoline transport modes.

Read the full hereR trajectory →

What is PEIMAN2?

PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.

PEIMAN2 does enrichment analysis over post-translational modifications, testing whether a protein list is enriched for particular PTMs against UniProt-derived annotations, with translation functions bridging to mass spectrometry workflows. Its answers are only as current as its bundled database, and until June that database could only be refreshed by releasing a new package version. Version 1.1.0 changes that.

Read the full PEIMAN2 trajectory →

hereR vs PEIMAN2: editorial side-by-side

H
hereR
INFRA · APIS
0.0

An R client for HERE's location APIs, shaped almost entirely by what the vendor exposes next.

◆ Current state

hereR wraps HERE's routing, isoline, traffic, weather and geocoding endpoints for R, returning sf objects. Development is steady and reactive: each release either adopts a transport mode, parameter or API version HERE has newly made available, or corrects a rate limit that was producing 429 errors in practice. The current release adds speed-limit control and five more isoline transport modes.

◆ Where it's heading

Two threads run through the whole history. One is coverage — new modes, tolls and currency, arrival times, speed limits — arriving in the package shortly after they appear in HERE's API. The other is defensive operational tuning, with request rates repeatedly lowered below HERE's documented limits because the documented limits do not hold up. 1.0.0 was the one moment the package had to move rather than choose, migrating traffic to v7 and weather to v3 and breaking three functions' output in the process.

◆ Prediction

Expect the next release to enable whatever HERE exposes next in routing or isolines, and to keep adjusting request rates empirically; the package's own design appears settled.

P
PEIMAN2
INFRA · APIS
0.0

PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.

◆ Current state

PEIMAN2 does enrichment analysis over post-translational modifications, testing whether a protein list is enriched for particular PTMs against UniProt-derived annotations, with translation functions bridging to mass spectrometry workflows. Its answers are only as current as its bundled database, and until June that database could only be refreshed by releasing a new package version. Version 1.1.0 changes that.

◆ Where it's heading

The package has been moving from a fixed snapshot toward versioned, user-selectable data. Earlier releases updated the bundled database in place — 1.0.0 shipped the March 2025 version and said little else — which meant the annotation vintage was whatever the package version implied. Now update_peiman_database() downloads and caches external database files and UniProt PTM lists, enrichment workflows take a database_version argument, and the mass-spec translators take a ptmlist_version, so an analysis can pin a dated database rather than a package release. The CRAN-safe default is preserved deliberately: loading, examples and checks still use the bundled internal data and need no network.

◆ Prediction

Version pinning is now expressible but the release notes do not describe how a chosen version is recorded in output, so surfacing the active database version in results is the natural companion. The database and the UniProt PTM list are versioned separately, which leaves room for a combined manifest.

Alternatives to hereR and PEIMAN2

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 hereR or PEIMAN2.

See all hereR alternatives → · See all PEIMAN2 alternatives →

Recent activity from hereR and PEIMAN2

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

  1. 2mo agoPEIMAN2Database updates decouple from package releases
  2. 1y agoPEIMAN2Bundled database refreshed to the March 2025 UniProt vintage
  3. 1y agoPEIMAN2Documentation fix for the second example dataset
  4. 1y agohereRSpeed limits and five more isoline transport modes
  5. 1y agohereRPedestrian consumption model dropped; route request rate lowered
  6. 2y agohereRTraffic v7 and Weather v3 migration breaks three functions
  7. 2y agoPEIMAN2Background lists for SEA and PSEA; tidyverse dependency dropped
  8. 3y agohereRResubmission after CRAN archival over an undeliverable email
  9. 4y agohereRToll costs and currency selection arrive in routing
  10. 4y agohereRArrival-time routing enabled; failed requests report their endpoint

Frequently asked questions

What is the difference between hereR and PEIMAN2?

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

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

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

What are the best alternatives to PEIMAN2?

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