XsGenerator: Difference between revisions

Browse history interactively

← Older edit

Content deleted Content added

VisualWikitext

Revision as of 13:27, 20 September 2018 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,365 edits No edit summary ← Older edit		Latest revision as of 13:21, 29 September 2025 view source Abrar.Alttahir (talk \| contribs) Bureaucrats, Administrators 345 edits No edit summary
(7 intermediate revisions by one other user not shown)
Line 1: = Introduction = xsGenerator.exe creates TUFLOW 1D cross-section databases (ie. a 1d_xs layer and a .csv file for each cross-section) using .mif layers of survey (elevation) points and, optionally, lines.<br> Any number of .mif layers can be specified. The elevation points can be in the same layer, several layers or a different layer to the cross-section lines. The cross-section lines are optional (as discussed below). Each .mif layer must have four attributes as described in the first table below, and in the same order as in the table. For line/polyline objects of the cross-section locations, only the XS_ID attribute is used. The second table below describes the options (switches) available.<br> Line 6 ⟶ 7: #Elevation points having the same XS_ID are sorted based on the shortest distance between them. This means the points do not have to be in order across the cross-section (as often seems to be the case!). The cross-section line is not used for setting the distance (X) values for the profile. #If there is no cross-section line for a set of elevation points, this is accepted provided that at least one point (the start on the left bank) has a LCR values of “L” to denote the start of the cross-section. There must also be at least two “C” points in succession. Except for the first “L” point, subsequent isolated “L” and “R” points are ignored. This means it is possible to generate a cross-section database from a layer of surveyed points only, provided each point is assigned their respective XS_ID. If a TUFLOW cross-section database has been created using [[~~12da_to_from_mif~~12da_to_from_GIS \| ~~12da_to_from_mif~~12da_to_from_GIS.exe]], it will have created a .mif layer ready to be used for xsGenerator.exe. This layer can be used to assign material values in a GIS to the MNR attribute from a material polygon layer (e.g. 2d_mat layer), then processed by xsGenerator to recreate the TUFLOW cross-section database with material values allocated across the cross-section profiles in the .csv files.<br> xsGenerator can also be used to generate a cross-section database using survey data in the ~~ISIS~~Flood Modeller format (see the Flood ~~isis~~Modeller option). The first file specified must be a .mif file in the correct projection, with subsequent files being the survey files. Wildcards can be used to input numerous files (e.g. *.xyz).<br><br> '''TABLE 1: xsGenerator .mif Layer Attributes''' {\| align="center" class="wikitable" Line 18 ⟶ 19: Mandatory for point objects. Not used for lines. \|- \|MNR\|\| Float \|\| The Material, Manning’s n or Relative resistance value at that point along the cross-section. Use the –M-M, -N or –R-R switch in the table below to indicate which type of value it is.<br> Mandatory for point objects. Not used for lines. \|- Line 41 ⟶ 42: \|"-R"\|\|The MNR attribute in the .mif file is a relative resistance number. \|- \|"-ppol"\|\|Project Points Onto Line. This option projects points onto their line . Only lines with two vertices can be used. This is very useful if the cross-section points are not surveyed perpendicular to flow, this ensures that the flow area is not exaggerated. \|} <br> '''TABLE 3: xsGenerator Options (Switches) for .~~ISIS~~Flood Modeller Cross-Section Input Files or Mike11 input files''' {\| align="center" class="wikitable" Line 50 ⟶ 51: ! width=85% \| Description \|- \|"-isis"\|\|Indicates the input files are in the ~~ISIS~~Flood Modeller cross-section format. \|- \|"-m11"\|\|Indicates the input files are in the Mike11 XZ cross-section format. For Mike11 cross-section conversion the utility also requires the network (.nwk11) and parameter (.hd11) files. For Mike11 the subsequent input data files are .txt, .nwk11 and .hd11 in any order. Line 62 ⟶ 63: \|} =Examples= <li><tt>xsGenerator.exe -M -isis projection.mif datafile.asc</tt><br> ~~Coming soon.~~ <li><tt>xsGenerator.exe -M -m11 projection.mif xs.txt model.nwk11 model.hd11</tt><br> <br> {{Tips Navigation \|uplink=[[TUFLOW_Utilities \| Back to TUFLOW Utilities]]