P2P confirmations

Previously there has been a lot of discussion regarding P2P confirmations, or rather the lack of.

I have added a bit of debug to the over-night P2P confirmation script… which provides the following information (as of 07:00BST 2018-08-31):

  • 19,237 QSOs with an unconfirmed P2P claim
  • 18 of these could not confirm due to potential duplicate matches, outside of a time tolerance (I can look into those)
  • 2,482 QSOs cannot confirm due to band, mode or reference discrepancies!

Once I’ve validated the script, I’ll publish more details to users… but the key point here is: PLEASE CHECK YOUR LOGS!

Logsearch Update – August 2018

Just in time, the August 2018 update (v0.0.3) has just been released…

The headline is the addition of the CUFF award, together with a number of framework updates to support ongoing work.

In particular, attempts to detect problems that prevent (potential) P2P confirmations will be ongoing.

Issues Addressed

This addresses the following GitLab issues:

  • Issue #00004 – Directory Manager
    • Address issues with slashing and unslashing of special characters
  • Issue #00005 – P2P Confirmation Error flag (*)
    • Framework put in place for future updates
  • Issue #00006 – hunterHomeCall (*)
    • Framework added – used to simplify Top Operator calculations
  • Issue #00007 – Directory SpecialFlags (*)
    • Display of specialFlags
  • Issue #00008 – CUFF Award
    • Added at entry level

(*) = Framework for ongoing development

Open Issues can be found in the GitLab Issue Tracker.

Personal Note

Development of Logsearch has to fit around family and work commitments! This is particularly the case as I’ve recently started a new job which means I’m on the road a lot!


Any problems, or new feature requests, via the Help Desk Forum please.

Forum Usage

All users are reminded that access to WWFF Logsearch and the WWFF Forum is a privilege, not a right – and the WWFF Team reserve the right to temporarily suspend access (or permanently ban) anyone who’s conduct may bring WWFF into disrepute.

The WWFF Team have previously avoided the need for published Forum Rules, however (regretfully) this has become necessary.

Therefore, by accessing the WWFF Forum, you agree to abide by the discussion rules.

These include:

  • Do not submit comments that contain personal information e.g. home addresses or phone numbers.
  • Do not submit comments that are unlawful, harassing, abusive, threatening, harmful, obscene, profane, sexually orientated or racially offensive.
  • Do not swear or use language that could offend other forum participants.
  • Do not advertise or promote products or services.
  • Do not spam or flood the forum. Only submit a comment once.
  • Do not resubmit the same, or similar, comments.
  • Keep your comments relevant to the discussion topic.



Get Your Park ON!



Hello fellow WWFF Country Coordinators and others….

I am writing to let you know about a new WWFF event, sponsored by KFF (USA), VEFF (Canada) and XEFF (Mexico) called Get Your Park ON!.
During the week of October 14-20, 2018 we will have as many North American WWFF parks on the air as we can. In turn we are encouraging ham radio operators world wide to reach out to make contact with all activated parks in North America during that week. The sponsor groups also have a cross promotion agreement with the Earth Science Week program taking place that same week to bring attention to the protected nature areas of our world.
We are asking you to share the information for Get Your Park ON! throughout your country organization and encourage your operators to participate in this first time event. Planned North America park activations will be listed on the Get Your Park ON! Facebook group at http://getyourparkon.com.
As details are finalized about this event they can also be found at that same location. All operators are encouraged to join the Facebook group at that same location.
Attached you will find a press release and a graphic that you may use to promote Get Your Park ON! in your region.
NOTE: While this year we are focused on North America WWFF parks, we hope to expand the participation to other countries and regions in future events of this type–perhaps including the entire WWFF global family. Please freely share this with any operators that you feel would be interested.
I will be active as an Activator and a Hunter during Get Your Park ON! and we hope that we have wonderful participation from around the world.
Thank you for being a part of World Wide Flora and Fauna.

Kraig D. Pritts, KA2LHO

WWFF-KFF Coordinator

Logsearch Update – July 2018

Just in time, the July 2018 update has just been released… this generates a CSV copy of the WWFF Directory nightly.

This is in response to requests for a format that can be imported into various logging programs.


While this may well only be a small update, it marks the first contribution by Marc VK3OHM – thank you Marc.

Version Control

Up until now, Logsearch has been released as v0.0.1, but as a set of dated versions. This release moves this onto v0.0.2 – future released will be uniquely versioned rather than dated (not that this matters to the users!).

Personal Note

Development of Logsearch has to fit around family and work commitments! This is particularly the case as I’ve recently started a new job which means I’m on the road a lot!


Any problems, or new feature requests, via the Help Desk Forum please.

ZV8FF active from PYFF-0209

Expedition Fauna & Flora and Contest IOTA

PS8RV – Ronaldo Val, will be in a new expedition in the Island of the Canaries, Delta of Parnaíba for joint operation in the Diploma WWFF and Contest IOTA. The operation will be carried out in the period from July 27 to 28 in the HF bands (80 to 10m) with a ZV8FF sign.

WWFF – PYFF – 0209 – DELTA DO PARNAIBA & IOTA SA- 072 (Caju Archipelago)DX Expedition & Contest IOTA – 28,29 July, 2018

Operator: Ronaldo Val – Callsign: ZV8FF Power – 100 WATTS – Bands – 10 – 15 – 20 – 40 – 80 meters – Mode SSB

More information: www.qrz.com/db/zv8ff


Confirming Park-To-Park

A recurring question is: How are P2P contacts confirmed.

It’s quite simple…

  • Both logs must be uploaded – we will call them Log A and Log B
  • A number of fields must match…
    1. Callsigns:
      • The STATION call of Log A must match the HUNTER call of Log B
      • The STATION call of Log B must match the HUNTER call of Log A
      • Note: Callsigns are compared after stripping all prefixes and suffixes
    2. References:
      • The HUNTER REFERENCE in Log A must match the ACTIVATOR REFERENCE in Log B
      • The HUNTER REFERENCE in Log B must match the ACTIVATOR REFERENCE in Log A, or be empty
      • Note: Thus only one log needs to claim the P2P for BOTH to be confirmed (if there is a match)
    3. The BAND, MODE and DATE of both Logs must match
    4. The TIME field is only used as a tie-breaker:
      • If there is only one matching QSO, then it is confirmed without further ado
      • If there is more than one matching QSO, then TIME must match (± 5 minutes)
Translate »