KA3DRR (Scot): Screenshots | ViewProp, DX Atlas, And Reverse Beacon Network

Image may be NSFW. Clik here to view.

Screenshot DX Atlas Populated Azimuth

Image may be NSFW. Clik here to view.

PropView Azimuth vs. Time

Image may be NSFW. Clik here to view.

PropView Band vs. Time

Good afternoon from #hamr shackadelic as I logged a few 15m Qs from the Florida QSO Party using The Morse Machine memory keyer. My experience was a little different from that of pressing keyboard function keys although it was as exciting. Band conditions seem satisfactory given a few hours in the operating chair. Also, followed up with ferrite chokes on all cabling leading to my Kenwood TS850S inputs including power cords.

I snapped a few screenshots of ViewProp and DX Atlas with Reverse Beacon Network feeds. I'm of the opinion this is only the beginning of a revolutionary change in the interpretation of spot data. Perhaps, many are questioning validity leading to reliability of the data, given erroneous inputs if not corrected prior to entering the system resulting in false positives.

Is it feasible or efficient given for example the West Coast Triad of skimmer sensors located in Utah, Nevada, and California that at least 3 sensors would vote on the accuracy of the input? If two of three sensors cannot agree then the input is deleted? I'm not a programmer and a voting system most likely would slow down output to individual users. Although, at face value, we are currently receiving raw data at our screens, without an interpretive product like ViewProp.

This explains why I'm enthused about ViewProp because Rick, ZL2HAM's product interprets the data into manageable modules leaving the end user to interpret the information displayed on the monitor.

Currently, both ViewProp and DX Atlas are running on my Acer notebook, admittedly it is much like observing a video game of sorts while Reverse Beacon Network populates in real time. Fascinating!

73 from the shackadelic near the beach.