leading zeroes

[SeanGlen]

I wondered if anyone else was seeing the same problem with leading zeroes in the timestamp. It seems that Excel likes to drop leading zeroes and RouteConverter likes to assume trailing zeroes.

I haven't got concrete examples yet. I just noticed it.
I use the Columbus P-10 GPS logger set to record a CSV file. I'm in and out of buildings all day and the tracker will have transcription errors, usually in the timestamp but I've seen location as well.
I open the CSV file in Excel, correct all of the typos, delete the points that have a speed of less than 1.0 and save the file.
I open the edited file in RouteConverter and it's a mess. A six hour trip took 48 hours.
I figured out the dropped leading zeroes in Excel and formatted the TIME column to be six digits (hh:mm:ss) and then save it.
If I leave the Excel file open and then open the same file in RouteConverter, it works but
If I close the Excel file, the formatting for leading zeroes didn't survive and opening the file in RouteConverter brings back the original problem of crazy timestamps
20000 is two o'clock in the morning
I force it to be 020000
If the leading zeroes are dropped, it reverts to 20000 which RouteConverter assumes to be 200000 or 20 o'cloque

Thanx,
Seán

[routeconverter]

Hi Sean,
please provide sample files and explain the steps you’re doing. I don’t understand what you want to achieve.

[nordlicht]

If I leave the Excel file open ....
If I close the Excel file

Hi Seán,

Excel is NOT a suitable CSV editor, you have to use a plain text editor like Notepad or Notepad++ (assumed you're on a Windows machine).

RouteConverter can open, modify and save Columbus CSV files directly, I don't understand why you take a detour to a second software.