How can alerts be filtered for both VK and ZL associations?
I can obtain one or the other. If a separator is included it is treated as part of the filter and so no results are returned. Maybe this is ‘future functionality’.
Thanks Andrew. The regex is a wonderful addition and solves the issue.
Was going to suggest a distance-based method such as d<4000 to capture alerts within 4000km.
Quite happy to utilise VK[1-9]|ZL[1-9] to filter out the local alerts.
First of all, congratulations on the SW3 migration !
For various reasons * I find that the “add SOTA spot” window once opened is not practical because it is fixed and hides information that is behind it.
Could you make it floating ?
half of the spots are not visible which can interfere to see if we are not going to send an already existing spot, at least as far as frequency is concerned.
Thanks Andrew. I like the new filter features, I just been using ZL|VK|JA seems sufficient… I like the upgrade to SOTAWatch3. If there was anything on my wish list it would be that something visual happens when you hit the “Add Spot” button at the bottom of the add spot window. Especially when out on a summit using a touch screen on a phone sometimes there can be quite a delay and you don’t know if your Add Spot request is been action-ed or not. Cheers John.
Not quite as there is currently an OK/ZL region. I also wanted to future proof it against new regions that include VK and ZL. Only last Sunday OK/ZL-055 was activated so the alert would have matched a simpler filter. Hence the need for the eventual VK[1-9]|ZL[1-9] filter.
Hi again
My question maybe wasn’t in right thread or I don’t used a right alert !
I’ll try this @MM0FMF@VK3ARR Sorry if isn’t the right way ! Respect for all the job was make for the results what everybody can see today !
Need only a response