Update data format documentation

Author: ConnectedSystems

docs/src/expected_data_formats.md

@@ -7,8 +7,28 @@ By convention, Streamfall expects data to be formatted in the following manner:
 - Unit of measure itself is optionally included in square brackets (`[]`)
 - In-file comments are indicated with a hash (`#`)
 
+## Streamflow data
 
-## Example
+Data for a node representing a subcatchment or gauge should, at a minimum, include columns
+for date and streamflow (`Q`) in a consistent unit (in this case, megaliters/day).
+
+Streamflow columns should begin with its name and include an identifiable suffix.
+Here, `_Q` is used but this can be user-defined when preparing data for modelling.
+
+```csv
+# A comment
+Date,406219_Q_[ML]
+1988-07-23,0.5184
+1988-07-24,13.6512
+1988-07-25,407.6352
+1988-07-26,2488.4928
+1988-07-27,3443.6448
+... snip ...
+```
+
+## Dam releases
+
+Note that releases is denoted with `_releases`.
 
 ```csv
 # A comment
@@ -21,7 +41,6 @@ Date, 406000_releases_[ML], 406000_extractions_[ML]
 ... snip ...
 ```
 
-
 ## Climate data
 
 Streamfall currently expects data for all nodes to be stored in one large DataFrame.
@@ -30,7 +49,7 @@ Streamfall currently expects data for all nodes to be stored in one large DataFr
 ### Example climate data structure
 
 ```csv
-Date, 406214_rain, 406214_evap, 406219_rain, 406219_evap
+Date, 406214_P, 406214_ET, 406219_P, 406219_ET
 1981-01-01, 0.0, 4.8, 0.0, 4.9
 1981-01-02, 0.1, 0.5, 0.1, 3.3
 1981-01-03, 10.5, 5.3, 7.2, 2.3
@@ -39,6 +58,8 @@ Date, 406214_rain, 406214_evap, 406219_rain, 406219_evap
 ... snip ...
 ```
 
+where `P` indicates rainfall, and `ET` denotes evapotranspiration.
+
 ### Climate data functions
 
 ```@autodocs