TUFLOW Message 2073

From Tuflow
Revision as of 10:06, 23 September 2024 by Emilie Nielsen (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

TUFLOW Message
WARNING 2073 - GIS object below ignored. Only Points, Lines, Polylines & Region Centers used.

Alternate Message
WARNING 2073 - Object below ignored. Only Lines, Polylines & Multiple Polylines used.
WARNING 2073 - Object below ignored. Only Points, Lines, Polylines & Regions used.
ERROR 2073 - Object ignored. Only Polygons used, object Type <type>
WARNING 2073 - Object ignored. Only Polygons used, object Type <type>
ERROR 2073 - Object ignored. Only Points used, object Type <type>
WARNING 2073 - Object ignored. Only Points used, object Type <type>
ERROR 2073 - Object ignored. Only Lines used, object Type <type>
WARNING 2073 - Object ignored. Only Lines used, object Type <type>
WARNING 2073 - 2D IWL must be a polygon... ignoring point. This layer could be a 1d_IWL - use ESTRY Control File or 1D commands in TCF for 1d_IWL.
WARNING 2073 - Null Shape object ignored. Only Regions, Lines, Polylines & Multiple Polylines used.

Message Type
ERROR
WARNING

Description
The GIS object has been ignored. There are two reasons that this can occur:

  • The GIS objects is unsupported:
    Various GIS packages handle the advanced GIS geometries (such as arcs) differently, for example if converting a MapInfo Arc object using QGIS, the arc object is converted to a polyline with vertices along the length. For consistency between packages and to provide better support across GIS platforms not all GIS geometries are supported by TUFLOW. For lines, arc objects are not supported (but line and polyline objects are both recognised). For region objects rectangles, rounded rectangles and ellipses are not supported.
    Two special cases of unsupported geometries are “Text” objects, which can be used to annotate GIS layers, and “None” or “Null” objects, which GIS software may add to the layer to indicate deleted objects (particularly if using the shapefile format).
    For the 2016 release of TUFLOW this can be set to either a Warning or Error using the command:
    GIS Unsupported Object == ERROR
    or
    GIS Unsupported Object == WARNING
    This command, introduced for the 2016-03 release, controls TUFLOW’s response for geometries that are not supported by TUFLOW. The ERROR option stops the simulation with a Message 0323, while WARNING issues Message 0323 and continues the simulation. There is an optional severity level component that can be specified as a second argument (separated by a vertical bar) with the options for <level> being: The severity levels are:
    • Level 0 – No checks on unsupported geometries (i.e. previous behaviour)
    • Level 1 – Check for ellipses, rectangles, rounded rectangles and arcs (curved arcs)
    • Level 2 – All the level 1 checks as above plus checks for null and text objects.
    An example is:
    GIS Unsupported Object == ERROR | 2
    

    The default for unsupported objects is ERROR with severity level 1, that is arcs, ellipses, rectangle and rounded rectangles will cause the simulation to stop, but any None and Text objects will be ignored.

  • The GIS object is supported, but the type is not expected at this stage in the processing:
    The second reason for an object being ignored is that at this stage in the processing, only a specific type of GIS data is expected. For example, when the command Read GIS RF Point == <gis file> is specified, only point objects are being read by TUFLOW and lines and regions will be ignored.
    For the 2016 release of TUFLOW this can be set to either a Warning or Error using the command:
    GIS Supported Object Ignored == ERROR
    or GIS Supported Object Ignored == WARNING
    The default approach is for a Warning to be output.

Suggestions
Ensure that the data in the specified is correct.
See also the following commands in the TUFLOW Manual for more details on the options for handling unsupported or ignored GIS data.
GIS Supported Object Ignored ==
GIS Unsupported Object ==
In some cases it helps to the select all features in a map window (not from attribute table) and export only the selected features under a new name.


Up
Go-up.png 2xxx Messages