Is there an acceptable practice to test log uploads on the SOTA database?
I haven’t actually done a SOTA activation, but I’d like to test how my app (Ham2K PoLo) interfaces with the SOTA program, so I’d like to be able to do a couple of test uploads.
POTA has the “K-TEST” reference for this. Is there something equivalent for SOTA?
Just load anything you want.
You have the ability to delete/change individual entries/QSOs from your upload as well as the entire log yourself.
Either via ‘SOTA Data > Logs’ page or via ‘SOTAData > Uploads > Manage Uploads’.
GL
73, Robert
So just pick a random summit, upload a made-up log, and then delete it afterwards. Great!
I assume you will be generating SOTA CSV or ADIF files. If you upload the file manually, then there is a webpage shown which shows what you are uploading. You can review the data to check it is what you think without submitting it to the database itself. i.e. generate file, upload it, review it and then delete it. WHen you think everything is correct you can submit it for another review. Later on you can delete it.
As far as I know there is no direct file upload API yet. But I might be wrong 
But Andrew @VK3ARR just recently teasered an update to Sotadata4 so I would suggest to have a chat with him. A log-upload API at least was under discussion during the Sotadata3 development but was not high on the priority list as far as I recall.
A log-upload API exists, but basically we have an intermediate format that CSV/ADIF/FLE files are converted into before being uploaded. There’s no intent to provide an API that directly reads a CSV/ADIF/FLE file and uploads it. Instead, that processing is done on the client front-end (SOTAData3).
I can’t remember teasing SOTAData4, so hopefully I haven’t overpromised 
Okay it was a new SotaWatch. My bad 
.