The Weak Signal Propagation Reporter Network is a group of amateur radio operators using K1JT's MEPT_JT digital mode to probe radio frequency propagation conditions using very low power (QRP/QRPp) transmissions. The software is open source, and the data collected are available to the public through this site.

On Saturday, Jan 10th, I had my transmit-only beacon that I wrote sending both a visual MEPT indicator (the MV that you can see in the attached image) and the WSPR beacon, and tried out a simple program that simultaneously records, and later makes an FFT display of that portion of the band.

It seems to work!

Recently installed the ICOM FL53 (250HZ) CW filter in the IC703. This works very well
and it's passband sits nicely centered at 1500 hz with zero IF Shift. This is very
convenient for WSPR QSO mode in USB with WSJT 7 as this is the default center for this mode.

I will be operating from my QTH on the island of Fuerteventura from January 13 - January 25.

This is a long overdue project.

Using the downloadable CSV data, it's pretty trivial to load the data into R for some decent analysis. I was able to load all 3+ million spots into a data frame, and I'm going to start to try to learn some things. My first pictures are trivial histograms of Received SNR, Transmitted Power, and SNR-Power (un-normalized path loss). These are across all 30m spots to date.

Documentation and software downloads of WSPR programs and other WSJT-related modes of Joe Taylor, K1JT, are available from the WSJT web site. The entire database of millions of WSPR spots is available for public download in comma-separated value (CSV) format compressed with the gzip and zip utilities. Each file contains the data for one calendar month of spots. The data begins with the initial release of WSPR in March, 2008. The file for the current month is updated automatically once per day in the early morning UTC, and the monthly historical files are re-generated once every month. Compressed file sizes range from 1-20MB.

2008-03 gz zip
2008-04 gz zip
2008-05 gz zip
2008-06 gz zip
2008-07 gz zip
2008-08 gz zip
2008-09 gz zip
2008-10 gz zip
2008-11 gz zip
2008-12 gz zip
2009-01 gz zip
2009-02 gz zip
2009-03 gz zip
2009-04 gz zip
2009-05 gz zip
2009-06 gz zip
2009-07 gz zip
2009-08 gz zip
2009-09 gz zip
2009-10 gz zip
2009-11 gz zip
2009-12 gz zip
2010-01 gz zip
2010-02 gz zip
2010-03 gz zip
2010-04 gz zip
2010-05 gz zip
2010-06 gz zip
2010-07 gz zip
2010-08 gz zip
2010-09 gz zip
2010-10 gz zip
2010-11 gz zip
2010-12 gz zip
2011-01 gz zip
2011-02 gz zip
2011-03 gz zip
2011-04 gz zip
2011-05 gz zip
2011-06 gz zip
2011-07 gz zip
2011-08 gz zip
2011-09 gz zip
2011-10 gz zip
2011-11 gz zip
2011-12 gz zip
2012-01 gz zip
2012-02 gz zip
2012-03 gz zip
2012-04 gz zip
2012-05 gz zip
2012-06 gz zip
2012-07 gz zip
2012-08 gz zip
2012-09 gz zip
2012-10 gz zip
2012-11 gz zip
2012-12 gz zip
2013-01 gz zip
2013-02 gz zip
2013-03 gz zip
2013-04 gz zip
2013-05 gz zip
2013-06 gz zip
2013-07 gz zip
2013-08 gz zip
2013-09 gz zip
2013-10 gz zip
2013-11 gz zip
2013-12 gz zip
2014-01 gz zip
2014-02 gz zip
2014-03 gz zip
2014-04 gz zip
2014-05 gz zip
2014-06 gz zip
2014-07 gz zip
2014-08 gz zip
2014-09 gz zip
2014-10 gz zip
2014-11 gz zip
2014-12 gz zip
2015-01 gz zip
2015-02 gz zip
2015-03 gz zip
2015-04 gz zip
2015-05 gz zip
2015-06 gz zip
2015-07 gz zip
2015-08 gz zip
2015-09 gz zip
2015-10 gz zip
2015-11 gz zip
2015-12 gz zip
2016-01 gz zip
2016-02 gz zip
2016-03 gz zip
2016-04 gz zip
2016-05 gz zip
2016-06 gz zip
2016-07 gz zip
2016-08 gz zip
2016-09 gz zip
2016-10 gz zip
2016-11 gz zip
2016-12 gz zip
2017-01 gz zip
2017-02 gz zip
2017-03 gz zip
2017-04 gz zip
2017-05 gz zip
2017-06 gz zip
2017-07 gz zip
2017-08 gz zip
2017-09 gz zip
2017-10 gz zip

