Received an email ref discrepancies with the G/DC Grid reference and maps.
In looking at G/DC-001 shows Grid 50.68520 and map shows somewhere in Egypt and Distance of 7937 kms!
Several other G areas appear to have same problem.
My other area G/SC-001 shows correct Grid SS 891415 and corresponding map.
Jimmy M0HGY (G Association Manager) has just updated the G ARM. This takes account of the changes advised in the newly issued MARHOFN. Changes are all slight coordinate/height data changes, but nothing that would cause anything significant like a promotion/demotion, points band change etc.
His work was all correct and accurate, and can be seen by pulling up the new G ARM from the SOTA website (click on “Website” above).
However, when it came to my job of uploading the updates to the Database, I managed to make an almighty cock-up in the preparation of the tables. The result is the wrong coordinate information you are seeing.
I apologise to all (especially Andy MM0FMF and Jon GM4ZFZ for whom I have created extra work) for this error, but be sure we are working on it and it should be rectified soon. As usual, the Database will be fixed first, then there may be a short delay before the corrections filter through to SOTAwatch.
The affected regions are CE, DC, LD, NP, SE, SP and WB. SC, SB and TW should be unaffected.
In reply to M1EYP:
Ah, the old “Lat/Long” vs “Long/Lat” trick… done that one myself a few times.
Easy done.
Ironically it is “little cock ups” like this that actually show all the hard work that goes on in the background.
It’s a bit like my day job working on phone systems. Everyone just expects “dial tone” and doesn’t think about all the hard work going on in the background. It’s only when something goes wrong that we can all appreciate the work that usually happens without anyone noticing.
Yeah, the lats went in in place of the longs. But what went in in place of the lats was actually the NGRs. The longs did not go in at all…
I have completed all the remedial actions I can do so far, and it appears from the Database that Andy has sprinkled his magic dust on that and made all the rest of the data correct. SOTAwatch should follow soon…
So Jimmy emailed me and asked how he should format his updates which he explained was mainly a documentation fix, positions, callsigns etc. Relatively unimportant cruft.
“Correctly Jimmy.” was my flippant reply. And he did it correctly. Every i was dotted, every t crossed. Squeakily perfect. Then he handed his work of art to me and Tom, The Chuckle Brothers!
What we both forgot to tell Jimmy was that UK associations are handled differently to every where else. We don’t update them very often so we both forgot as well.
And lo, it came to pass that all the beautifully formatted data did spew out all over the database causing the very fabric of geo-spatial coordinates to be torn asunder. Or latitude became longitude and stuff moved from England to South of Ghana. Which isn’t what we wanted.
“Oh dear!” I said when I saw that the flux capacitor had leaked everywhere. Well that’s easy to fix and I conjured up a quick Expelliarmus and swapped lat & long. Trivial I thought and wondered who I could blame for this as I’d looked at the input data before Tom uploaded it and declared it kosher.
Except it’s worse. Remember I said we did UK association differently. Well they’re all keyed off NGR not lat & long. NGR only applies to UK summits and there is some slight of hand at work. Basically Jimmy’s file has all the right data but not necessarily in the right order.
My fellow partner in ineptitude, Tom, has grubbed about in Jimmy’s file and we have now got all the UK summits to have the correct NGR. Some of them display the correct lat & long and Maidenhead locator. Some of them display almost the correct lat & long and Maidenhead locator. Some of them are just wrong. It’s left as an exercise to the user to figure out which is which!
The NGR’s for G summits are correct. But only on the database website, SOTAwatch is wrong. The lat & long for G summits maybe wrong. The incorrect data will be fixed over the next few days. When it’s all done then we’ll get SOTAwatch updated but there’s no point in the meantime. I reckon there’s 22 summits in slightly the wrong place. Or there’s 22 areas of map which are wrong because the database is always correct! Look we could have played with W7 and borked the locations of 17500 summits. So it’s not all bad
Sir Arthur Charles Clarke, CBE, FRAS,(16 December 1917 – 19 March 2008) was a British science fiction writer and inventor and futurist. I think the clue is in the word Fiction.
Well I downloaded the golden CSV file and latest summitslist.csv and wrote a script that found the rubbishy looking latitudes and spouted forth a whole plethora of “UPDATE SUMMITDATA WHERE SUMMIT=‘G/LD-052’” etc. lines. I ran that on the console and lo… the data looks reasonable.
It all worked first time and that has to be magic!