12da to from GIS: Difference between revisions
Content deleted Content added
No edit summary |
|||
Line 1:
=Introduction=
'''12da_to_from_GIS.exe''' converts .12da files from the 12D software [https://www.12d.com (www.12d.com)] to and from .mif and .shp files, the .12da file needs to be in ANSI encoding, not UTF.
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.<br>▼
* If importing/exporting to/from 12D and a GIS simply specify the file that you wish to have translated. If the file has a .12da (or a .4da) extension, the program converts it to a .mif/.mid file format.
There are some very useful options as discussed in the table below.<br>▼
* If the file has a .mif extension, the program converts it to a .12da file.
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.<br>▼
▲* 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.
The zln option can also be very useful when the DTM river bathymetry is poor because the aerial survey is inaccurate where there is water or dense vegetation, and you need to carve a section through the DTM along the river based on a cross-section survey.<br>▼
** Of particular note is the -xs option to generate a TUFLOW 1D cross-section database from a 12D DTM.
▲
▲** The zln option can also be very useful when the DTM river bathymetry is poor because the aerial survey is inaccurate where there is water or dense vegetation, and you need to carve a section through the DTM along the river based on a cross-section survey.
=Options (switches)=
'''TABLE 1: 12da_to_from_GIS Options (Switches)'''
Line 37 ⟶ 40:
=Examples=
<tt>12da_to_from_gis.exe -mif road_breaklines.12da</tt><br>
creates .mif/.mid files of the 2D and 3D breaklines in the file road_breaklines.12da.
<tt>12da_to_from_gis.exe 2d_hx_lines.mif</tt><br>
creates a file 2d_hx_lines.mif.12da.
<tt>12da_to_from_gis.exe 2d_hx_lines_draped.12da</tt
This creates 3D breakline .mif/.mid files of the TUFLOW HX lines that can be used to ensure the 2D HX cells are set to the exact elevations along the HX lines by using the below command in the .tgc file.:<br>
<tt>Read GIS Z Line THICK == mi\2d_hx_lines_draped.12da.mif </tt
=Frequently Asked Questions (FAQ)=
Line 51 ⟶ 56:
[[File:12da_TIN_export_screenshot.JPG|500px]] <br>
This change will be highlighted at the bottom of the Write 12da pop up box. See figure below. <br>
[[File:12da_TIN_export_screenshot_ANSI_Format_set.JPG|500px]]
Alternatively, an existing .12da file can easily be converted to ANSI encoding in Notepad++, under the Encoding menu: <br>
| |||