Uploading Custom Weather Records (CSV / Excel)
[!TIP] If your project uses an on-site weather station, a local rain gauge, or data from a regional agency, you can upload a custom CSV or Excel file.
The Climate Simulator accepts standard CSV (Comma-Separated Values) and Excel (.xlsx) files containing daily historical weather records.
File Format Requirements
Organize the spreadsheet with one row per calendar day and column headers.
Required & Supported Columns
Your file should include at least three columns:
- Date: Daily timestamp (supported formats include
YYYY-MM-DD,MM/DD/YYYY, orDD/MM/YYYY). - Precipitation: Daily rainfall or snow-water equivalent (depth per day).
- Daily Maximum Temperature ($T_{\max}$): Highest temperature recorded during that calendar day.
- Daily Minimum Temperature ($T_{\min}$): Lowest temperature recorded during that calendar day.
(Optional) You may also include:
- Average Temperature ($T_{\text{avg}}$): If $T_{\max}$ and $T_{\min}$ are missing, the engine can estimate daily ranges based on seasonal averages, though providing both daily maximum and minimum is recommended for calculating monthly temperature parameters.
- Solar Radiation or Wind: For future evaporation calculations.
Example Spreadsheet Layout
| Date | Precip (mm) | Tmax (C) | Tmin (C) |
|---|---|---|---|
2000-01-01 |
0.0 | 5.2 | -3.1 |
2000-01-02 |
14.8 | 3.1 | -1.0 |
2000-01-03 |
2.4 | 4.0 | -0.5 |
2000-01-04 |
0.0 | 7.8 | 0.2 |
(If using US Customary units, precipitation should be in inches and temperatures in °F).
How to Upload Your File
- In the Data Source card, click on the Custom Upload tab.
- Drag and drop your file into the upload dropzone, or click Browse Files to select your file from your computer.
- The Column Mapping Dialog will automatically appear:
- Match your spreadsheet's date column to Date Column.
- Match your precipitation column to Precipitation Column.
- Match your temperature columns to Tmax and Tmin.
- Select your file's native units (Metric: mm / °C or Imperial: in / °F).
- Click Import & Process.
Handling Missing Values & Gauge Outages
Field gauge records may contain missing entries due to power or equipment outages. The importer handles these entries as follows:
- Blank cells or
NaN: Treated as missing observations. - Flagged codes (e.g.,
-999orM): Standard missing data flags are converted to nulls. - Leap Years: February 29th observations are included in February parameter calculations.
[!WARNING] If your custom record contains long stretches of missing data (e.g. 6 consecutive months missing), it is best to filter out those incomplete years using the Date Range Filter so that monthly statistics are not skewed by incomplete records.