A look on SOTA Database reveals that the Lat/Long fields in the database are empty and that clicking the “history” link for that summit causes a database exception!
I suspect this is one that I noticed was missing the Lat/Long information a couple of weeks ago (when I was working on using the CSV download for my SOTA Log Editor) - but I forgot to mention it.
The other ‘feature’ I noticed was the inconsistency of what is entered into the GredRef1 and GridRef2 columns of the Summit CSV ranging from UK or Ireland NGR’s to various format’s of Lat/Long including a significant number with embedded HTML character codes and various combinations of quotes that break some library code that I was trying to use at the time.