POTA Award Refs Update stops POTA ID in "Note" field

[G4POP]

I've noticed that a lot from OMs posts on k4zkf or any of the other ve7cc associated clusters. They don't all follow the basic/expected format of US-123456 ...

At least most (close to all) of the posts from the hamalert cluster do follow the expected format. For both POTA and SOTA.

The point is he allocated a US POTA REF for a Dutch Station! Clearly we can't match a US ref to a station operating in Holland

[KI5IO]

Terry,

It appears I 'might have' just stumbled into a Ref csv file import configuration that works (for me anyway) so it doesn't stop Log4OM from recognizing the POTA IDs in the Cluster 'notes' field.

On the 'select file and format' tab for the csv file import I tried multiple combinations of which or all of the fields to import.

The combination that (so far) has worked for me is to NOT select the "active" field.

I'll keep my fingers crossed and a close eye on the operation and also try some more updates in days/weeks ahead to see if my "luck" holds.

.

[KI5IO]

I've noticed that a lot from OMs posts on k4zkf or any of the other ve7cc associated clusters. They don't all follow the basic/expected format of US-123456 ...

At least most (close to all) of the posts from the hamalert cluster do follow the expected format. For both POTA and SOTA.

The point is he allocated a US POTA REF for a Dutch Station! Clearly we can't match a US ref to a station operating in Holland

Terry,

I reached out to kd5uyz and he just confirmed that his spot was a typo on his part ... certainly not on purpose he said in his e-mail that I just got back from him.

[G4POP]

Terry,

It appears I 'might have' just stumbled into a Ref csv file import configuration that works (for me anyway) so it doesn't stop Log4OM from recognizing the POTA IDs in the Cluster 'notes' field.

On the 'select file and format' tab for the csv file import I tried multiple combinations of which or all of the fields to import.

The combination that (so far) has worked for me is to NOT select the "active" field.

I'll keep my fingers crossed and a close eye on the operation and also try some more updates in days/weeks ahead to see if my "luck" holds.

.

That's the problem I think?

We don't use that data firstly how could a park be deemed to be active or inactive? So there is no matching field in lod4om

I wonder where you put it? However that accounts why it works for me because I ignore the field.

[KI5IO]

Terry,

It appears I 'might have' just stumbled into a Ref csv file import configuration that works (for me anyway) so it doesn't stop Log4OM from recognizing the POTA IDs in the Cluster 'notes' field.

On the 'select file and format' tab for the csv file import I tried multiple combinations of which or all of the fields to import.

The combination that (so far) has worked for me is to NOT select the "active" field.

I'll keep my fingers crossed and a close eye on the operation and also try some more updates in days/weeks ahead to see if my "luck" holds.

.

That's the problem I think?

We don't use that data firstly how could a park be deemed to be active or inactive? So there is no matching field in lod4om

I wonder where you put it? However that accounts why it works for me because I ignore the field.

Terry,

RE: Active vs Inactive

Then looking at Page 177 of U.G. need to change as it shows "Active to Valid Field" being used.

PC9DB also set out a similar placement for the fields from the POTA csv at his Forum thread here:
https://forum.log4om.com/viewtopic.php? ... a&start=10

Can definitely close this one it appears.

.

[KI5IO]

Here are a couple screen clips of the selected fields for the import of the POTA Ref update.

These images reflect what I've noted above that at least works for me to keep Log4OM from recognizing the POTA IDs in the Cluster Notes field.

.

[LB4MI]

Hi,
I was going to write a case about this same issue when I found this being already discussed.

The same issue occur specially when receiving spots from a POTA/SOTA cluster, dxc.n1rbd.radio at port 7300.

The "Notes" contain the correct references to the POTA, SOTA or WWFF. But Log4OM does not always collect that and add it to Award automatically.
For SOTA there is a separate cluster, cluster.osta.org.uk at port 7300. When I use this, I always get the reference to SOTA correct to Log4OM.

I suspect this has to do with how the cluster generate the "Note".

Underneath are one example where Log4OM did not fill in automatically from Notes.
(Sorry for bad picture quality, I had to make then small due to forum limitations 250kb)

The reference is correct in Note (as it is directly populated from the POTA website or SOTA website).

It it something with the way the "Note" is made by the cluster (dxc.n1rbd.radio) that makes this issue? Note that this is not a new issue, but I haven't taken time to register it before.

not picking up ref from Notes 1 (Medium).jpg (249.71 KiB) Viewed 6205 times

[IW3HMH]

There are many ways Log4Om tries to "extract" a reference from the messages.
It will try to find a reference by replacing "/-_" and some other characters from a string, then comparing it with the list of references (all will be "normalized" internally).
Another way, more delicate, is to check words in pairs, so in the string "This Is IOTA EU 131" the application will try "THISIS", "ISIOTA", IOTAEU", "EU131".
The last one is good.

But if you write "This Is EU IOTA 131" the sequence will never find "EU131", but EUIOTA or IOTA131 and no one is similar to a good reference.
To avoid false positives all references are checked against:

1) country (the reference country list should match the QSO country)
2) valid dates (the QSO must be inside the reference valid date range, if any)

That's why a good database (on import) is fundamental (and sometime we notice missing data from our data sources, POTA and WWFF included)

[LB4MI]

Hi,
just letting you know that I also (I stole this topic) solved my "issues" with references not being picked up from cluster notes:

POTA: I had also, most likely, added the "Active" field as OP mentioned. Doing a new full import of POTA database, ignoring the Active field made all POTA references come back.

WWFF: Here I did a full import following the User Manual. And afterwards I didn't get the references from notes in cluster. Based on the recently learned info from POTA, I ignored the User Manual page 179:

Valid settings:
Valid field: status
Valid value: active

And after a new import, with the settings underneath. And a restart of Log4OM, everything seem to work fine again.
So perhaps the two fields are not neccessary, and will cause a problem?

My import settings:

WWFF import.jpg (92.92 KiB) Viewed 3090 times