Difference between revisions of "GPKG Time Series Format Specification"

From Tuflow
Jump to navigation Jump to search
Line 48: Line 48:
 
! style="background-color:#005581; font-weight:bold; color:white;" width=5%| Series_units
 
! style="background-color:#005581; font-weight:bold; color:white;" width=5%| Series_units
 
|-
 
|-
−
|1||M06_5m_003_swmm_ts_P||22||hours since 2020-01-01 00:00:00||0.083333||Depth||Depth||m
+
|1||M06_5m_003_swmm_ts_P||22||hours since 2020-01-01 00:00:00||1.0||Depth||Depth||m
 
|-
 
|-
−
|2||M06_5m_003_swmm_ts_P||22||hours since 2020-01-01 00:00:00||0.083333||Water Level||Water Level||m
+
|2||M06_5m_003_swmm_ts_P||22||hours since 2020-01-01 00:00:00||1.0||Water Level||Water Level||m
 
|-
 
|-
−
|3||M06_5m_003_swmm_ts_P||22||hours since 2020-01-01 00:00:00||0.083333||Storage Volume||Storage Volume||m3
+
|3||M06_5m_003_swmm_ts_P||22||hours since 2020-01-01 00:00:00||1.0||Storage Volume||Storage Volume||m3
 
|-
 
|-
−
|4||M06_5m_003_swmm_ts_L||18||hours since 2020-01-01 00:00:00||0.083333||Flow||Flow||cms
+
|4||M06_5m_003_swmm_ts_L||18||hours since 2020-01-01 00:00:00||1.0||Flow||Flow||cms
 
|-
 
|-
−
|5||M06_5m_003_swmm_ts_L||18||hours since 2020-01-01 00:00:00||0.083333||Velocity||Velocity||m/s
+
|5||M06_5m_003_swmm_ts_L||18||hours since 2020-01-01 00:00:00||1.0||Velocity||Velocity||m/s
 
|-
 
|-
 
|}
 
|}
Line 90: Line 90:
 
|-
 
|-
 
|Velocity||FLOAT||Result velocity
 
|Velocity||FLOAT||Result velocity
 +
|-
 +
|}
 +
<Br>
 +
The GIS layer should contain a feature for each applicable element and timestep i.e. the same pipe may be referenced 10 times if there are 10 output timesteps. The order be ascending based on the output time.<Br>
 +
<b>Example <code>M06_5m_003_swmm_ts_L</code> with three output timesteps and three culverts</b><Br>
 +
{| class="wikitable" style="width:70%"
 +
! style="background-color:#005581; font-weight:bold; color:white;" width=5%| fid
 +
! style="background-color:#005581; font-weight:bold; color:white;" width=10%| geometry
 +
! style="background-color:#005581; font-weight:bold; color:white;" width=15%| ID
 +
! style="background-color:#005581; font-weight:bold; color:white;" width=10%| Type
 +
! style="background-color:#005581; font-weight:bold; color:white;" width=10%| Source
 +
! style="background-color:#005581; font-weight:bold; color:white;" width=5%| TimeId
 +
! style="background-color:#005581; font-weight:bold; color:white;" width=10%| Time_relative
 +
! style="background-color:#005581; font-weight:bold; color:white;" width=15%| Datetime
 +
! style="background-color:#005581; font-weight:bold; color:white;" width=10%| Flow
 +
! style="background-color:#005581; font-weight:bold; color:white;" width=10%| Velocity
 +
|-
 +
|1||LINESTRING||FC01.1_R||CONDUITS||SWMM||1||1.0||2020-01-01T01:00:00Z||52.313579||5.3814558
 +
|-
 +
|2||LINESTRING||FC01.2_R||CONDUITS||SWMM||1||1.0||2020-01-01T01:00:00Z||66.050522||4.5863313
 +
|-
 +
|3||LINESTRING||FC04.1_C||CONDUITS||SWMM||1||1.0||2020-01-01T01:00:00Z||0.5314214||2.1729025
 +
|-
 +
|1||LINESTRING||FC01.1_R||CONDUITS||SWMM||2||2.0||2020-01-01T02:00:00Z||19.547256||2.2898435
 +
|-
 +
|2||LINESTRING||FC01.2_R||CONDUITS||SWMM||2||2.0||2020-01-01T02:00:00Z||50.088657||3.4779915
 +
|-
 +
|3||LINESTRING||FC04.1_C||CONDUITS||SWMM||2||2.0||2020-01-01T02:00:00Z||0.6140663||2.2505249
 +
|-
 +
|1||LINESTRING||FC01.1_R||CONDUITS||SWMM||3||3.0||2020-01-01T03:00:00Z||3.1847720||1.4646966
 +
|-
 +
|2||LINESTRING||FC01.2_R||CONDUITS||SWMM||3||3.0||2020-01-01T03:00:00Z||7.6079978||0.5282743
 +
|-
 +
|3||LINESTRING||FC04.1_C||CONDUITS||SWMM||3||3.0||2020-01-01T03:00:00Z||0.1079226||1.4705778
 
|-
 
|-
 
|}
 
