Difference between revisions of "GPKG Time Series Format Specification"
Ellis Symons (talk | contribs) |
Ellis Symons (talk | contribs) |
||
| Line 3: | Line 3: | ||
===GIS Layers=== | ===GIS Layers=== | ||
The results are stored in GPKG layers, typically between 1 - 3 layers are stored in the result file depending on the output (one for point results, one for line results, one for polygon results). There is no requirement against storing results from multiple model runs in a single GPKG, this is just not typically how outputs are written.<Br> | The results are stored in GPKG layers, typically between 1 - 3 layers are stored in the result file depending on the output (one for point results, one for line results, one for polygon results). There is no requirement against storing results from multiple model runs in a single GPKG, this is just not typically how outputs are written.<Br> | ||
| + | <br> | ||
The column names of the GPKG layers should follow the convention below:<br> | The column names of the GPKG layers should follow the convention below:<br> | ||
{| class="wikitable" style="width:40%" | {| class="wikitable" style="width:40%" | ||
Revision as of 02:22, 10 November 2023
The below section lists the TUFLOW GPKG time series format specification. The specification sits ontop of the GPKG v1.2 Specification with two additional required tables. The below lists the details of the additional tables with examples. The examples are based a the 1D/2D linked TUFLOW-SWMM example model based on TUFLOW's module 6 tutorial model - M06_5m_003.tcf.
GIS Layers
The results are stored in GPKG layers, typically between 1 - 3 layers are stored in the result file depending on the output (one for point results, one for line results, one for polygon results). There is no requirement against storing results from multiple model runs in a single GPKG, this is just not typically how outputs are written.
The column names of the GPKG layers should follow the convention below:
| Column Name | Type | Description |
|---|---|---|
| fid | INTEGER | Primary key |
| geometry | GEOMETRY | GeoPackage Geometry |
| ID | TEXT | Element ID (e.g. Pipe1) |
| Type | TEXT | Element Type (e.g. CONDUIT) |
| Source | TEXT | Result Source (e.g. SWMM) |
| TimeId | INTEGER | Unique id for each timestep |
| Time_hours | FLOAT | Output time in hours |
| Datetime | DATETIME | Output time in datetime |
| ...[column for each result type for that given geometry type - examples below] | ||
| Flow | FLOAT | Result flow |
| Velocity | FLOAT | Result velocity |