05 Thursday Jan 2017
Announcing the third update in three days, I am pleased to advise that the Reference Activation Statistics are now available in “new” Logsearch.
Note: the All-Programs/All-Time report lists 13,249 activated references, and as such is quite slow to load… and at 7MB is quite a bandwidth consumer, so I may remove this one!
Some improvements in layout will follow, as will the inclusion of the Unactivated report.
04 Wednesday Jan 2017
I am pleased to report that, after much deliberation and experimentation, we have overcome the problems that have prevented the reliable generation of the Top Operator pages.
As such, these should now again be generated overnight (UTC).
Thanks to Manfred DF6EX for his assistance!
Note: the results do not (at present) differentiate between single-operator and club-stations. I hope to resolve this in due course.
As before, these are intended to be indicative, and are not intended to be definitive – they work by aggregating the OPERATOR and HUNTER fields within logs… so activators, when using a club- or special-event callsign, please remember to correctly populate the OPERATOR field!
03 Tuesday Jan 2017
Happy New Year from M0YMA
To get the new year underway, the following updates have been launched this morning:
Good hunting…
13 Tuesday Dec 2016
Over the past year (or so), I’ve completely re-written WWFF Logsearch as a WordPress plugin, to integrate within this main WWFF.CO website. This has mostly been completed… however, the ToDo list (for completion, but especially for new features) remains quite long and I just do not have much spare time…
So I am looking for a suitable competent person (or persons) to help with further Logsearch development – or maybe to take it over completely?!
Skills required are:
Note: this is not something for a “hobby hacker”!
If interested, please post a reply here (if logged in), contact me via the Contact form, or email me (see QRZ.com). Please provide details of your skills, and how you can help!
For the avoidance of any doubt, Logsearch has been donated to WWFF by me (Andrew M0YMA), and is available to anyone else (as is, with no warranties or guarantees), under a GPL2 licence.
29 Tuesday Nov 2016
Tags
Just a reminder that when activating a WWFF reference, you as operator are responsible to follow the rules of your (limited) license. When in a foreign country activating, always check the local rules for your license. It may be different from your home country rules! WWFF is no Radio Police, WWFF is NOT checking if you activated LEGAL or not !
Also about the use of /P /M /MM /A is a lot of confusion. Most countries have clear rules in their Ham licenses when to use /P /M it or not. To avoid confusion it’s important to repeat your call often, and ALWAYS USE THE SAME CALLSIGN. Fill in the WWFF AGENDA with your correct activation data, it helps a lot to spread the correct information among WWFF hunters. For sending QSL (digi or paper) use the SAME CALL AS USED ON AIR. Digital logbooks give an error when downloading wrong data !
WWFF has now a partnership with eQSL. How to eQSL correct from /P is explained here : Correct eQSL for portable operations
28 Monday Nov 2016
Tags
ZS8Z, David (ZS1BCE), gives his full support to the WWFF program. The logs from his previous stays on Marion Island ZSFF-0012 will be uploaded to the LogSearch database.
For those who have not worked him yet, David will stay on Marion Island again December 2016 – May 2018. David mainly operates SSB and DIGI modes. QSL via ZS1AL.
28 Monday Nov 2016
Posted in Awards, News, WWFF board news
≈ Comments Off on Special Awards in LogSearch
Tags
WWFF added the button “Special Awards” into LogSearch.
From now on we can add special event awards and make them available via the well known LogSearch procedure (push the button and get the award)
We’re thinking about awards for one day events, activity days, personal awards etc.
If you have an award to be added please contact me at dannyATon4vt.be
If you are planning an event, please discuss the Rules (etc) with the team to make sure they can easily be implemented in LogSearch!