|}

Revision as of 20:46, 10 November 2023

The below section describe the TUFLOW GPKG time series format specification. The specification sits ontop of the GPKG v1.2 Specification with two additional required tables. The additional tables and details of the GIS layers are descibed below 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.

TUFLOW Time Series Version

An additional table called TUFLOW_timeseries_version should be present in the GPKG. This table contains the version number of the TUFLOW GPKG time series format and should be set to 1.0.0. The table should have the following columns:

Column Name Type Description
Version TEXT Major.Minor.Patch version number

Time Series Info

An additional table called Timeseries_info should be present in the GPKG. The purpose of this table is to list the available result types and relevant information for each type. The table should have the following columns:

Column Name Type Description
row INTEGER Primary key
Table_name TEXT Reference to the GIS table that the result sits within
Count INTEGER Number of unique elements
Reference_time TEXT Reference time in the form of: [UNITS] since YYYY-MM-DD hh:mm:ss
dt FLOAT Output timestep (units defined in Reference_time)
Column_name TEXT Name of the column in the GIS table containing the result
Series_name TEXT Name of the result type
Series_units TEXT Result type units


Example Timeseries_info

Row Table_name Count Reference_time dt Column_name Series_name Series_units
1 M06_5m_003_swmm_ts_P 22 hours since 2020-01-01 00:00:00 1.0 Depth Depth m
2 M06_5m_003_swmm_ts_P 22 hours since 2020-01-01 00:00:00 1.0 Water Level Water Level m
3 M06_5m_003_swmm_ts_P 22 hours since 2020-01-01 00:00:00 1.0 Storage Volume Storage Volume m3
4 M06_5m_003_swmm_ts_L 18 hours since 2020-01-01 00:00:00 1.0 Flow Flow cms
5 M06_5m_003_swmm_ts_L 18 hours since 2020-01-01 00:00:00 1.0 Velocity Velocity m/s

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_relative FLOAT Output relative time (reference time and units in Timeseries_info)
Datetime DATETIME Output time in datetime
...[column for each result type for that given geometry type as listed in Timeseries_info- examples below]
Flow FLOAT Result flow
Velocity FLOAT Result velocity


The GIS layer should contain a feature for each applicable element and timestep i.e. the same pipe may be referenced 10 times if there are 10 output timesteps. The order be ascending based on the output time.
Example M06_5m_003_swmm_ts_L with three output timesteps and three culverts

fid geometry ID Type Source TimeId Time_relative Datetime Flow Velocity
1 LINESTRING FC01.1_R CONDUITS SWMM 1 1.0 2020-01-01T01:00:00Z 52.313579 5.3814558
2 LINESTRING FC01.2_R CONDUITS SWMM 1 1.0 2020-01-01T01:00:00Z 66.050522 4.5863313
3 LINESTRING FC04.1_C CONDUITS SWMM 1 1.0 2020-01-01T01:00:00Z 0.5314214 2.1729025
1 LINESTRING FC01.1_R CONDUITS SWMM 2 2.0 2020-01-01T02:00:00Z 19.547256 2.2898435
2 LINESTRING FC01.2_R CONDUITS SWMM 2 2.0 2020-01-01T02:00:00Z 50.088657 3.4779915
3 LINESTRING FC04.1_C CONDUITS SWMM 2 2.0 2020-01-01T02:00:00Z 0.6140663 2.2505249
1 LINESTRING FC01.1_R CONDUITS SWMM 3 3.0 2020-01-01T03:00:00Z 3.1847720 1.4646966
2 LINESTRING FC01.2_R CONDUITS SWMM 3 3.0 2020-01-01T03:00:00Z 7.6079978 0.5282743
3 LINESTRING FC04.1_C CONDUITS SWMM 3 3.0 2020-01-01T03:00:00Z 0.1079226 1.4705778
Retrieved from "https://wiki.tuflow.com/w/index.php?title=GPKG_Time_Series_Format_Specification&oldid=34868"