12da to from GIS - Revision history

Anne.Kolega: /* Options (switches) */ i.e.

2026-04-02T01:47:41Z

Options (switches): i.e.

← Older revision		Revision as of 11:47, 2 April 2026
Line 36:		Line 36:
	\|"-hip"\|\| When converting a .12da file to a .mif file will include any 12D hipdata polylines.		\|"-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 (ie. 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>		\|"-xs"\|\| When converting a .12da file to a .mif file creates a TUFLOW cross-section database (i.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>		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>		*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>

Abrar.Alttahir at 01:37, 21 January 2026

2026-01-21T01:37:03Z

← Older revision		Revision as of 11:37, 21 January 2026
Line 64:		Line 64:
	Will embed the specified 12d model name into the created .12da file.		Will embed the specified 12d model name into the created .12da file.
	-->		-->
			\|}

	= Examples =		= Examples =
	<tt>12da_to_from_gis.exe -mif road_breaklines.12da</tt><br>		<tt>12da_to_from_gis.exe -mif road_breaklines.12da</tt><br>
Line 98:		Line 98:
	<Header>.mif is any .mif file with the correct projection.<br />		<Header>.mif is any .mif file with the correct projection.<br />
	Will search input directory for "Header.mif" or "Projection.mif" if omitted.		Will search input directory for "Header.mif" or "Projection.mif" if omitted.
			\|}

	=== CONVERT FROM 12DA TO SHP ===		=== CONVERT FROM 12DA TO SHP ===

Abrar.Alttahir: /* Options (switches) */

2026-01-21T01:31:47Z

Options (switches)

← Older revision		Revision as of 11:31, 21 January 2026
Line 47:		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>		: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>).		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>		Specifies the output file name when creating a new file.<br>
			For example:<br>
	<tt>12da_to_from_gis.exe -out output_file.12da <Lines>.mif</tt><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.		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>		When converting to a .12da file, sets the model name in the output.<br>
			For example:<br>
	<tt>12da_to_from_gis.exe -model 12d_Model_Name <Lines>.mif</tt><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.		Will embed the specified 12d model name into the created .12da file.
			-->
	\|}

	= Examples =		= Examples =

Abrar.Alttahir: /* Examples */

2026-01-21T01:29:10Z

Examples

Abrar.Alttahir: /* Options (switches) */

2025-09-29T01:27:35Z

Options (switches)

← Older revision		Revision as of 11:27, 29 September 2025
Line 27:		Line 27:
	! width=85% \| Description		! width=85% \| Description
	\|-		\|-
	!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"\| When converting from a ~~.mif~~ file to a .12da file		!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"\| When converting from a GIS 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>		\|"-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!).		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 ~~.mif~~ file		!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"\| When converting from a .12da file to a GIS file
	\|-		\|-
	\|"-hip"\|\| When converting a .12da file to a .mif file will include any 12D hipdata polylines.		\|"-hip"\|\| When converting a .12da file to a .mif file will include any 12D hipdata polylines.

Abrar.Alttahir: /* Introduction */

2025-09-29T01:23:30Z

Introduction

@@ Line 1: / Line 1: @@
-=Introduction=
+= 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 .12da file needs to be in ANSI encoding, not UTF.
+da_to_from_GIS.exe converts .12da files from the 12D software [https://www.12d.com (www.12d.com)] to and from .mif and .shp formats.
 =Options (switches)=
 '''TABLE 1: 12da_to_from_GIS Options (Switches)'''

Abrar.Alttahir: /* Options (switches) */

2025-09-29T01:02:17Z

Options (switches)

@@ Line 36: / Line 36: @@
 :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>).
 |}

Abrar.Alttahir: /* Examples */

2025-09-29T00:46:02Z

Examples

@@ Line 38: / Line 38: @@
 |}
-=Examples=
+= Examples =
 <tt>12da_to_from_gis.exe -mif road_breaklines.12da</tt><br>
 creates .mif/.mid files of the 2D and 3D breaklines in the file road_breaklines.12da. The .mif/.mid files can be directly used by Read GIS Z Line.
