Cluster Spot Integration With Stats

[kylekrieg]

Today the end user can log into a cluster and NR will pull on average per min the # of spots and give stats. This is good for seeing if a band is hot, but what if NR could display better stats on what the cluster is telling them?

1. heat map of what regions are hot from one location to another. Example, if there are a lot of EU stations being spotted from NA, that's good info to maybe get on a certain band and work a bunch of EU stations from NA.

2. You could drill further and graph with great circle lines actual contacts in point 1 above like grid tracker does for FT8 contacts but that could get messy. We would need a time to live for points on the map.

3. Provide real time stats for spots. To/from stats in bar graphs, CW sending speed in bar graphs. This info is great after the fact, but it would be great if it was provided real time.

https://twitter.com/EA2CW/status/1597800931302772737?s=20&t=axSfhgZP5ueAXl6CHuAPJw

4. Documented in another feature-request, calculate and display # of mults per band from the cluster. See Add 15, 30 & 45 run rates #10 Available points per band #13 Q's per hour not calculating correct? #11

I'm seeing some type of local database table to be built up for lookups for the most active contest calls. Today we can look up calls via the QRZ page, but this API call is probably not fast enough for call and de station look up during very active contest periods. An local database with call, prefix, lat/lon, CQ zone would probably be best, kind of like the call history file or the super partial check file that a user could download on a regular basis and pull into their local database. This database could be crowdsourced since most of this data is already parsed via N1MM and lat/lon is looked up already via the NR contest dashboard.