12da to from GIS: Difference between revisions
Content deleted Content added
Anne.Kolega (talk | contribs) m →Options (switches): i.e. |
|||
| (2 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 (
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"||
Specifies the output file name when creating a new file.
For example:<br>
<tt>12da_to_from_gis.exe -out output_file.12da <Lines>.mif</tt><br>
Will create the file with the chosen output name instead of the default.
-->
<!--
|-
|"-model"||
When converting to a .12da file, sets the model name in the output.
For example:<br>
<tt>12da_to_from_gis.exe -model 12d_Model_Name <Lines>.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 92 ⟶ 98:
<Header>.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 ===
| |||