Jean-Marc MEESSEN
6134577dd0
|
4 years ago | |
---|---|---|
.github | 4 years ago | |
.vscode | 4 years ago | |
cmd | 4 years ago | |
doc | 4 years ago | |
docker | 4 years ago | |
notes | 4 years ago | |
test | 4 years ago | |
.gitignore | 4 years ago | |
.goreleaser.yml | 4 years ago | |
LICENSE | 5 years ago | |
README.md | 4 years ago | |
build.sh | 4 years ago | |
docker-FLEcli.sh | 4 years ago | |
go.mod | 4 years ago | |
go.sum | 4 years ago | |
main.go | 5 years ago | |
test.sh | 4 years ago | |
todo.md | 4 years ago |
README.md
FLEcli
Multi-platform "Fast Log Entry"(FLE) processing tool.
"Fast Log Entry" is a nifty tool, written by DF3CB. It allows quick and efficient entry of radio amateur contacts made during DXpeditions, contests or SOTA/WWFF activation. It can export the listed contacts in ADIF format ready to be uploaded to eQSL/LOTW or submitted for SOTA and WWFF. The program is only available as a Windows executable which leaves the Mac or Linux users (like me) in the cold.
This tool is intended to process FLE formatted files on other platform than Windows. The FLE file format is described on https://www.df3cb.com/fle/documentation/
But is also the alibi to learn and explore GO.
Installing
The tool is installed by downloading and unpacking the archive for your operating system.
A version is available for Windows, MacOS, Linux and ARM (RaspeberyPi). Most of them are available as 32 or 64 bit applications. A docker version is also available.
The releases can be downloaded from https://github.com/on4kjm/FLEcli/releases
Detailed installation instructions can be found at this page.
Usage
Detailed explanations can be found on this page.
Most comon use cases are described hereafter as examples.
Example: validate the FLE syntax of a file
To load and validate the FLE formated file (myActivation.txt
:
./FLEcli load -i=myActivation.txt
This command will parse and display the QSOs in grid format. Fields that couldn't be successfully parsed are prefixed with "*". Parsing errors or doubts are listed at the end of the list.
Example: generate an ADIF file
To generate an ADIF file based on activation.txt
:
./FLEcli adif -i activation.txt -o output/activation.adi --overwrite --interpolate
The -o
(or the long form, --output
) specifies the path and name of the output file.
If the flag and value are omitted, the tool will generate a filename.
It is based on the input filename, just replacing the extension with .adi
.
The --overwrite
flag indicates that, if the output file already exists, it should be overwritten.
The --interpolate
flag will interpolate the missing non-entered times based on the first and the last entered time.
Example: generate an ADIF file for WWFF upload
To generate a WWFF-ready ADIF file:
./FLEcli adif -i ON4KJM@ONFF-025920200524.txt --wwff --interpolate
The --wwff
indicates the adif flavour to produce.
You can use the --sota
switch to generate an ADIF file containing SOTA details.
The switch can be used together with --wwff
As we didn't provide an output filename, the default output, ON4KJM@ONFF-025920200524.adi
will be used.
Example: generate a SOTA csv file
To generate a CSV file that can be uploaded to https://www.sotadata.org.uk/ to report SOTA activations:
./FLEcli csv -i sotaActivation.txt --overwrite --interpolate
This command will generate sotaActivation.csv
based on the sotaActivation.txt
FLE logfile.
If the output file exists, it will be overwritten as the --overwrite
flag has been specified.
The --interpolate
flag will interpolate the missing non-entered times based on the first and the last entered time.