New version of SOTAData enters extended Beta stage

As we’ve been hinting for a while, there’s a new version of SOTAMaps and sotadata that will be integrated via Single Sign-On. In the spirit of Christmas, as a gift to all, I’m making it available for extended Beta stage. The old versions will still work concurrently with the existing ones, but you can play around and see the new version. The main change is the deprecation of the V1 CSV/TSV format, and replacing the separate Chaser/Activator upload so that you can upload a single CSV containing Chaser records, Activator records and S2S records all in one go.

The other changes are under the surface, allowing us a lot more flexibility in separating the interface from the database itself, plus the addition of SSL. These are less likely to be visible. Rob and I will work over the next few days to configure the new SOTA Mapping Project to go live too.

I’d like to call out a special thanks to my initial Beta testers who provided feedback: DB7MM, DD5LP, G4AZS, HB9DQM, M1MAJ, N0MAP, VK1AD and VK2IO. If I’ve forgotten anyone, my apologies.

I could just provide you the link, but it’s Christmas, and that means everything has to be a riddle (nice crossword, Rob - I learnt to love summitslist.csv!). Here’s a little tour around the SOTA world that at the end will take you to the new sotadata website.

  1. VK2/ST-041
  2. FL/VO-143
  3. ZL1/NL-099
  4. G/NP-010
  5. HL/US-001
  6. ZS/EC-098
  7. W7N/NS-180
  8. W7N/NN-231
  9. EI/IW-002
  10. JX/JM-004
  11. VK7/WC-058
  12. W2/GC-122
  13. TF/NL-069
  14. FK/NP-074
  15. ZS/WC-448
  16. V5/KA-531
  17. PR8/CM-008
  18. R9U/CE-069
  19. PY1/MM-018
  20. W7M/GA-121
  21. SP/BZ-008
  22. LA/VA-072
  23. W4T/SU-009
  24. TI/CA-036
  25. DM/TH-500
  26. EA4/TO-033
  27. DM/BW-794
  28. VP8/SG-232
  29. HB/LU-023
  30. OY/OY-007
  31. JA8/OM-038
  32. KLS/JU-201

thanks for the riddle … i found my way to the new sotadata website! but I’m not sure if i have to register as a new user for the new database or just one of the old passwords?!

73 martin, oe5reo

I too found the new Database, looks good!
Thanks for the work.

But I admit I am a bit confused:
There seem to be quit a few summits in the database which can not be found via

SOTA Summits ??

Example are the 2 entries 25. and 27. above…

merry Christmas and cu on the summit
Mark, HB9DBM

Ups… just found my “error”. the Database also holds summitinfo from summits which are no longer valid…

Never mind…

The actual database engine and store is the same. We just have 2 web front ends talking to the same data store. You use the same credentials as before.

Well I found it, but one of the clues appears to give a bogus character (from the CSV but not if using the database web site).

To clarify that it appears the viewing the Summit Names by opening the CSV in Microsoft Office (or other tools that use the Microsoft libraries for opening CSV files) in-correctly shows a number of strange characters for Summit names that have letters with accents. Opening the CSV in some Text only editors shows what I presume are the correct letters.

Just found this ten minutes ago - two of the summits appear to be no longer valid, but it’s pretty obvious what they should represent. So, I can finally view the new site, thanks…

All users on the database have been merged across with equivalent password credentials. Use your existing sotadata password to log in.

Oh, validity, right. I just scanned the database tables for summits that met my needs and chose associations around the world. I would pick the one association that has substantial deletions :smile:

MS Office is likely defaulting to ISO-1159-1 rather than UTF-8 as the character encoding.

Yes, it’s a pain that it does this. You need to import the data and change the file type in the import wizard as Excel ignores BOM in files.

The easier way is to stop using Office and use LibreOffice. For me LO does all I want, runs on low end machines as well as higher spec PCs and gives the same results on Linux and Windows. It’s free too but you can make donations.

1 Like

Is Peter VK3ZPF aware of the planned retirement of V1 format. VK Port-a-log ‘Activator Log’ output is currently set to V1 format.

Andrew VK1AD

1 Like

Yes he is, and will release a V2 only Port-A-Log soon

1 Like

Just a quick comment to say that if anybody is having time-out problems while logged in to this new SOTAData site, then please let us know here, giving details of your operating system and browser.


Finally found it too.
I was thinking way to complicated - haha story of my life :wink: - reading css thinking there is some css (cascaded style sheet) code hiding something … omg it’s so simple.

Btw. do I see that correct that there is now only one csv upload? That is a nice simplification to my usual log preparation and upload workflow. Now not having to extract the S2S extra for the chaser log is nice.

And mobile use on Android/Chrome is finally working too :+1:

Edit: almost. Selecting the Show analysis checkbox breaks the table format.

73 Joe

Hi Joe,
Yes the upload now takes care of S2S entries for you from your activation log, you don’t need to go into the chaser section separately as you used to have to do.

73 Ed.

1 Like

Viewing the sotadata site and looking at reports, I notice that the Analysis option offers band by band analysis of an activator log, but does not offer analysis by mode. The options on those reports to list by band or mode are also not offered in the version currently displayed. I hope those options will be returned eventually.

The login cookie appears to be still intact after 24 hours too.

The site appears to work smoothly on my system here (windows 10, Chrome browser).

thanks guys, great progress, big job.

73 Andrew VK1DA/2UH

(decoded the site address in an excel spreadsheet using vlookup, couldn’t just search the names list manually!)

Indeed, this is the major cosmetic feature update

The new interface works soooo much better with my Samsung tablet and phone. I always had problems getting the drop down menus to initiate and even changed from Firefox to Opera to effect an improvement, but even that was unreliable.

Many thanks for all the hard work put that has been put in. :+1:

73, Gerald

Thank you @VK3ARR for the advance notice a few months back. I have been very busy with life in general and have made no progress toward V2 only .csv file output. That said, it won’t take long once I start as the code is already in the app - has been there for 4 years - I just need to make it work.

One question, is the database that the beta page interacts with the real production database, or can I just upload whatever I want and fear nothing?

73 Peter VK3ZPF