14. Irrigation#
The FeST model can simulate water derivation from rivers and distribution on irrigation districts.
Irrigation simulation is activated by filling in the specific section in the main configuration file
( Section 3.13 ).
This chapter describes the irrigation configuration file, usually named intakes.ini.
The irrigation configuration file contains two main keywords as described in the following Table.
Keyword |
Description |
Requirements |
|---|---|---|
|
Number of intakes to configure |
MANDATORY |
|
EPSG code of the coordinate reference system used for intake coordinates. It is used only to write EPSG code in output file |
MANDATORY |
For each intake the user must configure the specific section numbered from 1 to the total number of intakes, filling in the required information as listed and described in the following table. Several intakes can exist at the same location and multiple intakes can discharge water to the same irrigated area.
Keyword |
Description |
Requirements |
|---|---|---|
|
Label Id of intake. |
MANDATORY. |
|
Name of the intake |
MANDATORY |
|
x-coordinate of intake on the watercourse |
MANDATORY |
|
y-coordinate of intake on the watercourse |
MANDATORY |
|
environmental flow (m³/s), minimum value of discharge to be released downstream the intake. To assign a changeable value during the year, a table on external file must be assigned (see example below) |
MANDATORY |
|
Maximum discharge (m³/s) that can be diverted from the river. To assign a changeable value during the year, a table on external file must be assigned (see example below) |
MANDATORY |
|
Day of year (1-365) when irrigation starts. |
MANDATORY |
|
Day of year (1-365) when irrigation stops. |
MANDATORY |
|
Maximum mean saturation of the irrigation district above which irrigation water is not distributed (option not yet implemented in the model). |
MANDATORY |
|
Map of the irrigation district |
MANDATORY |
In the following examples two intakes are configured. In the first one, maximum diverted flow and ecological flow change in time and are assigned with a table provided from external files. In the second intake, maximum flow and ecological flow are assigned as a constant value. Water diverted from both intakes is used for irrigation of the same irrigation district.
Example of intake configuration for managing irrigation.
###############################################
# Intakes configuration file #
###############################################
count = 2
epsg = 32633
[1]
name = intake_1
id = 01
easting = 301950.9
northing = 5064960.3
max-discharge = ./data/qmax_intake1.tab
e-flow = ./data/eflow_intake1.tab
doy-start = 105
doy-stop = 258
sat-max = 0.5
eta = 0.6
[[mask]] # mask of irrigated district
file = ./data/district.asc
format = esri-ascii
epsg = 32633
[2]
name = intake_2
id = 02
easting = 311050.9
northing = 5065380.2
max-discharge = 100. # [m3/s]
e-flow = 8. # [m3/s]
doy-start = 100
doy-stop = 220
sat-max = 0.5
eta = 0.8
[[mask]] # mask of irrigated district
file = ./data/district.asc
format = esri-ascii
epsg = 32633
Content of qmax_intake1.tab is reported as follows. In this example time
span between 31 and 90 doy is not included in the table. In this
period a value of zero is assigned to maximum flow.
Table Start
Title: Qmax intake 1
id: qmax
Columns: [count] [doy-start] [doy-stop] [value]
Units: [-] [day] [day] [m3/s]
1 1 30 15
2 91 200 35
3 201 365 18
Table End
Content of eflow_intake1.tab is reported as follows. In this example a discharge value is assigned for each month of the year.
Table Start
Title: eflow intake 1
id: eflow
Columns: [count] [doy-start] [doy-stop] [value]
Units: [-] [day] [day] [m3/s]
1 1 31 1
2 32 59 1.5
3 60 90 1.6
4 91 120 2
5 121 151 1.8
6 152 181 1.7
7 182 212 1.9
8 213 243 1.8
9 244 273 1.5
10 274 304 1.3
11 305 334 1.2
12 335 365 1
Table End
Two output files are created and populated during simulation:
<folder>irrigation_downstream.fts that contains river discharge downstream the intake,
<folder>irrigation_upstream.fts that contains river discharge upstream the intake,
and <folder>irrigation_diverted.fts that contains the diverted discharge values,
where <folder> is the output folder (and prefix) for writing output files (see Section 3.2 ).
An example of output file for diverted discharge is reported as follows.
description = irrigation discharge diverted from water courses
unit = m3/s
epsg = 32633
count = 2
dt = 3600
missing-data = -999.900
offsetz = 0.000
metadata
intake_1 01 301950.9 5064960.3 0.0
intake_2 02 311050.9 5065380.2 0.0
data
DateTime 01 02
2011-01-01T00:00:00+00:00 0.00 0.00
2011-01-01T01:00:00+00:00 0.00 0.00
2011-01-01T02:00:00+00:00 0.00 0.00
2011-01-01T03:00:00+00:00 0.00 0.00
2011-01-01T04:00:00+00:00 0.00 0.00
2011-01-01T05:00:00+00:00 0.00 0.00
2011-01-01T06:00:00+00:00 0.00 0.00
…
…
2011-05-01T00:00:00+00:00 28.18 32.01
2011-05-01T01:00:00+00:00 32.24 33.12
2011-05-01T02:00:00+00:00 34.45 34.15
2011-05-01T03:00:00+00:00 35.00 33.34
2011-05-01T04:00:00+00:00 35.00 38.10
2011-05-01T05:00:00+00:00 35.00 42.06
2011-05-01T06:00:00+00:00 35.00 44.78
…