Revision as of 12:36, 17 January 2025 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
Line 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 Flood Modeller format (see the Flood 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'''

XsGenerator: Difference between revisions