@@ Line 49: / Line 49: @@
 This creates 3D breakline .mif/.mid files of the TUFLOW HX lines that can be used to ensure the 2D HX cells are set to the exact elevations along the HX lines by using the below command in the .tgc file.:<br>
 <tt>Read GIS Z Line THICK == mi\2d_hx_lines_draped.12da.mif </tt>
 =Frequently Asked Questions (FAQ)=

Abrar.Alttahir: /* Examples */

2025-09-29T00:17:43Z

Examples

← Older revision		Revision as of 10:17, 29 September 2025
Line 1:		Line 1:
	=Introduction=		=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 .12da file needs to be in ANSI encoding, not UTF. 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.<br>		'''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 .12da file needs to be in ANSI encoding, not UTF.

⚫	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.~~<br>~~
			* 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.
⚫	There are some very useful options as discussed in the table below.~~<br>~~
			* If the file has a .mif extension, the program converts it to a .12da file.
⚫	~~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.~~<br>~~
		⚫	* 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.
⚫	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.~~<br>~~
		⚫	* There are some very useful options as discussed in the table below.
	<br>
			** 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)=		=Options (switches)=
	'''TABLE 1: 12da_to_from_GIS Options (Switches)'''		'''TABLE 1: 12da_to_from_GIS Options (Switches)'''
Line 37:		Line 40:
	=Examples=		=Examples=
	<tt>12da_to_from_gis.exe -mif road_breaklines.12da</tt><br>		<tt>12da_to_from_gis.exe -mif road_breaklines.12da</tt><br>
	creates .mif/.mid files of the 2D and 3D breaklines in the file road_breaklines.12da. The .mif/.mid files can be directly used by Read GIS Z Line.~~<br>~~		creates .mif/.mid files of the 2D and 3D breaklines in the file road_breaklines.12da. The .mif/.mid files can be directly used by Read GIS Z Line.

	<br>
	<tt>12da_to_from_gis.exe 2d_hx_lines.mif</tt><br>		<tt>12da_to_from_gis.exe 2d_hx_lines.mif</tt><br>
	creates a file 2d_hx_lines.mif.12da. Import this file into 12D then drape these lines over the DTM and export the file, say as 2d_hx_lines_draped.12da, then execute the following:~~<br>~~		creates a file 2d_hx_lines.mif.12da. Import this file into 12D then drape these lines over the DTM and export the file, say as 2d_hx_lines_draped.12da, then execute the following:

	<tt>12da_to_from_gis.exe 2d_hx_lines_draped.12da</tt~~><br~~>		<tt>12da_to_from_gis.exe 2d_hx_lines_draped.12da</tt>

	This creates 3D breakline .mif/.mid files of the TUFLOW HX lines that can be used to ensure the 2D HX cells are set to the exact elevations along the HX lines by using the below command in the .tgc file.:<br>		This creates 3D breakline .mif/.mid files of the TUFLOW HX lines that can be used to ensure the 2D HX cells are set to the exact elevations along the HX lines by using the below command in the .tgc file.:<br>
	<tt>Read GIS Z Line THICK == mi\2d_hx_lines_draped.12da.mif </tt~~><br~~>		<tt>Read GIS Z Line THICK == mi\2d_hx_lines_draped.12da.mif </tt>

	=Frequently Asked Questions (FAQ)=		=Frequently Asked Questions (FAQ)=
Line 51:		Line 56:
	[[File:12da_TIN_export_screenshot.JPG\|500px]] <br>		[[File:12da_TIN_export_screenshot.JPG\|500px]] <br>
	This change will be highlighted at the bottom of the Write 12da pop up box. See figure below. <br>		This change will be highlighted at the bottom of the Write 12da pop up box. See figure below. <br>
	[[File:12da_TIN_export_screenshot_ANSI_Format_set.JPG\|500px]] ~~<br>~~<br>		[[File:12da_TIN_export_screenshot_ANSI_Format_set.JPG\|500px]] <br>

	Alternatively, an existing .12da file can easily be converted to ANSI encoding in Notepad++, under the Encoding menu: <br>		Alternatively, an existing .12da file can easily be converted to ANSI encoding in Notepad++, under the Encoding menu: <br>

Emilie Nielsen at 00:38, 18 July 2024

2024-07-18T00:38:01Z

← Older revision		Revision as of 10:38, 18 July 2024
Line 1:		Line 1:
	=Introduction=		=Introduction=
	'''12da_to_from_GIS.exe''' converts .12da files from the 12D software [~~http~~://www.12d.com (www.12d.com)] to and from .mif and .shp files, the .12da file needs to be in ANSI encoding, not UTF. 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.<br>		'''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 .12da file needs to be in ANSI encoding, not UTF. 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.<br>
	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.<br>		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.<br>
	There are some very useful options as discussed in the table below.<br>		There are some very useful options as discussed in the table below.<br>