CSV File Format The fields in the CSV file are as follows:
Spot ID
A unique integer identifying the spot which otherwise carries no information. Used as primary key in the database table. Not all spot numbers exist, and the files may not be in spot number order
The time of the spot in unix time() format (seconds since 1970-01-01 00:00 UTC). To convert to an excel date value, use =time_cell/86400+"1/1/70" and then format it as a date/time.
The station reporting the spot. Usually an amateur call sign, but several SWLs have participated using other identifiers. Maximum of 10 characters.
Reporter's Grid
Maidenhead grid locator of the reporting station, in 4- or 6-character format.
Signal to noise ratio in dB as reported by the receiving software. WSPR reports SNR referenced to a 2500 Hz bandwidth; typical values are -30 to +20dB.
Frequency of the received signal in MHz
Call Sign
Call sign of the transmitting station. WSPR encoding of callsigns does not encode portable or other qualifying (slash) designators, so the call may not represent the true location of the transmitting station. Maximum of 6 characters.
Maidenhead grid locator of transmitting station, in 4- or 6-character format.
Power, as reported by transmitting station in the transmission. Units are dBm (decibels relative to 1 milliwatt; 30dBm=1W). Typical values are 0-50dBm, though a few are negative (< 1 mW).
The measured drift of the transmitted signal as seen by the receiver, in Hz/minute. Mostly of use to make the transmitting station aware of systematic drift of the transmitter. Typical values are -3 to 3.
Approximate distance between transmitter and receiver along the great circle (short) path, in kilometers. Computed form the reported grid squares.
Approximate direction, in degrees, from transmitting station to receiving station along the great circle (short) path.
Band of operation, computed from frequency as an index for faster retrieval. This may change in the future, but at the moment, it is just an integer representing the MHz component of the frequency with a special case for LF (-1: LF, 0: MF, 1: 160m, 3: 80m, 5: 60m, 7: 40m, 10: 30m, ...).
Version string of the WSPR software in use by the receiving station. May be bank, as versions were not reported until version 0.6 or 0.7, and version reporting is only done through the realtime upload interface (not the bulk upload).
Archives generated after 22 Dec 2010 have an additional integer Code field. Non-zero values will indicate that the spot is likely to be erroneous (bogus callsign, appears to be wrong band, appears to be an in-band mixing product, etc. When implemented, the specific codes will be documented here.

Hi all,

I looked in the database today and found sometimes a strong difference in receiving and transmitting level of some stations over the last months.

Can it be that the spotted TX power level in the database is not correct....

I am using ERP Scale ...5W ERP means around ...37dBm

73 de michael DG0OPK

Hello I would be interested to know what the operators on 160 are using?
I am currently loading up my hbrew Doublet,,, but plan to experiment with some other variations...

73 Rodger

I switched radios today to try my Tentec Corsair 2 on WSpr
and noticed it would not receive WSPR unless I received
on SB-R... Strange, I thought. Anybody else noticed
anthing like this? N9BPE

Having seen and read several posts regarding the puzzle of WSPR QSO mode operation, I found it puzzling that I hadn't had a lick of trouble figuring it out--now, I'm no rocket scientist so I figured there must be more to it--perhaps I was missing something.

Now I'm convinced that having used the JT65 mode in WSJT for a while prior to trying WSPR set the stage for the largely undocumented operation of WSPR in ver7.

What's the frequency for the 60 meterband?

73 de CX2ABP

is somebody activ on 136 khz ????
dial freq. ????

73 de IK4GBU - Valerio

Hi Folks!

Recapping on Frequency Accuracy
As you can see from previous entries in my blog I have been delving into why WSPR and ARGO report different audio frequencies with an error of 17Hz at 1500Hz.

If you look at my blogs below you will see I have been puzzled by a discrepancy between what ARGO and Spectran reports as the frequency of an audio tone supplied and what WSPR reports.

I have FINALLY figured out what is happening (I am sure others wiser than me already know this - but I didn't).

I believe the following database entries are bogus as they occurred during a period of severe mains line interference.

2008-12-24 21:36 O75YN 10.140273 -24 1 DM03 +20 0.100 VK2SRO QF56ik 12006 7460
2008-12-24 21:28 O89RRF 10.140174 +9 0 LK77 +47 50.119 VK2SRO QF56ik 11592 7203
2008-12-24 20:54 AF0DD 10.140256 -23 0 PL88 +23 0.200 VK2SRO QF56ik 7051 4381
2008-12-24 20:54 AC8KCS 10.140284 -17 0 JR94 +47 50.119 VK2SRO QF56ik 14141 8787