Tuflow

12da to from GIS: Difference between revisions

Browse history interactively
← Older edit
Content deleted Content added
VisualWikitext
No edit summary
 
(4 intermediate revisions by the same user not shown)
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 formats.12da file needs to be in ANSI encoding, not UTF.
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 .mif12da or .4da extension, the program converts it to a .12damif/.mid file. ▼
* If the file has a .mif extension the program converts it to a .12da file.
 
* Note, whenWhen converting from a .12da file to a .mif file without any options, 12da_to_from_mif12da_to_from_gis.exe 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. ▼
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:
** Of particular note is the -xs: option to generategenerates a TUFLOW 1D cross-section database from a 12D DTM. <br>▼
** This approachmethod is far more preferable to extractingmanual cross-sections manuallysection extraction and ismore much betteraccurate than extracting cross-sections from a grid based DTM, (eg.for example Vertical Mapper or Spatial Analyst), asbecause it only extractssamples points where the DTM triangle sides intersect the cross-section line,. therebyThis keepinglimits the number of points in theeach cross- section profile to a minimum, and also improving theimproves accuracy of the profile. ▼
 
* -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 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.
▲* 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.
* There are some very useful options as discussed in the table below.
▲** 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.
** 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 16 ⟶ 27:
! width=85% | Description
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| When converting from a .mifGIS file to a .12da file
|-
|"-zln"|| When converting a .mif file to .12da file, if zln is specified polylines are interpreted in the same manner as a TUFLOW 3D breakline (see Read GIS Z Line) such that any points snapped to the polyline are used to set the elevations of any vertices along the polyline that do not have points snapped to them. The first attribute in the .mif file must be the Elevation. (Note, when converting in reverse 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.)<br>
This is useful for creating 3D polylines for 12D where an elevation does not exist at a vertice. It is particularly useful where a river’s bathymetry in a DTM is being created from cross-section surveys, and the DTM operator wishes to use the elevations at the cross-section survey points, but needs to put more shape into the breaklines being digitised between the cross-sections so as to carve out the river’s bathymetry into the DTM. Using 12da_to_from_mid with the zln option will interpolate elevations at every string vertice, something that 12D does not offer (as far as we know!).
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| When converting from a .12da file to a .mifGIS file
|-
|"-hip"|| When converting a .12da file to a .mif file will include any 12D hipdata polylines.
Line 36 ⟶ 47:
:This will produce a 1d_xs layer in shapefile format ready for use by TUFLOW and a .csv file for each cross-section line. Keep the 1d_xs layer and the .csv files in the same folder in the event that you move them elsewhere.<br>
Using the xsGenerator.exe utility, you can also assign material values to each of the cross-section points (see <u>[[xsGenerator | this page]]</u>).
<!-- DRAFT / HIDDEN CONTENT BELOW
|-
|"-out"||
|"-out"|| <span style="color:red">'''UNDER CONSTRUCTION'''</span><br>
Specifies the output file name when creating a new file. <br>For example:<br>
For example:<br>
<tt>12da_to_from_gis.exe -out output_file.12da &lt;Lines&gt;.mif</tt><br>
Will create the file with the chosen output name instead of the default.
-->
 
<!--
|-
|"-model"||
|"-model"|| <span style="color:red">'''UNDER CONSTRUCTION'''</span><br>
When converting to a .12da file, sets the model name in the output. <br>For example:<br>
For example:<br>
<tt>12da_to_from_gis.exe -model 12d_Model_Name &lt;Lines&gt;.mif</tt><br>
Will embed the specified 12d model name into the created .12da file.
-->
|}
 
= Examples =
<tt>12da_to_from_gis.exe -mif road_breaklines.12da</tt><br>
Line 60 ⟶ 77:
<tt>Read GIS Z Line THICK == mi\2d_hx_lines_draped.12da.mif </tt>
 
<!-- DRAFT / HIDDEN CONTENT BELOW
<span style="color:red">'''UNDER CONSTRUCTION'''</span>
 
=== CONVERT FROM GIS TO 12DA ===
 
<tt>1: 12da_to_from_gis.exe &lt;Lines&gt;.mif</tt><br />
Converts to 2D breakline.
 
Line 71 ⟶ 89:
&nbsp;&nbsp;&nbsp;interpolation of Z values at intermediate vertices.
 
<tt>2: 12da_to_from_gis.exe -zln &lt;Points&gt;.shp &lt;Lines&gt;.shp</tt><br />
<tt>3: 12da_to_from_gis.exe -zln &lt;Points&gt;.mif &lt;Lines&gt;.mif</tt><br />
<tt>4: 12da_to_from_gis.exe -zln &lt;Lines_and_Points&gt;.mif</tt>
 
=== CONVERT FROM 12DA TO MIF ===
 
<tt>5: 12da_to_from_gis.exe -mif &lt;12da_file&gt;.12da &lt;Header&gt;.mif</tt><br />
&lt;Header&gt;.mif is any .mif file with the correct projection.<br />
Will search input directory for "Header.mif" or "Projection.mif" if omitted.
|}
 
=== CONVERT FROM 12DA TO SHP ===
 
<tt>6: 12da_to_from_gis.exe -shp &lt;12da_file&gt;.12da &lt;Header&gt;.prj</tt><br />
&lt;Header&gt;.prj is any .prj file with the correct projection.<br />
Will search input directory for "Header.prj" or "Projection.prj" if omitted.<br />
Line 96 ⟶ 115:
&nbsp;&nbsp;&nbsp;For conversions to .12da the "<tt>-model &lt;model_name&gt;</tt>" option can be used to set the model name.
 
<tt>7: 12da_to_from_gis.exe -out output_file.12da &lt;Lines&gt;.mif</tt><br />
<tt>8: 12da_to_from_gis.exe -model 12d_Model_Name &lt;Lines&gt;.mif</tt>
-->
 
=Frequently Asked Questions (FAQ)=
Retrieved from "https://wiki.tuflow.com/12da_to_from_GIS"