Roger thanks for sharing. Do you have any other ideas to reduce false Spots being uploaded and stored in the Database? Look at the Screenshot in my opening post. I am still looking for ways to count t

#WSPR

http://www.wsprnet.org/drupal/node/7109

#WSPR

Many are already registered members on qrz.com (free or paid sub). In order to use the XML API you need to have an XML subscription (USD29.95/year). I use the service for several other HAM-related pro

#WSPR

My post is about invalid locators/callsign pairs. GM1BAN is a correct callsign.

#WSPR

That's another good question. I think that needs more research. To stick to the example with GM1BAN and the wrong locator it was decoded by WSJT-X 2.1.2

#WSPR

People are moving, changing locations for many reasons. Therefore I think a year is a long period of time for a client-side call/locator cache.

#WSPR

That would be great to have this functionality integrated into WSJT-X. I like the idea of caching for a certain time Roland

#WSPR

Every Operator is responsible for his own Data

#WSPR

Biil, GM1BAN is only sending 4 character locator as all of our Beacons

#WSPR

The question I have is can we validate some of the Spot data like the locator before it gets uploaded? As explained in my opening post?

#WSPR

Hi Bill, I am the founder of the Intl. WSPR Beacon Project, GM1BAN is one of our Beacons. Here are his transmissions Link That is just one example. I don't know how many there are in total, difficult

#WSPR

It seems many decoded Spots contain wrong information like TX locator for example. There is no Data validation in the whole chain which leads to problems if you are into Data Analytics. My proposal is

#WSPR

Another example on 40m. 26 Spots in ALL_WSPR.txt 211102 1506 -30 -0.10 7.0399895 PA2HGJ JO22 10 -1 0.15 1 1 0 0 27 212 -95 211102 1506 -6 0.24 7.0400087 G4GCI IO90 37 0 0.54 1 1 0 0 2 1 531 211102 150

#WSPR

I started with live decode performance testing (Band hopping) using WSJT-X 2.51 on the Pi Zero 2. I ran into an issue where Spots don't get uploaded to wsprnet. It seems to happen when large amounts o

#WSPR

That's good to know, thanks Bill. I have not changed the decoding wsprd parameters and will do a side-by-side test with an RPi Zero 2 and an RPi4, just to confirm decoding performance, sharing the sam

#WSPR

I am currently testing the all-new RPi 2 W. I am curious to see if the 15$ SOC can handle decodes on busy bands, with lots of WSPR signals to decode. Now my question is does WSJT log if a decode timeo

#WSPR

Every now and then WSJT-X throws a Subprocess Error while WSPR RX Band hopping on a Rpi 3B+ (Buster). If I click "OK" WSJT-X crashes. If I leave the Error window untouched, WSJT-X continues to run. An

#decode #WSPR #raspberryPi

This is the map of the current Beacon candidates https://www.google.com/maps/d/u/1/edit?mid=14X0GJ4vSQ7D8piZfuHDs902Y9tINuPqB&usp=sharing nothing finalized yet

#Beacons

Quick update on the Intl. WSPR Beacon Project, currently we have 15 candidates from 8 DXCC entities expressing their interest to run a Beacon. Still missing Japan. Please help to spread the word. Than

#Beacons

Thanks Bob, currently reaching out to HAM Radio Clubs around the world to draw some interest and to promote the new Project. I already made a post on the Wsprnet.org forum. Much appreciated if you cou

#Beacons