Revision as of 00:09, 7 July 2023 view source ElizaCollison (talk \| contribs) Bureaucrats, Administrators 3,910 edits →QGIS Browser Panel ← Older edit		Revision as of 00:17, 7 July 2023 view source ElizaCollison (talk \| contribs) Bureaucrats, Administrators 3,910 edits →Command Files Newer edit →
Line 10: For more information see the <u>[https://downloads.tuflow.com/TUFLOW/Releases/2023-03/TUFLOW%20Release%20Notes.pdf 2023 Release Notes]</u>. <br><br> = Database Organisation = ~~= Command Files =~~ There are many ways to organise model inputs when using GeoPackages. This allows modellers to decide how they structure their inputs files, for example some options include: ~~There are many ways to use GeoPackages, for example, one database for an entire project or one database for a developed case. To define the database the following command is used:~~ :a single database for an entire project, :separate database for an existing or developed case, or :*separate databases for each type of input (e.g. elevation, materials, culverts). <br> To define the database for TUFLOW to refer to the following command is used:<br> <font color="blue"><tt>Spatial Database</tt></font> <font color="red"><tt>== </tt></font> <font color="black"><tt>/path/to/database </tt></font> <br><br> ~~If a database is~~ This command can be repeated multiple times throughout control files, TUFLOW will change which database it looks to based on the last time the above command has been referenced. <br> ~~Since a GeoPackage database can have more than one layer, when reading data into TUFLOW a GeoPackage database~~ Some examples include: ~~and layermay need to be specified. The following options are possible:~~ ~~One difference between previous formats and the GeoPackage format is that the spatial database must be referenced in the control files.~~ == Referencing a GeoPackage Database ==

GeoPackage Tips: Difference between revisions