a robust decoding and reporting system for WSPR
Please note: The wsprdaemon Timescale database is still in development, changes are likely, and the information below will reflect those changes.
10-15 May 2020: Major change in wsprdaemon v2.9 to add generated by wsprd meant change of table names. Previous tables are still there until 20 May 2020 for those not yet on 2.9.
After trying out Influx as our database for wspr spots and noise we settled on . In this application TimescaleDB required less CPU and disk resources to provide useful functionality. TimescaleDB is built upon , an open source full-featured relational database using SQL (structured Query Language).
There is the inevitability of jargon - our current implementation comprises:
• A single Database with the name 'tutorial'. Within that Database, we currently have four Tables:
• spots - comprising wspr spots scraped every six minutes from wsprnet.org.
• wsprdaemon_spots - comprising wspr spots uploaded by WsprDaemon users that choose to do so.
• wsprdaemon_noise - comprising noise spots uploaded by WsprDaemon users that choose to do so.
• kp - a geomagnetic disturbance index, scraped each day from NOAA's .
These postgeSQL Tables have been converted into Hypertables for use with TimescaleDB.
Each Hypertable has a Data Retention Policy (set by our Digital Ocean Droplet storage capacity):
• spots - data is kept for 30 days.
• wsprademon_spots - We have yet to set a retention period.
• wsprdaemon_noise - We have yet to set a retention period.
• kp - this is a tiny data set and no compression or retention policy is currently needed.
Check out our Guide by clicking the TimescaleDB logo.
This version covers installation of postgreSQL on your machine, how to gain access to the WsprDaemon database and sample Tables, together with numerous examples of simple SQL queries in 'Flat File' mode.