It’s probably not going to be fixed. Well maybe it will.
It’s barfing on what it claims is a malformed datetime item in the log. Your log looks OK to me (for what that is worth.) There’s two copies of the activation due to how sotamaps gets a local copy of the DB. I tried some changes in your log and that has confused sotamaps.
Eventually sotamaps will be led outside and taken round the back of the software shed, there’ll be a bang and that will be that.
You’ll have to live with Mark M0NOM’s chaser mapping software, SOTL.as and the functionality that moves and is still to move from sotamaps into the database.
How am I going to see then these beautiful pictures on sotamaps/activations?
How am I going to calculate that multi-band linked dipole?
But seriously, there is one bug in sotamaps/activations: I uploaded erroneously an activation for HB/LU-023, when this should have been HB/LU-013. Everyone can make a typo, right? I corrected this on sotadata (delete, correct and upload), but it still shows up on sotamaps.
Beauty, they say, is in the eye of the beholder … there are “workaday” (alltägliche) replacements for those sotamaps/activations views already in the database, although they may be missing a few of the “bells and whistles” familiar to users of the SMP.
You may be pleased to learn that a replacement for the multi-band linked dipole designer is being worked on, and will have more features than the one in the SMP. It will be hosted elsewhere…
You’ll have to wait for the sotamaps copy of the data to be updated…maybe 1/2 a day?
In that case, it’s a job for Andrew @VK3ARR to attend to, but it has to be said that the SMP is low on the list of priorities these days. Perhaps PM him?
Well, it’s not that important. Now that I know, that SMP will be retired, no need to invest much in bug-fixing / repairing. I’ll just miss the geographical display of QSOs.
But you won’t miss them, since they’re already there in the SOTA Database. Login, view a list of your activations, and click on the “map” icon in the list; example:
Ok, I get the hint , I should click on all those buttons.
But now, there is a discrepancy between sotamaps and sotadata: My nice connection to Brazil does not show on sotadata (I’ve entered on PV8AL’s QTH based on his QRZ.com entry on sotamaps), but a QSO with DJ3CE shows up, who appears to live in Somalia. On sotamaps, no geographical line appears (correct, as no location entered there). In the activation list, there are also others whose QTH is unknown, why are they not shown in sotadata or are they overlaid by the DJ3CE connection?
The display is actually quite nice, I like it. You can’t click to get the QSO details, but that’s a detail
Yes, there is a discrepancy between sotamaps and the SOTA “database”. This is because, right from the start, sotamaps/SMP was denied access to the main database, but provided with a copy of it in what amounted to a sealed room, and this copy db got updated every day, or most days anyway. In addition, the SMP had/has its’ own small database into which, among other things, a person’s QTH details could be entered: but those details were, and continue to be, available only to the SMP, but not to the main SOTA software.
An artful DB administrator - or one who cared sufficiently about such things - could, in a matter of minutes, easily write a script to import such QTH details from the SMP’s database to the main database, thus making a lot more such details available to the wider SOTA community. Will this happen any time soon? - it’s a moot point but, based on my own experiences, I would say probably, most likely, “no”.
Actually, it was copied over just prior to the SD3 launch. It also incorporates updates from SSO profile amongst other places.
The cron to update from QRZ has been disabled for years, and predates me doing anything with it. It’s half written to convert that to point at the main database version of the table, not the SMP version, but we’re so far behind because it’s been disabled for so long that whenever I test it I hit ratelimits on the QRZ.com API. I suspect it’d take several days to get everything updated from QRZ but I haven’t seriously quantified it.
Just to add a factor to this topic - I logged a S2S with 2E0BIA on 10/6 from Holme Fell (G/LD-051). He was on Stony Cove Pike (G/LD-018), yet the map on SOTAData shows him as being in London. During the same activation I also logged a S2S with M0JKS on High Stile (G/LD-012), who is shown as being in the Indian Ocean (pretty good for 2m FM!). So there seems to also be an issue with displaying some summits correctly.
thx
, I should click on all those buttons.