This morning I noticed that the quick-log function on SOTAWatch includes a new field entitled “LOCATION” in addition to the Summit designator. What location data is appropriate here?
Stay well & 73! Mike, WB2FUV
1 Like
Your own!
I suspect this is getting ready for the 2026 challenge where that data will be needed
Mike, your lat & long in your SOTA account were malformed. I have corrected them for you. The hint to us programming types was the display showing “NaN, NaN”. Nan = Not a Number which means whatever is in the field is not a number. Obvious when you know and NaN,NaN suggests malformed lat & long to me. If you log out of SOTAwatch and log back in and look again at logging a chase your Location field should show your location correctly. Have a look and let me know if it looks to be correct.
1 Like
Thanks Andy. No idea what caused my lat/long error ??!!! Stay well & 73! Mike WB2FUV
1 Like
The most common issue is people putting in DMS format, rather than decimal, prior to the profile software being upgraded and now allowing us to put validation checks.
Otherwise it could be specifying N, S, E or W, again before the validation checks were available.
If you want 6, 8 or 10 digit grid square (25m precision) 
For Chaser !
73, Éric F5JKK
1 Like
Hi Mike @WB2FUV 
On your QRZ lookup you have to go here and update your coordinates!
Can help you with the TK5EP tool
73, Éric F5JKK
1 Like
There appears to be wrinkle in the software.
When you try to edit old chaser entries prior to the Location field update they do not appear for edit.
I guess the old records do not have a Location field which is causing the edit page not to display any of the content. I put a new chase in and it appeared to edit OK.
I presume the Microwave locations from the comments (%QRA%IO84FL%) field will not auto populate the Location Field.
73 de Andrew G4VFL
1 Like