Difference between revisions of "TUFLOW Message 2416"
Jump to navigation
Jump to search
(Created page with "{{TUFLOW_Message |tuflow_message=ERROR 2416 - .12da file does not contain any TIN data. |alt_msg=NA |type=ERROR |message_desc=The .12da file being accessed by a Read TIN comm...") |
|||
(6 intermediate revisions by 3 users not shown) | |||
Line 4: | Line 4: | ||
|type=[[ERROR]] | |type=[[ERROR]] | ||
|message_desc=The .12da file being accessed by a Read TIN command does not contain any TIN data. | |message_desc=The .12da file being accessed by a Read TIN command does not contain any TIN data. | ||
− | |suggestions=Check that the .12da file has been exported from a 12D TIN layer. | + | |suggestions=Check that the .12da file has been exported from a 12D TIN layer.<br> |
− | + | In 12D, when you export the TIN as a .12da file, make sure to select the "[Ansi format]" <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> | |
− | + | [[File:12da_TIN_export_screenshot_ANSI_Format_set.JPG|500px]] <br> | |
+ | Name the 12da TIN file, write from 12D as normal and read into TUFLOW.<br> | ||
+ | The cause appears to be due to the default output from v10 12D being written out in UTF-16 code. | ||
+ | |||
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | |uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | ||
− | |||
}} | }} |
Latest revision as of 14:54, 18 July 2024
TUFLOW Message
ERROR 2416 - .12da file does not contain any TIN data.
Alternate Message
NA
Message Type
ERROR
Description
The .12da file being accessed by a Read TIN command does not contain any TIN data.
Suggestions
Check that the .12da file has been exported from a 12D TIN layer.
In 12D, when you export the TIN as a .12da file, make sure to select the "[Ansi format]"
This change will be highlighted at the bottom of the Write 12da pop up box. See figure below.
Name the 12da TIN file, write from 12D as normal and read into TUFLOW.
The cause appears to be due to the default output from v10 12D being written out in UTF-16 code.
Up |
---|
2xxx Messages |