I’ve just corrected my lat/long as it was a couple of miles out. Not sure why it was wrong. I’m unlikely to chase 2m SSB/CW from home but you never know.
I just tested a few values at 3 and 3.5 decimal places in google maps until I found a pair that looked reasonable (i.e. not spot on someone else’s house, and near enough to mine). QRZ also updated to use the same numbers.
My previous two-decimal-places position wasn’t quite that far out, but definitely far enough out for me to need to zoom out a bit to find my place…
I think in some cases it is impossible to really know until something like this sort of challenge happens.
I worked M1DYU from billinge yesterday. The interesting thing is that he is literraly in the same 6 figure grid square as the summit, IO83PM, so I was wondering what kind of score it would generate. The answer (for my score) was 2km . Looking at the mapped qsos it also showed him in exactly the place I expected which suggested that his home location has been correctly input. So for the majority of the time , it would appear to anyone looking at the qso maps to be correct.
It was only the chaser challenge scores that had gone out of kilter. As a silly excersise I looked to see what ancient measurement it could have been converted to which would give the right answer. A “Span” (9 inches) is the closest I could come up with although a “Shaftment” is also pretty close.
One for the DB admins, is it easier for you guys to just correct these as they happen or have some kind of procedure that checks and flags up say scores over a certain amount for a qso (say 2000km). It probably the manual approach for now as that should be a decreasing workload over time, but in case of other similar challenges its worth making a note of.
Good to work you. First time for me using 2m SSB 
2 Likes
Part of the challenge was to give some of these GIS type features are good going over. People’s locations are stored in their SSO (the sign on account) database. A first programmatic fix is to run through all the accounts and find
- not in decimal degrees
- invalid characters
- latitude > +/-90 (indicates probably needs swapping with longitude)
All of those checks give absolute fixes. The harder fix is people who have swapped lat&long but the values are in range. e.g. mine is 55.9,-3.5 swapping it to -3.5, 55.9 gives a valid location, somewhere near The Seychelles. So to spot it as wrong involves converting the home association to a geographic extent and then checking the lat&long are inside that extent. I’m sure Andrew VK3ARR said there was something to aide with this but I can’t find where he said it now.
But… this is a “How do you eat an Elephant” kind of problem. You take lots and lots of small mouthfuls over some time rather than trying to swallow it in one go. And we have till Jan 1st 2027 (should Putin/Trump allow the world to continue that long) to fix it!
1 Like
Two decimal places is already more precise than a 6-digit locator which, at the same latitudes, is roughly 4.6 km (2.9 miles) N/S by 3.6 km (2.2 miles) E/W.
I notice 3 decimal places gets you almost on my house and 2 decimal places is in the nearby estuary. Better the latter so any bomb goes in the drink.
Probably easier to give your 6-digit locator rather than two decimal numbers (one of which could be negative, as with my QTH) especially in Morse.
Andy
[IO84of]
Over the air I would give my locator. I was referring to how accurate my position as a chaser would be when it came to the DB calculating my chaser challenge distance.
1 Like
Wishful thinking?
1 Like
23 SOTA summits so not a bad plan. Except there may not be so many summits in a few years time.
I’ve been wondering what ways there are for entering locations for QSO end-points into the database. So far, I figure:
-
An Activator’s location is determined automatically from their summit reference, so a Chaser (including another Activator working summit-to-summit) does not need to get a specific location from an Activator. The summit reference is all that’s needed.
-
A Chaser’s own location defaults to their lat/long location as entered in their SSO profile. If a Chaser is at their default location they don’t need to do anything more to get the location of their end of a QSO into the database. If, however, they’re chasing from some other location then (as far as I can tell) they need to upload an ADIF with either MY_GRIDSQUARE or MY_LAT and MY_LON set appropriately.
-
An Activator needs to get a location from each chaser, and can put that into the database using one of:
a) A %QRA%ZZ99ZA% type comment in the V2 .csv
b) Via ADIF location fields, either “GRIDSQUARE” or “LAT” and “LON”
c) Enter each location contact by contact via the website.
What have I missed/got wrong?