Features for SOTA?

Thanks for the app, I am loving it!

I have moved over from Outd Log which isnt being supported anymore. There are a couple of features I miss, so I thought I would menton them just incase I am missing something.

My ‘thing’ is SOTA and especially S2S (summit to summit). Two features that would really speed things up are:
A shortcut for adding /P at the end of a call sign. At the moment I have to flick between a couple of keyboard screens to do this.
Also when adding a summit to summit, adding their summit takes three different keyboard screens. In Outd Log if you enter G SP 004, it would insert the / and - so G/SP-004

Forgive me if I have missed this but they would be nice features to have.

Thanks for your consideration
Martin

1 Like

As for the first question, the . (dot/full stop) is replace with a slash. Try it.

And the second, the same thing goes for entering references, you just type the numbers and letters, and PoLo formats the reference for you.
If this is not the case for your particular jurisdiction, then we need some examples.
Alan

Alan

Thanks for your help… it gets better and better!
Cheers

Martin

Btw. it would be great if this would also work for the summit references as the automatic recognition (formating of the S2S ref) is not working very well.
But I guess it is in the Regex for recognizing a sota reference. A search from the “end of the string” should work better.

  • Always 3 decimals at the end . \d{3}$
  • Add a dash before that if not there already
  • The region always has always 2 letters (non-digit) A-Z]{2} (always the last 2 non-digit)
  • Add the forward slash before that
  • Everything before the slash is the association (it can contain A-Z and 0-9 with {1,3} )

Not an regex expert but something like that should bring the propper groups?


So all variations with or without the / or - should give a group of list of 3 with Assoziation, Region, Summit number

Can you give me some examples of references that do not work with the current code?

I tested the ones you show on your screenshot and they all work fine and are formatted correctly as soon as you enter the first digit.

It is not a specific reference. It is a timing issue from my point of view.

Quickly typed FLVO001

Slowly typed the same FLVO001

Thanks for taking care :+1:

73 Joe

Thanks - I can make the same comment about entering POTA reference numbers. Typed normally on the simulator the reference prefix is inserted correctly. Typed normally in the field where internet latency is higher, the prefix codes are often not inserted. Typing very slowly can fix it, but not always.
Alan

1 Like

All the data that I put in the field is obviously visible (so nothing is lost). But the assessment and reformatting kicks in too late ( or too early) or incorrectly?

1 Like

This should get better with the August release

Just tested on the August release and unfortunatly still the same behaviour :flushed:

Please update to 25.8 patch 1 and try again.

Thanks. First tests for SOTA references look good. Will do a field test under real life conditions next weekend.

73 Joe

The real-life tests on three SOTA activations this weekend unfortunatly still show the same issue.

73 Joe