Template:CMS-Flow Hard Bottom Dataset
From XMS Wiki
Revision as of 15:53, 3 September 2024 by Jcreer (talk | contribs) (Created page with "__NOINDEX__ __NOTOC__ ===Polygons from Arcs=== <!--====Tool Description====--> The ''CMS-Flow Hard Bottom Dataset'' tool converts all arcs in a coverage to polygons based on specified parameters. This tool is designed to simplify the creation of linear polygons to represent features such as channels or embankments. The feature extraction operations create stream or ridge networks. These features can be used to position cells/elements in a mesh/UGrid to honor these featu...")
Polygons from Arcs
The CMS-Flow Hard Bottom Dataset tool converts all arcs in a coverage to polygons based on specified parameters.
This tool is designed to simplify the creation of linear polygons to represent features such as channels or embankments. The feature extraction operations create stream or ridge networks. These features can be used to position cells/elements in a mesh/UGrid to honor these features. However, it is often useful to represent such linear features as Patch polygons to allow or anisotropic cells—elongated in the direction of the feature.
Each arc in the input polygon will be converted to a polygon. The following applies during the creating process:
- The polygon for isolated lines/arcs will consist of offset lines in both directions from the arc. The ends of the polygon will be perpendicular to the end segment of the arc.
- If two arcs are connected (end to end), the orientation of the two polygons will be averaged so that the polygons share and "end".
- If three arcs/lines join at a node, the two that have the most similar direction will be maintained as a continuous feature. The third will be trimmed back to not encroach on the polygons of the other two. If more than three arcs/lines join at a single location, the two arcs with the most similar direction will define the preserved direction. All other arcs will be trimmed back to not encroach.
- If a single arc closes in a loop, the resulting polygon closes on itself. This polygon will not function as a patch in SMS. This workflow is not recommended.
- The tool performs a check to determine if the polygons from two unconnected overlap/intersect each other. This is reported in the progress dialog.
Input Parameters
- Input coverage – This can be any map coverage in the project. The arcs in the coverage will be used to guide polygon creation.
- Average element/cell width – This defines the average width of the segments projecting perpendicular from the arc. The units (foot/meter) correspond to the display projection of SMS.
- Number of elements/cells (must be even) – This defines the number of segments projecting in each direction from the centerline. Because it is projected in both directions, it must be even.
- Bias (0.01-100.0) – This provides control of the relative length of the segments across the feature. In this case, it is actually a double bias because both sides of the feature are biased from the outer edges to the center. Therefore, a bias less than 1.0 results in segments that are shorter at the center. A bias greater than 1.0 results in segments that are longer at the center. Specify a small bias to improve representation of the channel bottom or embankment crest and a larger bias to increase resolution (representation) or the outer edge (shoulder or toes) of the feature. See images below for examples.
Output Parameters
- Output coverage – Specify the name of the coverage to be created that will contain the generated polygons. The intent of this coverage is to be incorporate into a mesh generation coverage for the domain. The resulting coverage will have the Area Property coverage and will need to be changed to the desired coverage type.
Current Location in Toolbox
CMS-Flow/CMS-Flow Hard Bottom Dataset