← Older revision		Revision as of 11:29, 21 January 2026
Line 71:		Line 71:
	<tt>Read GIS Z Line THICK == mi\2d_hx_lines_draped.12da.mif </tt>		<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>		<span style="color:red">'''UNDER CONSTRUCTION'''</span>

	=== CONVERT FROM GIS TO 12DA ===		=== CONVERT FROM GIS TO 12DA ===

	<tt>1: 12da_to_from_gis.exe <Lines>.mif</tt><br />		<tt>1: 12da_to_from_gis.exe <Lines>.mif</tt><br />
	Converts to 2D breakline.		Converts to 2D breakline.

Line 82:		Line 83:
	interpolation of Z values at intermediate vertices.		interpolation of Z values at intermediate vertices.

	<tt>2: 12da_to_from_gis.exe -zln <Points>.shp <Lines>.shp</tt><br />		<tt>2: 12da_to_from_gis.exe -zln <Points>.shp <Lines>.shp</tt><br />
	<tt>3: 12da_to_from_gis.exe -zln <Points>.mif <Lines>.mif</tt><br />		<tt>3: 12da_to_from_gis.exe -zln <Points>.mif <Lines>.mif</tt><br />
	<tt>4: 12da_to_from_gis.exe -zln <Lines_and_Points>.mif</tt>		<tt>4: 12da_to_from_gis.exe -zln <Lines_and_Points>.mif</tt>

	=== CONVERT FROM 12DA TO MIF ===		=== CONVERT FROM 12DA TO MIF ===

	<tt>5: 12da_to_from_gis.exe -mif <12da_file>.12da <Header>.mif</tt><br />		<tt>5: 12da_to_from_gis.exe -mif <12da_file>.12da <Header>.mif</tt><br />
	<Header>.mif is any .mif file with the correct projection.<br />		<Header>.mif is any .mif file with the correct projection.<br />
	Will search input directory for "Header.mif" or "Projection.mif" if omitted.		Will search input directory for "Header.mif" or "Projection.mif" if omitted.
Line 94:		Line 95:
	=== CONVERT FROM 12DA TO SHP ===		=== CONVERT FROM 12DA TO SHP ===

	<tt>6: 12da_to_from_gis.exe -shp <12da_file>.12da <Header>.prj</tt><br />		<tt>6: 12da_to_from_gis.exe -shp <12da_file>.12da <Header>.prj</tt><br />
	<Header>.prj is any .prj file with the correct projection.<br />		<Header>.prj is any .prj file with the correct projection.<br />
	Will search input directory for "Header.prj" or "Projection.prj" if omitted.<br />		Will search input directory for "Header.prj" or "Projection.prj" if omitted.<br />
Line 107:		Line 108:
	For conversions to .12da the "<tt>-model <model_name></tt>" option can be used to set the model name.		For conversions to .12da the "<tt>-model <model_name></tt>" option can be used to set the model name.

	<tt>7: 12da_to_from_gis.exe -out output_file.12da <Lines>.mif</tt><br />		<tt>7: 12da_to_from_gis.exe -out output_file.12da <Lines>.mif</tt><br />
	<tt>8: 12da_to_from_gis.exe -model 12d_Model_Name <Lines>.mif</tt>		<tt>8: 12da_to_from_gis.exe -model 12d_Model_Name <Lines>.mif</tt>
			-->

	=Frequently Asked Questions (FAQ)=		=Frequently Asked Questions (FAQ)=