12da to from GIS: Difference between revisions
Content deleted Content added
No edit summary |
|||
| (3 intermediate revisions by the same user not shown) | |||
Line 27:
! width=85% | Description
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| When converting from a
|-
|"-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
|-
|"-hip"|| When converting a .12da file to a .mif file will include any 12D hipdata polylines.
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 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:
Converts to 2D breakline.
Line 82 ⟶ 89:
interpolation of Z values at intermediate vertices.
<tt>2:
<tt>3:
<tt>4:
=== CONVERT FROM 12DA TO MIF ===
<tt>5:
<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 ===
<tt>6:
<Header>.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:
For conversions to .12da the "<tt>-model <model_name></tt>" option can be used to set the model name.
<tt>7:
<tt>8:
-->
=Frequently Asked Questions (FAQ)=
| |||