|
|
|
|
FMU/SO Shape Submission Checklist
Use this checklist to examine whether the FMU data you plan to submit is compliant with the FMU data standard. All data standard pagesin this topic are based on standards documented at, https://wfmrda.nwcg.gov/sites/default/files/docs/Data/Geospatial_DataStandard.pdf including the page numbers in the second column of this table.
At the end of this topic is information for using this checklist.
Standard
|
Data Std Pg
|
Pass/Fail
|
Comments
|
Zipfile Named Correctly? |
4 |
|
|
Zipfile contains all needed components of the shapefile? |
|
|
|
Shapefile named correctly? |
4 |
|
|
Fieldnames named correctly? |
3 |
|
|
Field properties match standard? |
3 |
|
|
''CODE'' attribute field information matches the standard? |
3 |
|
|
''UNIT_ID'' attribute field information matches the standard? |
3 |
|
|
''DESC_" attribute field information matches the standard? |
3 |
|
|
''AGENCY" attribute field information matches the standard? |
3 |
|
|
Polygons Pass Geometry Check |
n/a |
|
Good Practice Run ArcGIS/ArcPro Check/Repair Geometry |
Vertices Count |
n/a |
|
Good Practice number of vertici > 1 million, consider Generalize tool. Add VxCount Field, run calculate field where VxCount=!Shape!.pointcount |
Polygons sharing the same "CODE" attribute are singlepart? |
2 |
|
|
Polygons have no overlaps? |
2 |
|
|
Polygons have no unintended gaps? |
2 |
|
|
''CODE" attribute field matches the FMU Code entered in the application by the WFDSS Data Manager? |
2 |
|
|
"Unit_ID" shapes will fit into the latest compiled version of FMU data that it will eventually be integrated into? No big overlaps? |
n/a |
Pass |
Consider using Count Overlaps tool in ArcPro against neighboring unit boundaries |
Unit_IDs checked agains NWCG current valid Unit IDS. |
n/a |
|
https://unitid.nifc.gov/ords/prd/f?p=116:101:10417641311651:::RP:: |
The data from this AGENCY will not overlap with data from the same "AGENCY" in the latest compiled version of the FMU data? |
n/a |
P |
Consider using Count Overlaps tool in ArcPro for shapes within unit boundaries. Strategic Objective shapes should not overlap. Managment Requirement shapes MAY have overlaps. |
To Use the FMU/SO Shape Submission Checklist
Follow these steps for completing the FMU/SO Shape Submission Checklist.
- Create a new text attribute field, UnitID. Populated it with "WASPA."
- Recalculated the "Agency: attribute field to read "BIA."
- Select and delete all existing 'WASPA' polygons from the copy of FMU v7.1.
- Using the "Append" GP tool add the three new polygons to the dataset.
Evaluate the level of firefighter and aviation exposure required to successfully meet the current strategy and implement the course of action. Rank this element as N/A (Very Low), Low, Moderate, or High. Considers the likelihood that those resources will be effective; exposure of firefighters; reliance on aircraft to accomplish objectives; and whether there are clearly defined trigger points.
In This Section |
See Also |
Reference |