← Back to home
Comparison · Analytics

qqman vs wasserportal

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

qqman vs wasserportal: at a glance

Featureqqmanwasserportal
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesgwas, genomics, manhattan-plot, visualizationgroundwater-monitoring, web-scraping, thingsboard, iot-telemetry
Last editorial update1h ago8h ago
WebsiteVisit →Visit →

What is qqman?

The Manhattan-plot package for GWAS results, finished and dormant since 2017.

qqman does two things: manhattan() and qq() plots for genome-wide association study results. Its six visible releases run from 2014 to a single 2017 packaging fix, and the last release with any user-facing change shipped in 2015. The archive is non-monotonic — a 0.0.0 tag published after 0.1.1 archives the pre-package standalone script — so version order and publication order disagree.

Read the full qqman trajectory →

What is wasserportal?

A Berlin groundwater scraper grew a full IoT publishing pipeline in two days.

wasserportal scrapes groundwater and surface water monitoring data from Wasserportal Berlin — station metadata, water levels, quality series. For its first four years that was the whole product, with releases tracking the portal's own churn: a new API version in 2023, new three-letter variable codes, and a 2026 fix decoding pages as windows-1252 because the server declares UTF-8 but emits Latin-1. In June 2026 it added a ThingsBoard integration, then extended it to self-hosted instances two days later.

Read the full wasserportal trajectory →

qqman vs wasserportal: editorial side-by-side

Q
qqman
ANALYTICS
0.0

The Manhattan-plot package for GWAS results, finished and dormant since 2017.

◆ Current state

qqman does two things: manhattan() and qq() plots for genome-wide association study results. Its six visible releases run from 2014 to a single 2017 packaging fix, and the last release with any user-facing change shipped in 2015. The archive is non-monotonic — a 0.0.0 tag published after 0.1.1 archives the pre-package standalone script — so version order and publication order disagree.

◆ Where it's heading

The real development window was 2014 to 2015. The 0.1.2 release did the substantive work, replacing the assumption that SNPs are evenly distributed across chromosomes and handing users control of axis limits, labels and log transformation; 0.1.3 then added annotation by p-value threshold and top-SNP-per-chromosome. After that the package stops. Notably, the archival 0.0.0 entry records that the original script had confidence intervals on QQ plots and richer highlighting than the released package ever regained.

◆ Prediction

With one packaging fix in the last decade, these entries support no prediction of further releases. The package reads as complete for its narrow purpose rather than abandoned mid-arc.

W
wasserportal
ANALYTICS
0.0

A Berlin groundwater scraper grew a full IoT publishing pipeline in two days.

◆ Current state

wasserportal scrapes groundwater and surface water monitoring data from Wasserportal Berlin — station metadata, water levels, quality series. For its first four years that was the whole product, with releases tracking the portal's own churn: a new API version in 2023, new three-letter variable codes, and a 2026 fix decoding pages as windows-1252 because the server declares UTF-8 but emits Latin-1. In June 2026 it added a ThingsBoard integration, then extended it to self-hosted instances two days later.

◆ Where it's heading

The package is repositioning from a data-access library into the first half of a monitoring pipeline. 0.6.0 shipped push helpers, device discovery and cleanup, an importable dashboard and a GitHub Actions workflow; 0.7.0 immediately generalised the authentication so it works against self-hosted Community Edition rather than only the Cloud tier, and lifted the push from a five-station demo to the entire groundwater archive. The hardening detail in 0.7.0 — retries on 5xx, warnings when only one of two credentials is set — reads like a maintainer who has run this against a real deployment.

◆ Prediction

The obvious next step is extending the ThingsBoard path to the surface water stations, which the package has flagged as under-supported since 0.1.0. The entries show no other direction under construction.

Alternatives to qqman and wasserportal

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 qqman or wasserportal.

See all qqman alternatives → · See all wasserportal alternatives →

Recent activity from qqman and wasserportal

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

  1. 1mo agowasserportalSelf-hosted ThingsBoard support via JWT login
  2. 1mo agowasserportalThingsBoard integration turns the scraper into a pipeline
  3. 3mo agowasserportalwindows-1252 decoding fixes umlaut handling on Windows
  4. 3y agowasserportalExport and import functions for scraped datasets
  5. 3y agowasserportalAdapted to Wasserportal's new API version
  6. 4y agowasserportalTemperature parameter naming corrected
  7. 9y agoqqmanREADME image path fix for pandoc
  8. 11y agoqqmanAnnotate SNPs by p-value threshold or per-chromosome top hit
  9. 11y agoqqmanChromosome ticks stop assuming even SNP spacing; axis control opens up
  10. 12y agoqqmanArchival tag for the pre-package standalone script
  11. 12y agoqqmanVignette touch-up
  12. 12y agoqqmanZenodo archival tag, no code change

Frequently asked questions

What is the difference between qqman and wasserportal?

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

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

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

What are the best alternatives to wasserportal?

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