Forum Replies Created
-
Posts
-
Just to clarify.
Richard’s log VK2OKR@VKFF-0490_20221216.adi had the incorrect reference VKFF-0490 Tomaree National Park.
It should be corrected to VKFF-0608 Tilligerry National Park.Thanks,
Gerard – VK2IOUnfortunately these logs were submitted with a STATION_CALL of VK2HQ instead of VK2BYF. Once removed the correct log can be submitted.
Hi Daryl,
The correction was made.
You now have a confirmed P2P @ VKFF-2091 with VK2APC @ VKFF-1292.Thanks to whoever made the correction!
Cheers,
Gerard – VK2IOHi Mal,
Your VKFF-0758 log was uploaded on 23 Jan so is now on the system.
The correction was included as you have a confirmed park-to-park with VK2HBG @ VKFF-0248.Cheers,
Gerard – VK2IOHi Pete,
To look for the logsearch entries for VK2ATC
1. Go to the wwff.co site and log in
2. Click LOGSEARCH on the top row
3. In the dialog box replace the default callsign(s) such as VK2LP with VK2ATC and press Search.
You will find there are 9 references worked.
4. Press QSOs.
10 QSOs will be listed. The latest was in 2017 which was before Alec got his VK2APC callsign.
I have worked VK2ATC once myself back in 2014, but it wasn’t from a park so doesn’t appear.This means the callsign corrections have been made.
Alec’s park-to-parks should now be confirmed.
Thank you to the angel (Andrew?) who did that.Cheers,
Gerard – VK2IOHi Mal,
There is no log for 220102 under your callsign within LogSearch.
Have you submitted the log?ParksnPeaks history shows spots for you at VKFF-0758 Holey Plains State Park not VKFF-0389 Nightcap National Park. It is unlikely that you activated VKFF-0389 as it is in northern NSW.
No log correction is possible currently.
Cheers,
Gerard – VK2IOHi Pete,
Just checked VK2APC Alec’s log and it is correct for VKFF-1292.On LogSearch, neither the VK3AWA nor VK3TV contact are confirmed. Note that they are both activating VKFF-2091 on the same day so only one P2P will be awarded anyway.
VK3TV logged a contact with VK2ATC @ VKFF-1292 so there is a callsign mismatch hence unconfirmed for both parties.
Similarly, VK3AWA logged a contact with VK2ATC instead of VK2APC so another callsign mismatch.
These two errors are preventing a confirmed P2P for Alec with VKFF-2091. Correction of these errors may not be possible under the new WWFF policy that logs are final.
Cheers,
Gerard – VK2IO (WWFF VK2 coordinator)Manfred,
The same error is in the VK4FNOR log (VK4FNOR@VKFF001120181124.adi).
The three VKFF-1338 QSOs would need correcting to VKFF-0255 there too.
Thanks.73, Gerard – VK2IO
Hi Manfred,
The problem is in the VK4SOE log (VK4SOE@VKFF001120181124.adi).
There are three QSOs with VKFF-1338 that should be changed to VKFF-0255. These are from VK2XSE, VI2WG50 and VK2KNV.73, Gerard – VK2IO
Hi Andrew,
I’ve fallen down an algorithmic rabbit hole too.
Three activations this year so far but not showing in the activators list. One as AX2IO/P (with OperatorCall as VK2IO) and the others as VK2IO/P. One had 11 QSOs and the others >= 44. One crossed a UTC day too.So the requirement seems to be 3 references of at least 44 QSOs.
I’ll know after my next VK2IO/P activation.Cheers,
Gerard – VK2IOTo answer my own question…
I eventually found the directory here:
https://wwff.co/wwff-data/wwff_directory.pdfNot in the right place but you can get the information.
Use the link above directly.73,
Gerard – VK2IOHi Luciano,
The update to the WWFF awards in Log4OM has just been released today
and it is now up-to-date including ERFF (Moldova) and all new VKFF parks (last is VKFF-1764).Thanks to all involved for the new release.
Cheers,
Gerard – VK2IOHi Luciano,
Today I was able to download an update from wwffaustralia.
Thank you for maintaining the directory and making the changes.
Releasing updates to the national sites while wwff.co is in a state of transition is a good idea.I notified the maintainer of Log4OM and hope that the new entries can be added soon.
73, Gerard – VK2IO
