SYNOP

[Pascal66]

Have you compared it to a log file produced by WD to ensure that you have the same spacing between fields, leading/trailing zeros and decimal places?

Now, yes, all are formatted like original, and.. still nothing :s
But, Brian you can't know how is formated your own .....lg.txt produced by WD ???
i've just to put sprintf everywhere is nedeed as WD create it.

I need some clues. And prefer this way than create a csv and import it after, i think it's more productive, even for those who need to rebuild data.

Or i'm in a wrong way, i don't know.

[Pascal66]

The one thing I do know after converting lg files to excel is that the first column for days 1-9 of a month are a space character then the numeric.  I have successfully converted them back again with that column shift incorporated and they have been valid text lg files.  That may not matter at all for the WD parser converting to data files for the graphs.  It may be more for cosmetic viewing structure for column alignments.

I see those strange spaces and lead/train 0 for not all values...
I just miss one space i dont know where.
Some parts of WD read le ....lg.txt and some not.
I'm searching and loose my time for a space...
THank you TokKiwi

[Pascal66]

Something strange today :
After reading my self formatted myyyylg.txt, i still cant view it in graph or noaa report. BUT
Values are interpreted correctly in view->all time records and view->data log files

So my new idea is that WD use sometimes bin files and sometimes txt files ??
Thank you