Spot Origin filter
|
Pete Smith
I've been trying to get this feature to work. Using the Origin window in Spot Collector, I have selected NA-E, but I continue to get spots originating, for example, in Europe. What am I missing? -- 73, Pete N4ZR Check out the new Reverse Beacon Network web server at <https://reversebeacon.net>. For spots, please use your favorite "retail" DX cluster. |
|
|
|
Dave AA6YQ
+ AA6YQ comments below
+ That's correct behavior.
+ When you set the Origin filter to NA-E, SpotCollector will only display active stations that have been spotted at least once from the east coast of North America. This filter does not mean "only display active stations that have been spotted ONLY from the east coast of North America. + Say, for example your next door neighbor spots P5DX, which you need. You don't want SpotCollector to hide the entry for P5DX because it was also spotted from France. 73,
|
|
|
|
Pete Smith
Thanks, Dave. Using
Spot Collector in real time, though, I'd want to know that the
previous spot by a NA-E station occurred within a time window
that I have set, such as "spots heard in NA-E within the last
hour." Is that condition met by my setting the spot database
Age Filter to, for example, 60 minutes? 73, Pete N4ZR Check out the new Reverse Beacon Network web server at <https://reversebeacon.net>. For spots, please use your favorite "retail" DX cluster. On 10/8/2022 1:03 PM, Dave AA6YQ wrote:
+ AA6YQ comments below |
|
|
|
Dave AA6YQ
+ AA6YQ comments below
Thanks, Dave. Using Spot Collector in real time, though, I'd want to know that the previous spot by a NA-E station occurred within a time window that I have set, such as "spots heard in NA-E within the last hour." Is that condition met by my setting the spot database Age Filter to, for example, 60 minutes? + No, The Age filter is triggered by any spot of an active station. A Spot Database Entry records the time of the most recent spot; it does not record the time of the most recent spot from NA-E, the time of the most recent spot from NA-M, the time of the most recent spot from NA-W, the time of the most recent spot from AS, the time of the most recent spot from EU, the time of the most recent spot from AF, or the time of the most recent spot from OC. + If your goal is to hide the display active stations that you are unlikely to be able to hear and work, see https://www.dxlabsuite.com/dxlabwiki/HidingDXYouCantHear
73,
|
|
|
|
Dave AA6YQ
"Since DX stations are reported by stations around the world, you won't be able to hear every DX station that is reported as active. The time you spend listening for a needed station to whom the band isn't open is time you can't spend working a needed station to whom the band is open. Many DXers address this problem by only considering DX stations spotted by stations in their own geographic area -- but this can be counterproductive. If you're located in the US Midwest, for example, and have configured SpotCollector to hide DX Stations not spotted from somewhere in North America, the display of a needed and workable DX station that was first spotted by a station in Europe will be delayed until it is spotted by someone in North America. Similarly, a European DXer who hides DX stations not spotted by a fellow European risks missing needed and workable DX first spotted by a station in Africa, Asia, or North America. When operating on VHF or UHF bands, the problem is that geographical areas are too large to serve as reliable indicators; the fact that an "East Coast" station in Florida is working a Caribbean station on 6 meters doesn't mean that an "East Coast" station in Maine will also have a 6 meter opening to the Caribbean."
"SpotCollector provides three better mechanisms for hiding active DX stations that likely can't be worked: hiding low-band DX during your daytime, hiding VHF and UHF DX not spotted by nearby stations, and using propagation forecasts to hide DX to which there is probably no band opening" - from https://www.dxlabsuite.com/dxlabwiki/HidingDXYouCantHear 73,
|
|
|
|
Pete Smith
That's too bad... in
using DXLab in real time, I would want to know not only are
people (wherever) still hearing him, but is he someone who was
heard in my area within the last hour - maybe an enhancement
idea? 73, Pete N4ZR Check out the new Reverse Beacon Network web server at <https://reversebeacon.net>. For spots, please use your favorite "retail" DX cluster. On 10/8/2022 1:40 PM, Dave AA6YQ wrote:
+ AA6YQ comments below |
|
|
|
Dave AA6YQ
+ AA6YQ comments below
That's too bad... in using DXLab in real time, I would want to know not only are people (wherever) still hearing him, but is he someone who was heard in my area within the last hour - maybe an enhancement idea? + If you check the "Record individual spot information" box in the Controls panel on the "Spot Database" tab of SpotCollector's Configuration window, then you can right-click any Spot Database Entry, choose "Display spots of ..." from the pop-up menu to display a window show all spots of the Entry's station in chronological order - with the region of each each spot's spotting station. Thus you can easily determine whether or not an active station has been spotted from your region in the last hour. See the 5th bullet in https://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm#Selecting%20a%20Spot |
|
|