Re: I'm looking for FST4W signals


Gwyn Griffiths
 

Rob, Jim
I hope to bring some light and not add to the confusion. There are, to my mind, three sources of confusion:
1. The wsprnet database team repurposed an existing field to signify the new modes, so the meaning of the numbers in the database field 'code' has changed.
2. Reporters running older wsjt-x software will still be uploading numbers into the code field that reflect its previous usage.
3. It is only Gary's post #13 in the thread  that gives the mapping between the database value for code and the mode (which is what one searches for on the wsprnet.org page), he wrote:

"So that code:1 means WSPR-2. I need to update the doc on the github, but it's still a bit of moving target and I don't want to create more updates when it changes. It's code = 1,2,4,8 for WSPR-2, WSPR-15, /300, /1800 respectively.

Since we are using the column `code` to avoid a schema change I am mapping it to the mode values and there are more changes coming. I know it's not ideal, but it will work for us. It is in the CSV daily dumps, too, and at least for now I have no plans to remap them."

So, for FST4W /300 for example querying the wsprnet database table spots on one of the wsprdaemon servers with 

select * from spots where wd_band='630' and code =4 order by wd_time desc limit 1;

gives

       wd_time       |  Spotnum   |    Date    | Reporter  | ReporterGrid | dB  |   MHz    | CallSign |  Grid  | Power | Drift | distance | azimuth | Band |  version   | code | wd_band | wd_c2_noise | wd_rms_noise | wd_rx_az | wd_rx_lat | wd_rx_lon | wd_tx_az | wd_tx_lat | wd_tx_lon | wd_v_lat | wd_v_lon 

---------------------+------------+------------+-----------+--------------+-----+----------+----------+--------+-------+-------+----------+---------+------+------------+------+---------+-------------+--------------+----------+-----------+-----------+----------+-----------+-----------+----------+----------

 2021-09-11 13:45:00 | 3403461808 | 1631367900 | N6LF/B    | CN83lt       | -29 | 0.475779 | JH1OFX   | PM95ql |    30 |     0 |     7904 |      49 |    0 | 2.4.0      |    4 | 630     |      -999.9 |       -999.9 |      301 |    43.812 |  -123.042 |       49 |    35.479 |   139.375 |   43.812 | -123.042

while on wsprnet.org, for an MF search with mode=5 

Timestamp Call MHz SNR Drift Grid Pwr Reporter RGrid km az Mode
 2021-09-11 13:46   JH1OFX   0.475779   -29   0   PM95ql   1   N6LF/B   CN83lt   7904   49   5 

matches up
So it is the 'code' that has to be uploaded to the database, and wsprnet.org database then uses their 'mode' equivalent in their query.

To check for mode 30 on wsprnet.org on 2200 I get:
Timestamp Call MHz SNR Drift Grid Pwr Reporter RGrid km az Mode
 2021-09-14 06:30   JA1RWI   0.137520   +1   0   PM95tm   0.1   JA1NQI   QM05dv   73   55   30

and the query on wsprdaemon database

select * from spots where wd_band='2200' and code=8 order by wd_time desc limit 1;

returns

       wd_time       |  Spotnum   |    Date    | Reporter | ReporterGrid | dB |   MHz   | CallSign |  Grid  | Power | Drift | distance | azimuth | Band |  version   | code | wd_band | wd_c2_noise | wd_rms_noise | wd_rx_az | wd_rx_lat | wd_rx_lon | wd_tx_az | wd_tx_lat | wd_tx_lon | wd_v_lat | wd_v_lon 

---------------------+------------+------------+----------+--------------+----+---------+----------+--------+-------+-------+----------+---------+------+------------+------+---------+-------------+--------------+----------+-----------+-----------+----------+-----------+-----------+----------+----------

 2021-09-14 06:30:00 | 3411217293 | 1631601000 | JA1NQI   | QM05dv       |  1 | 0.13752 | JA1RWI   | PM95tm |    20 |     0 |       73 |      55 |   -1 | 2.3.0      |    8 | 2200    |      -999.9 |       -999.9 |      235 |    35.896 |   140.292 |       55 |    35.521 |   139.625 |   35.896 |  140.292

(1 row)


where you see that the code field is 8  corresponding to mode 30 as in Gary's post.

regards
Gwyn G3ZIL

Join wsprdaemon@groups.io to automatically receive all group messages.