开云体育

You'd have to account for the fact that some parks are in multiple counties, states, and even grids. Earl / KD5XB Sent from Proton Mail Android

The ability for SpotCollector to lookup a park's location would be very welcomed! Currently, I plug the POTA designator into the pota.app site so I can see on a map where it is. If it's in the same

+ AA6YQ comments below Been thinking about this a lot today as I have been chasing POTA on 20m FT8. My overall goal is to work ATNO's first and then whoever else is activating second (who may be

+ AA6YQ comments below I'll argue that when activators submit logs to LotW and don't create and use appropriate locations it may "hurt" grid or County hunters, and if in a different state or country,

Been thinking about this a lot today as I have been chasing POTA on 20m FT8.? My overall goal is to work ATNO's first and then whoever else is activating second (who may be activating multiples and

I'll argue that when activators submit logs to LotW and don't create and use appropriate locations it may "hurt" grid or County hunters, and if in a different state or country, it may "hurt" WAS or

+ AA6YQ comments below + You reported that the new misbehavior first occurred after a Windows update, so the initial hypothesis is that this update reduced your system's ability to handle the

Hi Dave, FYI only: Prune was set to 7 days.? It had been set to that value for years. I learned long ago to manage the size of the spot database.? Task manager did not show anything churning in the

+ AA6YQ comments below + Neither LoTW nor eQSL provide "POTA credit". What matters is that an activator correctly submit QSOs to POTA so that chasers will get credit. 73, Dave, AA6YQ

Since POTA hunters don't submit logs to the POTA system, any POTA awards are contingent upon the activator submitting their log for any "awards" to be issued. For that reason, especially when I'm

How is all this going to be affected when an activator goes home znd uploads to LotW, eQSL, etc, as if he was at home and not in a park? This is just about as common as breathing. Earl / KD5XB Sent

+ AA6YQ comments below + Thanks for your comments, Dennis!

+ AA6YQ comments below + Your Spot Database was evidently so large that the resulting load was more than your PC could handle. Preventing this is why SpotCollector provides the ability to monitor the

Thanks Joe, all four spot sources are showing green status. Pre Filtering is off. Oh, I just found it (or something that got it going).? I had size control set to 7 days.? I changed that setting

A bit late to the party but here is my .02 on the matter.? FWIW, I have 5500+ total contacts with POTA activators and ~2200 confirmed parks. The first issue is that the POTA database is very dynamic

See: <https://www.dxlabsuite.com/dxlabwiki/EmptyDatabase> In particular, check your computer clock and make sure the spot sources are all "green" (fully logged in). I would bet your computer's time

Greetings to the Group, Two days ago, I did a PC reboot to capture the latest Windows update. Like dozens of times before I did not see any issue.? To be candid I'm not sure this update and reboot is

+ AA6YQ comments below So it's 0715Z, I just woke up and checked Spot Collector. I'm receiving about 37 spots per minute with all skimmers turned off. Is this normal? Seems kinda low. + At 2033Z, I'm

So it's 0715Z, I just woke up and checked Spot Collector. I'm receiving about 37 spots per minute with all skimmers turned off. Is this normal? Seems kinda low. Spot sources are: n6ws.ddns.net

I tried by TCP/IP. Current log4OM manual says to use with slicemaster. Unable to get it to work. Using Omnirig was the only way I could get it to work. Greg AB7R Sent with [Proton