Tuflow

12da to from GIS: Difference between revisions

Browse history interactively
← Older edit
Content deleted Content added
VisualWikitext
 
(3 intermediate revisions by one other user not shown)
Line 36:
|"-hip"|| When converting a .12da file to a .mif file will include any 12D hipdata polylines.
|-
|"-xs"|| When converting a .12da file to a .mif file creates a TUFLOW cross-section database (iei.e. one .csv file per 3D polyline) and a 1d_xs layer (1d_tab or 1d_xs format – see Read GIS Table Links and Section 4.6.3). This is used to extract 1D cross-sections from a DTM for use in TUFLOW. Cross-sections generated this way can also be viewed and edited in the SMS TUFLOW Interface.<br>
The process to create the cross-sections from a 12D DTM is as follows:<br>
*Digitise the location of cross-section lines either in a GIS or in 12D. If in a GIS, export the layer out as a .mif file and then run 12da_to_from_gis to convert the .mif file into a .12da file. For example use:<br>
Line 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 71 ⟶ 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 82 ⟶ 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 107 ⟶ 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"