Difference between revisions of "XsGenerator"
(Created page with "=Introduction= =Examples= {{Tips Navigation |uplink= Back to TUFLOW Utilities }}") |
|||
| Line 1: | Line 1: | ||
| − | + | 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> | ||
| + | The logic for interpreting the .mif layer is:<br> | ||
| + | #The association between an elevation point and a cross-section line is based on having the same XS_ID. It is not based on whether the point is snapped to the line or not. This means the cross-section line is purely schematic and does not have to be located at exactly the same point as the first elevation point. | ||
| + | #The first point in a cross-section line is treated as the start of the cross-section on the left bank. | ||
| + | #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) as 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_mif.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 (eg. your 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 format (see the isis option). The first file specified must a .mif file in the correct projection, with subsequent files being the survey files. Wildcards can be used to input numerous files (eg. *.xyz).<br> | ||
=Examples= | =Examples= | ||
Revision as of 10:42, 10 September 2011
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.
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.
The logic for interpreting the .mif layer is:
- The association between an elevation point and a cross-section line is based on having the same XS_ID. It is not based on whether the point is snapped to the line or not. This means the cross-section line is purely schematic and does not have to be located at exactly the same point as the first elevation point.
- The first point in a cross-section line is treated as the start of the cross-section on the left bank.
- 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) as 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.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 (eg. your 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.
xsGenerator can also be used to generate a cross-section database using survey data in the ISIS format (see the isis option). The first file specified must a .mif file in the correct projection, with subsequent files being the survey files. Wildcards can be used to input numerous files (eg. *.xyz).
Examples
| Up |
|---|
 Back to TUFLOW Utilities
|