POTA/SOTA/WWFF

10 posts / 0 new
Last post
KF4DRR
POTA/SOTA/WWFF

With POTA especially for Park to Park credit one needs MY_SIG_INFO and SIG_INFO in the adif. What fields relate to these 2 entries?

from documentation on the POTA facebook group:
If I had a P2P, enter:
• MY_SIG_INFO Park I’m in
• SIG_INFO other person’s park

oh1kh
POTA/SOTA/WWFF

Hi
There are no such fields. If you look adif definitions http://adif.org/310/ADIF_310.htm#Data_Types_Enumerations_and_Fields we simply can not support them all.
I could be possible to add user defined fieds for qso record, but that raises another problem: how many there shoul be?

Simplest way is to use fieds we already have.
Maybe create first a new qth profile for every activation. Then use what ever field for opponent information. I have used "award" for saving FF information.

When exported to adif it is very easy to modify adif file with console command 'sed'. See this message https://cqrlog.com/comment/7644#comment-7644
When modifying adif tag name do not touch the length definition ":[number]" and the tag's text itself.

'sed' is perfect "all in one go" command for this.

--
Saku
OH1KH

KF4DRR
Thanks for the quick answer.

Thanks for the quick answer. I was hoping that I wouldn't be scripting around it but no problem. I can just use contest window and then after export just run a simple bash script to process the adif tags into what I need them to be.

73 thanks for the excellent program!

oh1kh
POTA/SOTA/WWFF

Hi!

Just another idea:

If you always export your adif log to same folder and with same name then you can include sed lines to cqrlog's stop script that is always run when program ends.
Then you have fixed export waiting when you close cqrlog :-D :-D

--
Saku
OH1KH

KF4DRR
separate logs in the database

separate logs in the database exported so separate folders to keep myself straight. the saved log dir structure looks something like ~/Documents/Logs/POTA/K-####/$$$$$.adi

oh1kh
POTA/SOTA/WWFF

HI!

Actually you do not need any script. Needed version of sed command can be run just from one command line. Of course to save typing in future it is nice to put it in one or 2 liner script in case command line history (ctrl-R) does not find it any more.

Enjoy your portable operations!

--
Saku
OH1KH

KF4DRR
true but then I have to type

true but then I have to type it every time I do an activation. I simply put the below in a bash script named POTA and now when i export the log is just POTA filename. I'll probably add emailing it to the script to just simplify life further at some point.

#!/bin/bash
file=$1
sed -i "s/STX_STRING/MY_SIG_INFO/g" "$file"
sed -i "s/SRX_STRING/SIG_INFO/g" "$file"
sed -i 's/100/5/g' "$file"

KF4DRR
<p>I just noticed that the

<p>I just noticed that the HTML filtered part of the script.</p>
<p>&nbsp;</p>
<p>#!/bin/bash<br />file=$1<br />sed -i "s/STX_STRING/MY_SIG_INFO/g" "$file"<br />sed -i "s/SRX_STRING/SIG_INFO/g" "$file"<br />sed -i 's/&lt;TX_PWR:3&gt;100/&lt;TX_PWR:1&gt;5/g' "$file"<br /><br /><br /><br /></p>

KF4DRR
blast!

blast!

oh1kh
Blast

Hi

This forum also needs sed :-)

To get arrows properly < > conversion to & l g ; and & g t ; is needed (without spaces between)
Even text between the "code" tags do not always show out properly with arrows.

--
Saku
OH1KH