12da to from GIS: Difference between revisions
Content deleted Content added
Line 1:
= Introduction =
The .12da file must be saved in ANSI encoding, not UTF.
When importing or exporting between 12D and GIS, specify the file to be translated:
* If the file has a .mif extension the program converts it to a .12da file.
This process is useful for importing 3D breaklines, for example a road design, directly into TUFLOW.
Several useful options are described in the table below. Particularly noteworthy are the following options:
* -zln: useful when river bathymetry in the DTM is poor because aerial survey data are inaccurate where water or dense vegetation is present.<br>
This option allows a section to be carved through the DTM along the river based on a cross section survey.
▲* If the file has a .mif extension, the program converts it to a .12da file.
▲* Note, when converting from a .12da file to a .mif file without any options, 12da_to_from_mif automatically creates a .mif/.mid file suitable for use by Read GIS Z Line. This is useful for importing 3D breaklines (eg. of a road design) directly into TUFLOW.
▲** Of particular note is the -xs option to generate a TUFLOW 1D cross-section database from a 12D DTM.
▲** This approach is far more preferable to extracting cross-sections manually and is much better than extracting cross-sections from a grid based DTM (eg. Vertical Mapper or Spatial Analyst) as it only extracts points where the DTM triangle sides intersect the cross-section line, thereby keeping the number of points in the cross-section profile to a minimum, and also improving the accuracy of the profile.
=Options (switches)=
'''TABLE 1: 12da_to_from_GIS Options (Switches)'''
| |||