GeoPackage Tips: Difference between revisions

There are many ways to organise model inputs when using GeoPackagesGPKG. This allows modellers to decide how they structure their inputs files, for example some options include:

*aA single database for an entire project,

*separateSeparate database for an existing or developed case, or

*separateSeparate databases for each type of input (e.g. elevation, materials, culverts).

To reference a GeoPackageGPKG Database:

<li>To specify a GeoPackageGPKG Database for the entire model, add the following command to the beginning of the .tcf. This database will then be the default for all inputs in all control files. There is no need to reference the database again in the other control files. <br>

<li>To specify a different GeoPackageGPKG Database for subsequent inputs, use the following command. A new database can be specified multiple times throughout control files, TUFLOW will change which database it looks to based on the last time the above command has been referenced. This command can be used in the .tcf, .ecf, .tbc, .tgc, .qcf, .tef. For example:<br>

<font color="blue"><tt>Spatial Database </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>gis\2d_zsh.gpkg </tt> <font color="green"><tt> ! Sets GeoPackageGPKG Database</tt></font> <br>

<font color="blue"><tt>Spatial Database </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>gis\2d_mat.gpkg </tt></font> <font color="green"><tt> ! Sets GeoPackageGPKG Database</tt></font> <br>

There are many ways to reference a GeoPackageGPKG Layer. The following commands can be used in the .tcf, .ecf, .tbc, .tgc, .qcf and .tef. <br>

<li>To specify a table in a .gpkgGPKG, use ">>":<br>

<li>To specify a .gpkgGPKG file path only. It will assume the table name is the same as the .gpkgGPKG database name. The following are equivalent:<br>

<li>To specify all the tables in a .gpkgGPKG, use the command "USE ALL" with ">>":<br>

If the GeoPackageGPKG Database is specified to use for subsequent inputs, the commands will become:<br>

<font color="blue"><tt>Spatial Database </tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>gis\2d_zsh.gpkg </tt> <font color="green"><tt> ! Sets GeoPackageGPKG Database</tt></font> <br>

Note: If the .gpkgGPKG for the model is referenced in the .tcf (using the 'Spatial Database' command), it does not need to be referenced again in the other control files. However, if the model inputs are not contained in a single .gpkgGPKG, the separate databases must be referenced accordingly.

Result and check file vector outputs can be written into separate databases or grouped, with 'grouped' being the default. Grouped databases will group by output folder location, for example, the check file folder will contain one GeoPackageGPKG Database that contains all check file layers within it. Separate databases will group geometries together, for example, PLOT_P, PLOT_L, PLOT_R will be written to one database. The following command can be used to set the output to either separate or grouped: <br>

This is a huge benefit in terms of file organisation. The below shows a TUFLOW 'Check' folder from a model using the GeoPackageGPKG (grouped). The same 'Check' folder for a model using Shapefile would have 44(!) items in it. <br><br>