Date format with SOTA export

[ON4ZD]

Sorry if this topic has been covered before, but I can't find the answer.
In my LOG4OM, the date format is DD-MM-YYY, same format if I export a SOTA file to upload it to the SOTA database.
This format is refused by SOTA because it must be in DD/MM/YYY format (/ instead of -).
It is therefore necessary to edit and correct the file before uploading to the SOTA database.
How to change the date format in Log4OM. The export examples in the manual are in the correct format.

[G4POP]

Have you tried exporting an ADIF file for the QSO's from Log4OM and uploading that? because I know SOTA accept a normally formatted ADIF

We will check the actual SOTA export

[G4POP]

I have now checked and it appears that the format we export in is what SOTA demand see https://www.sotadata.org.uk/en/upload/a ... r/csv/info

SOTA example from their web site


V2,G3WGV,,10/06/03,1023,432MHz,FM,G4TJC,G/SP-015,Simon (chaser entry)


Example SOTE export from Log4OM


V2,G4POP,,28/03/2014,1010,5.3985MHz,SSB,M0IML/P,G/SE-013,



Date separator is the same

[ON4ZD]

Hello,
Thanks for the quick response, but that doesn't satisfy me completely.
I know the syntax for the SOTA upload, you need the DD/MM/YYY format otherwise the upload gives an error in the date format.
In my log4OM2 version 2.23 all dates are in DD-MM-YYYY format (Why ??) and are therefore exported according to this format.
For uploading to SOTA, I have to edit the CSV file with notepad to change the format.
An adif export gives syntax like ''<QSO_DATE:8>20220828 is correct and accepted.
Where is my problem between / and - ?
Here is a copy of a QSO exported by my Log4OM2 with the date separator as -
V2,ON4ZD,,23-08-2022,0740,14.044MHz,CW,ON5JT/P,ON/ON-027

[KI5IO]

Leon,

Just curious ... what does your Recent QSO (F7) grid show for date? How about the grid display in the QSO Manager window?

Also (just thinking outside of the box here) what are your time/date settings in your computer?

Image below is a clip from my Recent QSO (F7) grid.

I just did some testing with my Windows O/S settings and depending upon various settings the date format with the hyphen will appear.

Log4OM uses the date/time format that you have selected for your Windows O/S. This may be the source of the issue you have noted.
.

[G4POP]

Hello,
Thanks for the quick response, but that doesn't satisfy me completely.
I know the syntax for the SOTA upload, you need the DD/MM/YYY format otherwise the upload gives an error in the date format.
In my log4OM2 version 2.23 all dates are in DD-MM-YYYY format (Why ??) and are therefore exported according to this format.
For uploading to SOTA, I have to edit the CSV file with notepad to change the format.
An adif export gives syntax like ''<QSO_DATE:8>20220828 is correct and accepted.
Where is my problem between / and - ?
Here is a copy of a QSO exported by my Log4OM2 with the date separator as -
V2,ON4ZD,,23-08-2022,0740,14.044MHz,CW,ON5JT/P,ON/ON-027

Your different exported date format probably is due to your windows date format

[ON4ZD]

Hello
Problem solved, it is the format defined in Windows 10 that had to be changed.
Thanks for your help.
73's de Leon