Hi guys.

Simplified advanced text can now be included in http://wspr.rocks/wdprop/ which allows visualising a single band such as 10m to get a better idea of past and current propagation trends.

For anybody not in the WD users menu, it is editable for any callsign as per the [tricks] info.

73, Phil

Hi Phil, how do you populate the WD users menu ? Is it supposed to be complete ?

Cheers,
Erwin

Hi Erwin, it's the top 30, otherwise the menu would be too long.

The idea is that (1) the menu at least starts off with a bunch of regular spotters with enough spots to provide worthwhile global propagation, and (2) anyone can edit the menu to add any callsign of interest.

As per the prev post  "For anybody not in the WD users menu, it is editable for any callsign as per the [tricks] info."

 

 

 

On 15/11/2022 09:40, Erwin - PE3ES - F4VTQ via groups.io wrote:

Hi Phil, how do you populate the WD users menu ? Is it supposed to be complete ?

Erwin

Click on "tricks" then the "menu editor"

I think you may only replace a call with yours, not add a new one.

73 Alan G4ZFQ

Hi Alan, yes, replacement is the word I should have used, thanks for clarifying.   That was a simple way of getting the app functional, how it evolve depends on feedback and spare time.

Phil

http://wspr.rocks/wdprop/   now has a 'search by map' option.

Will require a hard-refresh of the browser to load the new code.

--

Hi Rob, glad you like it, must say I didn't expect such a welcome response!  Probably has bugs, the code is a bit on the edge.

Short cut:  when you do a search from the map view, you can then toggle between chart and map view by clicking the Choose rectangles label as per the pic.

Limitations:  the rectangles are divided into 2char locator blocks for the query;  if I used 4 char locators ClickHouse can't handle the large number of them, there are 200 4ch squares in a 2ch square, anyway 2char is OK because areas smaller than one of those mostly don't have enough spots to give meaningful propagation charts.

When I say 'divided' I mean that any part of the visible rectangles that is in or on the edge of a 2char locator causes that locator to be selected.  Here's a Maidenhead chart for better understanding of what a rectangle will deliver.  https://dxcluster.ha8tks.hu/hamgeocoding/

EDIT:  The locators for each search are now visible in the browser console for anyone interested in exactly what area is queried.

I made the rectangle edges snap to the nearest 4char long/lats when the rectangle is resized, if you're wondering why they won't go exactly where you want.