SMS:TUFLOW 2D Geometry Components: Difference between revisions

From XMS Wiki
Jump to navigationJump to search
Line 16: Line 16:


==Considerations for modifying Z data==
==Considerations for modifying Z data==
As mentioned previously, the order links are listed matters for coverages and scatter data. This can be particularly useful for Z data but the user should make certain the attributes are applied in the correct order.  
As mentioned previously, the order links are listed matters for coverages and scatter data. This can be particularly useful for Z data but make certain the attributes are applied in the correct order.  


Suppose there is a situation where the user wants to incorporate a 2.0 m high fenceline and also raise a portion of the domain to model a proposed fill for a development. The fenceline is defined a z-line and the raised domain is a TIN (a user could use a 2D Z Lines/Polygons (simple) coverage if it is a simple fill scenario). If the fenceline is above the TIN in the project explorer, anywhere that they overlap the TIN would take precedence and the fenceline would get wiped out. If the fenceline is below the TIN, the TIN elevations will get applied and then the fenceline will raise the elevations 2.0 m above the new elevations. Depending upon the scenario to be represented, either option may be the preferred mechanism.
Suppose there is a situation where needing to incorporate a 2.0 m high fenceline and also raise a portion of the domain to model a proposed fill for a development. The fenceline is defined a z-line and the raised domain is a TIN (use a 2D Z Lines/Polygons (simple) coverage if it is a simple fill scenario). If the fenceline is above the TIN in the project explorer, anywhere that they overlap the TIN would take precedence and the fenceline would get wiped out. If the fenceline is below the TIN, the TIN elevations will get applied and then the fenceline will raise the elevations 2.0 m above the new elevations. Depending upon the scenario to be represented, either option may be the preferred mechanism.


==External files==
==External files==

Revision as of 19:46, 28 December 2015

A 2D geometry component groups grids and data that apply to the grid. The other kinds of data in a geometry component include coverages and TIN (scatterset). A TIN is used to modify the Z values. The purpose of each coverage is dependent upon the coverage type. Some coverages will modify z values and others will control other attributes. There can be multiple objects of the same type in a geometry component. When this happens, the data is applied in the order of the objects in the component. This means that the objects below in the project explorer are the ones that will control. This applies to Z as well as other attributes. Links can be rearranged by dragging them up or down within the 2D Geometry domain.

Coverages in a geometry component

TUFLOW 2D Geometry components associate grids with TUFLOW coverages that apply specifically to the domain. For example a grid component may contain an area property coverage that modifies the materials in the grid. Grids and coverages are represented as TUFLOW Project Explorer Links inside of a 2D Geometry component. Only one grid or grid frame coverage may be linked in each geometry component.

The following coverages can be put inside of a 2D Geometry domain

TINs (scatterset) in a geometry component

  • In addition, Scatter Data can also be put inside a 2D Geometry domain to modify Z values. Unlike the other components, it has additional TUFLOW options that can be set in its link's right-click menu. The TUFLOW Options that can be set for how the scatter data modifies Z values are All, Add, Min and Max.
  • Clip Regions for Read Tin z pts

Considerations for modifying Z data

As mentioned previously, the order links are listed matters for coverages and scatter data. This can be particularly useful for Z data but make certain the attributes are applied in the correct order.

Suppose there is a situation where needing to incorporate a 2.0 m high fenceline and also raise a portion of the domain to model a proposed fill for a development. The fenceline is defined a z-line and the raised domain is a TIN (use a 2D Z Lines/Polygons (simple) coverage if it is a simple fill scenario). If the fenceline is above the TIN in the project explorer, anywhere that they overlap the TIN would take precedence and the fenceline would get wiped out. If the fenceline is below the TIN, the TIN elevations will get applied and then the fenceline will raise the elevations 2.0 m above the new elevations. Depending upon the scenario to be represented, either option may be the preferred mechanism.

External files

An external file can be read in as part of a geometry component. As previously mentioned, the order of links is important, and the external file behaves the same way as the z-modifying data. An external file is added by right-clicking on the geometry component and selecting Add External File....

After a file has been selected, a tree item with the file name will appear at the bottom of the geometry component tree item group. This external file item can be moved around to the desired location and the file name can be changed by right-clicking and selecting Browse....

Related Topics