I am really enjoying that you created the option to support the export of QSO directly into Wavelog.
This reduces my worfklow after an activation! Thank you K0UWU!
I did run into one issue when I was setting it up:
Wavelog defines the API Link as follows:
The API URL for this Wavelog instance is: https://wavelog.domain.de/
But PoLo is expecting the API Key in this format
Wavelog API URL https://wavelog.domain.de/index.php
(I changed the domain, and used it only for clearification)
So if the /index.php is not added it did not work for me.
I thought others might run into this as well, therefore I wanted to make you aware of it.
And it would be helpful for me if I can select the station to export during the export per operation. As I set up a station for every single activity. But maybe such a thing is already planned.
Thanks Lucas,
I too would like to see station management. But there needs to be an api to create the station in Wavelog instead of having to create it before the sync.
I’d be endlessly having to create a station, then syncing otherwise.
At them moment syncing into the wrong station forces the portable gridsquare to be overwritten by the Wavelog station grid.
How have you avoided sending operation QSOs to the “wrong” station? and having the grid overwritten?
Alan
And it would be helpful for me if I can select the station to export during the export per operation.
then I think we have a misunderstanding. Even as I like your idea, my start was meant way easier:
Now you have to set up the station which is used for export on the PoLo app Setup. I would like to use the same function, but not as „per app“ but instead „per Operation“. I am aware that I have to setup the station on wavelog end before I can export to it.
And regarding your question:
i set up the station on Wavelog before I headed out, then I logged the contacts with PoLo, and once I finished, I selected the station for
this activity in the polo settings and exported it via the new feature.
Yes, What I am suggesting is that it would be nice to have a way to create a station on Wavelog, from PoLo for a new operation. Without the need to first log into Wavelog and create that station.
This isn’t possible I know until/unless Wavelog consider it a worthy option.
But my question was around the irritation in the workflow of having to create a new station before each sync.
I don’t have to do this with my current system. It just creates a dynamic “station” when I import a log with a MY_GRIDSQUARE value that is not yet in my log.
It’s just a subtle thing but as far as workflow economy goes, it wins over the cost of the export/import steps.
I haven’t tested it yet but does the PoLo sync just happen or do you need to trigger a sync process. i.e. if you haven’t created a new station and set it as current, wont’ you get a bunch of QSOs end up in the wrong station?
I got quite the same errors in Wavelog when I tried to import ADIF that has /P suffix. Then I went to the “stations” and set the /P station to active and it imported fine.
Dunno why Wavelog thinks suffixes are not the same “station”.
Using the configured Station+Location overwrites the gridsquare and SOTA/POTA references of an operation! The information becomes irreversibly incorrect in the Wavelog log, is not recoverable unless the original PoLo logs are kept, and may be propagated to 3rd party services like LotW.
The Station+Location is a single combined primitive in Wavelog. The Wavelog API supports creating them and the Wavelog docs discuss this decision and its consequences. It’s worth a read.
Since Wavelog has this footgun, PoLo should discourage users from shooting themselves in the foot with it by prompting for which Wavelog Station+Location to use for each operation upload, not globally. There should be an option to “create new” using the information in the Operation Data. The “create” option would prevent data deletion, even if it’s incomplete and must be edited in Wavelog later. It would be pleasant if the list were sorted by distance from the operation location.
The difference in data structures bit me before (when uploading ADIF files directly to Wavelog, see their Github issue #788). I lost a lot of SOTA “station-locations” that I no longer have in PoLo.
Thanks Emma & team for your work on this and for being open to feedback.
