Previous Topic

Next Topic

Book Contents

Book Index

Management Requirement Shape Considerations

Data Managers need to be aware of these considerations while working with Management Requirement shapes:

Management Requirement Shape data requirements

There are no formal data standards for Management Requirement (MR) shapes. Each shapefile uploaded represents the spatial area for a single management requirement. MR shapes must be polygons. If you wish to represent a management requirement as a line or point, you'll need to buffer them into a polygon before attempting to use them as an MR shape.

If the incoming shapefile has multiple records, WFDSS dissolves them into a single polygon. Attributes in the shapefile are ignored; the management requirement Label and Description are entered into the WFDSS Data Management/Unit Shapes tab when the management requirement shapefile is uploaded. If you wish to load multiple management requirements, you must load them one shapefile at a time.

There is a 150,000 vertex limit for management requirement shapes. It is important to consider that shapes that extend beyond the unit boundary (all FMU/SO shapes for the unit dissolved), the shape will be clipped to the unit boundary. This can result in a fairly simple MR shape gaining significant complexity, if the unit boundary is complex in the area where the clip occurred. Pay attention to the error messages you get if an MR shape fails to load, it will often mention that a clip occurred, and violation of the vertex limit.

Here are some tips for dealing with MR shapes that become unwieldy due to the boundary clipping issue.

The current vertex limit for Management Requirements is 150K. You can count the vertices in your upload shape in ArcGIS by adding a Double field called "VertCnt" and calculating its value with the FieldCalculator Python expression: !shape!.pointcount Make sure the Python Parser radio button is selected.

You can 'thin" a shape's vertices with the Simplify Polygon tool to get it under the limit.

WFDSS clips the Management Requirement shape with the Unit boundary (all the FMU/SO shapes for that unit merged). This step ensures that you do not have management requirements that apply outside your unit, and is therefore necessary. If you have a complex boundary, that can add many vertices, so a shape under the limit does not guarantee success. (For example, a shape with 129K vertices could bounce back with bounce with a message telling you that there were 150K vertices.)

If you hit the limit try one or more of the following:

In This Section

About Shapes

Management Requirement Shapes and Vertex Limits

See Also

Incident and Analysis Level Shapes

Shape Privileges by User Role

Considerations for Uploading Unit Shapes

Complex Shapes

Management Requirement Shapes

Strategic Objective Shapes


Field Descriptions

Glossary Resources

Spatial Data Reference

Landscape Data Source Reference

Relative Risk Reference

Organization Assessment Reference

Fire Behavior Reference

About the WFDSS Decision Editors