← Back to home
Comparison · Analytics

rtrek vs soilDB

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

Shared themes:r-package

rtrek vs soilDB: at a glance

FeaturertreksoilDB
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesstar-trek, web-scraping, datasets, api-clientsoil-data, usda-nasis, ssurgo, spatial-queries
Last editorial update1h ago6h ago
WebsiteVisit →Visit →

What is rtrek?

A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.

rtrek bundles Star Trek datasets — book series, timelines, episode transcripts, species and homeworlds, map tile sets — and layers live retrieval on top through memory_alpha() and memory_beta() plus their ma_* and mb_* helpers. Recent releases are almost entirely repairs to that retrieval layer as the source wikis change their page structure.

Read the full rtrek trajectory →

What is soilDB?

The R front door to USDA soil data finishes a long deprecation cleanup and turns local-first.

soilDB is the R access layer for USDA-NRCS soil data: NASIS local databases, Soil Data Access, SoilWeb coverage services, and a widening set of curated national grids. The 2.9.x line closed out a multi-release deprecation cycle — column aliases and stringsAsFactors are gone, R 4.1 is the floor, and the bundled sample profile collections were rebuilt against the new schema. Recent work has shifted from adding query functions to making existing ones faster and usable against local SQLite or GeoPackage copies.

Read the full soilDB trajectory →

rtrek vs soilDB: editorial side-by-side

R
rtrek
ANALYTICS
0.0

A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.

◆ Current state

rtrek bundles Star Trek datasets — book series, timelines, episode transcripts, species and homeworlds, map tile sets — and layers live retrieval on top through memory_alpha() and memory_beta() plus their ma_* and mb_* helpers. Recent releases are almost entirely repairs to that retrieval layer as the source wikis change their page structure.

◆ Where it's heading

The package's centre of gravity shifted once, at 0.2.0, from shipping static data to querying Memory Alpha and Memory Beta at runtime. Everything since has been the maintenance bill for that decision: HTML update fixes, parser improvements, portal retrieval bugs. Note that version numbers on this feed do not track time — 0.2.5 is stamped a year before 0.1.0, and three tags were backfilled within four minutes in November 2020 — so neither rank nor version ordering here indicates release sequence.

◆ Prediction

Expect the next release to fix retrieval against another Memory Alpha layout change, which is what the last four have done. The entries give no indication of new datasets or functions in progress.

S
soilDB
ANALYTICS
0.0

The R front door to USDA soil data finishes a long deprecation cleanup and turns local-first.

◆ Current state

soilDB is the R access layer for USDA-NRCS soil data: NASIS local databases, Soil Data Access, SoilWeb coverage services, and a widening set of curated national grids. The 2.9.x line closed out a multi-release deprecation cycle — column aliases and stringsAsFactors are gone, R 4.1 is the floor, and the bundled sample profile collections were rebuilt against the new schema. Recent work has shifted from adding query functions to making existing ones faster and usable against local SQLite or GeoPackage copies.

◆ Where it's heading

The arc points at offline and local-first workflows. downloadSSURGO() and createSSURGO() keep gaining arguments for building and querying local SSURGO databases, and the query internals were rewritten as common table expressions so identical code runs against the remote service or a local file. Coverage is widening in parallel: FY26 SoilWeb maps now reach most OCONUS surveys, while fetchHWSD() and fetchSOLUS() pull in datasets outside the core NASIS/SSURGO pair. Federal URL churn — EDIT, SoilWeb, S3-hosted geometry — is a recurring maintenance tax the package absorbs on users' behalf.

◆ Prediction

Expect the next releases to keep extending parallel and offline SSURGO handling, since LAPPLY.FUN has just opened the door to arbitrary parallel backends, and to fold more curated SoilWeb and FAO datasets behind fetch* wrappers.

Alternatives to rtrek and soilDB

Other Analytics 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 rtrek or soilDB.

See all rtrek alternatives → · See all soilDB alternatives →

Recent activity from rtrek and soilDB

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

  1. 1mo agosoilDBFY26 soil maps reach OCONUS; SSURGO downloads go parallel
  2. 4mo agosoilDBROSETTA v2 lands as the deprecated NASIS aliases are removed
  3. 10mo agosoilDBNASIS record IDs now retrievable through Soil Data Access
  4. 11mo agosoilDBSpatial queries can pull columns from non-spatial tables
  5. 1y agosoilDBNASIS 7.4.3 metadata, plus HWSD and a local cache in 2.8.10
  6. 1y agortrekMemory Alpha series portal retrieval fix
  7. 1y agosoilDBQuery internals rewritten as CTEs for local SQLite support
  8. 1y agortrekrtrek 0.5.1 release
  9. 2y agortrekParser improvements for wiki retrieval
  10. 2y agortrekDead external content and data dependencies removed
  11. 5y agortrekFixes for source website HTML changes
  12. 5y agortrekMemory Alpha and Memory Beta web APIs added

Frequently asked questions

What is the difference between rtrek and soilDB?

Both compete on the same themes — r-package — within Analytics. rtrek and soilDB 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 rtrek better than soilDB?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rtrek and soilDB 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 Analytics products to evaluate alongside.

What are the best alternatives to rtrek?

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

What are the best alternatives to soilDB?

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