Revision as of 14:54, 2 October 2023 view source Emilie Nielsen (talk \| contribs) Administrators 6,125 edits No edit summary ← Older edit		Revision as of 14:57, 2 October 2023 view source Emilie Nielsen (talk \| contribs) Administrators 6,125 edits →Input File Type – Prefix Naming Conventions Newer edit →
Line 17: As the bulk of the data input to TUFLOW is via GIS layers, efficient management of these datasets is essential. Different TUFLOW input files require different GIS attributes. For example, an initial water level input file only requires a single attribute on the GIS file (which is the initial water level), whereas, a 1D channel has a number of attributes (channel type, inverts etc.). Differentiating between these TUFLOW file types is therefore essential.<br> <br> TUFLOW input files are given different recommended prefixes depending on their purpose. This is demonstrated in the table below (~~Table~~can ~~2.4~~be found ofin the <u>[~~http~~https://~~www~~downloads.tuflow.com/~~Tuflow~~_archive/TUFLOW/Releases/2018-03/TUFLOW%~~20Documentation~~20Manual.~~aspx 2016~~2018-03~~-AE~~.pdf TUFLOW Manual]</u>). The TCF command <font color="blue"><tt>Write Empty GIS Files</tt></font> can be used to automate the creation of the template (empty) files, which use these recommended prefixes. These empty files are created with the precise GIS file formats required for each input TUFLOW file. The <u>[[TUFLOW Empty Files]]</u> page provides a reference list of the template (empty) GIS files, the associated TUFLOW command and a basic description of their function.<br> <br> It is strongly recommended that the prefixes described in the table below be adhered to for all 1D and 2D GIS layers. This greatly enhances the data management efficiency and, importantly, allows for the differentiation of input files , making it easier for another modeller or reviewer to quickly interpret the model.<br> <br>

Naming Convention: Difference between revisions