I’ve tried a few times to upload an Activator log using the manual input method, while my SOTA activation is valid, my Challenge points are not being added.
As per the instructions, I’ve gone afterward and performed an edit to include the chasers location details. I then get the World Globe symbol next to each callsign, showing the location information is correct. But the points are not being added to my score.
I am wondering if there is a stage I am missing.
Thanks
Nick G0HIK
Me too.
Andy
MM7MOX
present, not necessarily correct (although it could be!)
Could you send me a PM with a screenshot of the location dialog, so I can see how you’re entering the location data?
I’ve just tried entering the chaser location again, it works now if I enter lat and long but not if I use Maidenhead locator.
My results now show up in the challenge table as well.
I can work with that.
Thank you for your prompt response, I don’t know a lot about databases but really appreciate the behind the scenes effort that goes into SOTA.
Andy
MM7MOX
Ah, I see the issue for your log in particular - you have some interesting capitalization of your Maidenhead locators, and I have some really poor handling of input when it doesn’t look like a normal maidenhead locator 
Fix building now, but glad you have got to a point where everything is counted.
Thank you very much.
I’ve never really had to use Maidenhead locators before apart from reading them out to contest stations that chase me , so I’m not that familiar with the formatting.
Andy
MM7MOX
For some reason the default is capitals first two letters then lower case for the others. E.g.
For six characters: IO88ab
In all logging tools this is all upper case. Also in the adif standard.
This is just like some weird people add spaces jn their callsign… 
My typical input sanitation:
No! The specification is as Andrew says i.e. XX11xx
The only exception is the ADIF spec which says all upper case.
For some reason LotW also uses all upper case, maybe because they just copy what is in the uploaded ADIF
It’s done during the processing of the maidenhead, but getting all the possible combinations out of comments and location fields which may not be able to be uppercased means that the regular expression needs to be more open than what I had it (basically by making it case insensitive) in order to get the maidenhead into the maidenhead processing process.
What I wanted to say is that as a programmer one must expect that users make errors. And if possible one can correct those errors if they are minor.
I am daring to make that statement as I have programmed my own logging tool for the OE 1st May EMCOM exercise. I know how unmindful users can be. So I like to listen and if possible fix things for the fun of everyone. And I see that Andrew is doing the same.
And to Quote Wikipedia:
Maidenhead Locator System - Wikipedia
For additional precision, each square can optionally be sub-divided further, into subsquares. These are encoded into a second pair of letters, which should be presented in uppercase,[6] but are sometimes (incorrectly) presented in lowercase as a legacy from the old QRA