Input data is specific to the component models that you use, but typically consists of climate, topography, land use, rainfall, and management practices. Examples of these are provided in Tables 1 and 2.
...
- If the format is ISO 8601 compliant, this format will be used to read all subsequent dates;
- Failing that, an attempt is made to detect the dates and time - step with English-Australia ("en-AU") settings, for backward-compatibility reasons; and
- Last, the computer configuration is used for regional and language settings.
Possible problems with time-steps
Incorrectly-formatted date and/or time entries will result in errors if (eg. if Source is is unable to interpret your data file. You may also need to check your data if you use an ambiguous date format rather than the recommended ISO-8601 format.
There are two known problems where a time step may be incorrectly detected. First, when :
- When reading a file on a computer with
...
- US settings, because of the mm/dd/yyyy date format. This may happen if the whole of a daily time series covers less than 13 days, or less than 12 months for a monthly time series
...
- ; or
- When reading a file which has years in two digit format (eg. 30/01/99) instead of four digit format (eg. 30/01/1999).
...
Examples
Parsing the following file would raise an exception. Missing entries are not allowed since their interpretation may lead to ambiguities (ie. missing data, or zero record).
2000-01-01,0.9
2000-01-02,2.2
2000-01-05,1.1
2000-01-06,1.1
The following file, generated with Excel, will be recognised as a monthly time series on a computer with U.S culture (locale) settings, but loading it on a computer with different culture settings will likely fail:
01/01/2000,0.1
02/01/2000,0.8
03/01/2000,0.6
04/01/2000,0.9
05/01/2000,0.6
06/01/2000,0.4
07/01/2000,0.6
08/01/2000,0.2
09/01/2000,0.8
10/01/2000,0.6
11/01/2000,0.3
12/01/2000,0.1
01/01/2001,0.389
02/01/2001,0.389
...
| icon | false |
|---|
...
- An error will occur if your time series has the two-digit years 29 and 30. In this case 29 is read in as 2029, and 30 is read in as 1930. Note that data exported from Excel in *.csv format will be saved with the displayed date.
Both problems can be avoided by using the recommended ISO 8601 format to prevent ambiguity.
Predicted or calculated data
...