Dayfile.txt: Difference between revisions

181 bytes added ,  12:36, 9 September 2013
m
→‎Manipulation outside Cumulus: add further unknown value examples
m (→‎Dealing with rogue measurements: Correcting 'correcting' in last line)
m (→‎Manipulation outside Cumulus: add further unknown value examples)
Line 41: Line 41:
'''Important Rules''':  
'''Important Rules''':  
* The (meteorological) date format uses ''two digits for the year''. Edit this file using an editor that treats all fields as text (a text editor or a spreadsheet program that can be instructed ''not'' to recognise special field types).  -  ''Do not edit this file using Excel'' or any similar tool that recognizes dates, as it is likely to change the dates to have four figure years, and then Cumulus will no longer be able to use the file.  
* The (meteorological) date format uses ''two digits for the year''. Edit this file using an editor that treats all fields as text (a text editor or a spreadsheet program that can be instructed ''not'' to recognise special field types).  -  ''Do not edit this file using Excel'' or any similar tool that recognizes dates, as it is likely to change the dates to have four figure years, and then Cumulus will no longer be able to use the file.  
* Times are in ''format hh:mm'', and most value fields are in format x.y using your system decimal notation, a few are integers.
* Times are in ''format hh:mm'', and most value fields are in format x.y using your system decimal notation, a few (e.g. bearings, solar, humidity) are integers.
* If you insert a ''lowest or highest value'' into a day, where there was none before, insert a ''timestamp'' too, as a dayfile.txt row is only accepted by the Cumulus editor if a value and any related timestamp are either both present or both absent.  
* If you insert a ''lowest or highest value'' into a day, where there was none before, insert a ''timestamp'' too, as a dayfile.txt row is only accepted by the Cumulus editor if a value and any related timestamp are either both present or both absent. (Use a timestamp of your rollovertime 00:00, 09:00 or 10:00 if you have not looked up the precise time).
* Nulls ',,' are not allowed in the line, so if you do not know the value for a particular field within the line, then type in an extreme with opposite value (e.g. -999.9 for a signed decimal maximum, and 999.9 for a decimal minimum - assuming your system decimal format is using full stops).
* Nulls ',,' are not allowed in the line, so if you do not know the value for a particular field within the line, then type in a zero for integer values and an extreme with opposite value (e.g. -999.9 for a signed decimal maximum, and 999.9 for a decimal minimum) for decimal format (replace the full stops with your decimal separator).
* Make sure that any editing does not create any ''blank lines'' in the file.
* Make sure that any editing does not create any ''blank lines'' in the file.
* All rows must ''start with date'' and include some of the parameters listed ''in correct sequence''.
* All rows must ''start with date'' and include some of the parameters listed ''in correct sequence''.
5,838

edits