12da to from GIS: Difference between revisions

Browse history interactively

← Older edit

Content deleted Content added

VisualWikitext

Revision as of 11:31, 21 January 2026 view source Abrar.Alttahir (talk \| contribs) Bureaucrats, Administrators 395 edits →Options (switches) ← Older edit		Latest revision as of 11:47, 2 April 2026 view source Anne.Kolega (talk \| contribs) Bureaucrats, Administrators 184 edits m →Options (switches): i.e. Tag: Visual edit
(One intermediate revision 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 64: 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 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 ===