A typical example for a STP Table for non-irrigation demands is table STP_MUNICIPAL (only a very small selection of records is shown):
| SETT_ID | SCENARIO | YEAR | MONTH | DEMAND | SALINITY | LOG_SESSION | USER_NAME | DATE_SAVED |
|---|---|---|---|---|---|---|---|---|
| 3 | 0 | 1998 | 3 | 434 | 0 | |||
| 3 | 0 | 1998 | 4 | 396 | 0 | |||
| 3 | 0 | 1998 | 5 | 396 | 0 | |||
| 3 | 0 | 1998 | 6 | 396 | 0 | |||
| 3 | 0 | 1998 | 7 | 382 | 0 | |||
| 1135 | 1 | 2005 | 1 | 332 | 1 | Mpreproc20021104-231020 | preproc | 04/11/2002 23:11:27 |
| 1135 | 1 | 2005 | 2 | 332 | 1 | Mpreproc20021104-231020 | preproc | 04/11/2002 23:11:27 |
| 1135 | 1 | 2005 | 3 | 332 | 1 | Mpreproc20021104-231020 | preproc | 04/11/2002 23:11:27 |
| 1135 | 1 | 2005 | 4 | 332 | 1 | Mpreproc20021104-231020 | preproc | 04/11/2002 23:11:27 |
| 1135 | 1 | 2005 | 5 | 332 | 1 | Mpreproc20021104-231020 | preproc | 04/11/2002 23:11:27 |
Please note, that the results for all locations (= SETT_ID), scenarios (1, 2 or 3), months (1, 2 ... ) and years (both historical and projections) are stored in the same database table. Historical years have scenario 0. SALINITY indicates the salinity class.
The LOG_SESSION is needed to recall the parameters that were used to calculate that demand under the Pre-Processing module.