Revision as of 14:27, 30 October 2023 view source Abigail.lillo (talk \| contribs) Bureaucrats, Administrators 539 edits →Why are the SHP or MIF files created by the 12da_to_from_GIS utility empty? Tag: Visual edit ← Older edit		Revision as of 14:53, 30 October 2023 view source Par (talk \| contribs) Bureaucrats, Administrators 1,003 edits Added some extra information on UTF16 conversion. Tag: Visual edit Newer edit →
Line 47: =Frequently Asked Questions (FAQ)= ==Why are the SHP or MIF files created by the 12da_to_from_GIS utility empty?== The reason for empty output files may be that 12D (v10 or later) produces output files in UTF-16 encoding by default. This encoding is not compatible with the utility and can lead to empty SHP or MIF outputs. The .12da can be exported from 12D into ANSI format, or readily converted in text editor from UTF16 to ANSI making it compatible with TUFLOW and TUFLOW utilities. Instructions for both methods are below. <br> In 12D, when exporting the TIN as a .12da file, make sure to select the "[Ansi format]"<br> [[File:12da_TIN_export_screenshot.JPG\|500px]] <br> Line 53: [[File:12da_TIN_export_screenshot_ANSI_Format_set.JPG\|500px]] <br><br> AnAlternatively, an existing .~~12d~~12da file can ~~also~~ easily be converted to ANSI encoding in Notepad++, under the Encoding menu: <br> [[File:Convert ANSI.jpg\|500px]]

12da to from GIS: Difference between revisions