Revision as of 08:55, 18 May 2017 view source Teegan.Burke (talk \| contribs) Bureaucrats, Administrators 436 edits No edit summary ← Older edit		Revision as of 11:48, 22 February 2018 view source Stephen.kime (talk \| contribs) 205 edits →Input File Type – Prefix Naming Conventions Newer edit →
Line 21: 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> ~~{\| class="wikitable" width="80%"~~ ~~! style="background-color:#005581; font-weight:bold; color:white;" width=20%\| GIS Data Type~~ ~~! style="background-color:#005581; font-weight:bold; color:white;" width=10%\| Suggest File Prefix~~ ~~! style="background-color:#005581; font-weight:bold; color:white"\| Description~~ \|- \| 2D Boundaries and 2D/1D Links \|\| '''2d_bc_<br> (2d_hx_)<br> (2d_sx_)'''<br> \|\| Mandatory layer(s) defining the locations of 2D boundaries and 2D/1D dynamic links. For large models it may be wise to separate the boundary conditions from the 1D/2D links, in which case the 2d_bc prefix can be substituted with 2d_hx_ and 2d_sx_.<br> ~~Cell code values may also be defined in this layer.<br>~~ \|- \|} '''Note''' that the TUFLOW control files are structured to allow the majority of commands to be repeated and layered. Input file types of the same prefix may need to be used more than once. Hence, additional information such as a descriptor and a file version number is conventionally included in the input file name. An example of a typical file name for an input file is shown below:

Naming Convention: Difference between revisions