Just wanted to let everyone know that I have new versions of my ADIF to SOTA CSV apps for Macintosh based logging apps. Due to differences in the the way the three big Mac Logging apps (MacLoggerDX, Aether & RUMlog) handle their log files, I decided to create a separate app for each logging app. I may merge them back into one app in the future, but this was a quick and dirty way to get something workable for everyone. Please let me know if you have any questions or problems with the apps.
With the exception of the version for the latest MacLoggerDX which supports the SOTA ADIF fields, all of the apps are expecting the SOTA data to be in my ‘standard’ data format as described on my website. You are welcome to alter the underlying PHP script to meet your needs and the PHP script(s) could be easily adapted for command line use for the linux/unix folks. All of the apps will ignore any contacts that don’t have the requisite SOTA information and will produce a single V2 comma separated values file, suitable for upload as a Chaser/S2S or an Activator log as fitting.
MLDX->SOTA - For new versions of MLDX which support the new ADIF SOTA fields. ADIF export can contain both activator and chaser entries intermingled.
MacLoggerDX to SOTA - For older versions of MLDX using my standard data format. ADIF export must contain only chaser or activator/S2S entries.
Aether->SOTA - One line of the comments field must be formatted according to my data format. Other lines of the comments field may be used for other purposes. ADIF export must contain only chaser or activator/S2S entries.
RUMlog->SOTA - The notes field must be formatted according to my data format. ADIF export must contain only chaser or activator/S2S entries.
Hi, as a Mac user and SOTA chaser and activator I am keen to try out anything which could simplify the logging workflow, and your applications look very useful. However, after dowloading Rumlog->SOTA I could not make drag and drop work with it. No matter how I try to drag my RUMped-exported ADIF file onto the app icon, I can’t accomplish anything. Have you considered an alternative version of supplying the ADIF file? There’s File/Open menu, but it does not work either. I am using OS X 10.8.5 and I’ll appreciate any help.
I am sorry you are having difficulties in using my small app. Are you formatting the notes field according to ‘my standard data format’?
If the script finds no valid SOTA information, there will be no output file. I will be glad to make RUMlog->SOTA prompt for a file location, if that is what others prefer.
I have had several emails with the developer of RUMlog (Tom, DL2RUM) and there is a little known SOTA export capability straight out of RUMlog. It is currently not doing v2 CSV files, but he is now aware of the new format. Here are some notes from Tom:
"In the log just enter the SOTA reference into the note field. The export looks like this:
“thanks for the quick response.
Well, the SOTA export function is a little bit hidden. Use the Search Window (Menu–>Window–>Search) and search for QSOs, most probably by date. Select the desired QSOs in the table below (or nothing if all QSOs are affected) and select the “SOTA” option from the popup menu on the right hand side. Push the “Export” button.”
I have been expecting a few snags when other people start to use my apps. The scripts were created with my workflow in mind and work well with my processes. Marcin was kind enough to send me a log file and a few changes were needed to make the script a little more forgiving and reliable. This has been very helpful and a new version of RUMlog->SOTA has been uploaded to my website. I will add the modifications to the other versions and updated versions will be available soon.
thanks for excellent and very fast support, the new version of your app works perfectly. It is a very useful tool for all Mac users who are chasing and/or activating SOTA.
thanks for excellent and very fast support, the new version of your
app works perfectly. It is a very useful tool for all Mac users who
are chasing and/or activating SOTA.
Thanks Marcin! It is such a simple thing, but it makes my SOTA life so much easier.
I have been using Rumlog for several years but didn’t know SOTA export
is that easy.
I guess you are referring to the limited built-in export in RUMlog. I think that was added as a feature for a single user and never publicized. But, it outputs the older CSV format and doesn’t offer the additional features that my app provides. Hopefully, Tom-DL2RUM will add v2 support and also makes the export function more accessible. I encourage all RUMlog users to contact Tom and request that he adds the two new ADIF defined SOTA fields. That takes any ambiguity out of your SOTA contacts. There is no question whether it is a activator, chaser, or S2S entry.