Parent Layer: Wildfire Threat and Behavior

Name: Existing Vegetation Type Physiognomy

Display Field: EVT_NAME

Type: Raster Layer

Geometry Type: null

Description: This EVT dataset is a subset of the LANDFIRE existing vegeation type fuel data. The data was subset for use in the West Wide Wildfire Risk Assessment. The LANDFIRE existing vegetation layers describe the following elements of existing vegetation for each LANDFIRE mapping zone: existing vegetation type, existing vegetation canopy cover, and existing vegetation height. Vegetation is mapped using predictive landscape models based on extensive field reference data, satellite imagery, biophysical gradient layers, and classification and regression trees. DATA SUMMARY: The existing vegetation type (EVT) data layer represents the current distribution of the terrestrial ecological systems classification developed by NatureServe for the western Hemisphere (http://www.natureserve.org/publications/usEcologicalsystems.jsp). A terrestrial ecological system is defined as a group of plant community types (associations) that tend to co-occur within landscapes with similar ecological processes, substrates, and/or environmental gradients. EVTs are mapped in LANDFIRE using decision tree models, field reference data, Landsat imagery, digital elevation model data, and biophysical gradient data. Go to http://www.landfire.gov/participate_acknowledgements.php for more information regarding contributors of field plot data. Decision tree models are developed separately for each of the three life-forms -tree, shrub, and herbaceous - using C5 software. Life-form specific cross validation error matrices are generated during this process to assess levels of accuracy of the models. Decision tree relationships are then used to generate life-form specific EVT spatial data layers. The final EVT and Environemtanl Site Potential (ESP) layers are compared and rectified through a series of QA/QC measures. Values of one or more of these data layers are adjusted based on a hierarchical decision tree ruleset in order to align the respective life-forms and life-zone of each ESP and EVT category. The EVT layer is used in many subsequent LANDFIRE data layers. Refer to spatial metadata for date ranges of field plot data and satellite imagery for each LANDFIRE map zone. REFRESH 2008 (lf_1.1.0):Refresh 2008 (lf_1.1.0) used Refresh 2001 (lf_1.0.5) data as a launching point to incorporate disturbance and its severity, both managed and natural, which occurred on the landscape after 2001. Specific examples of disturbance are: fire, vegetation management, weather, and insect and disease. The final disturbance data used in Refresh 2008 (lf_1.1.0) is the result of several efforts that include data derived in part from remotely sensed land change methods, Monitoring Trends in Burn Severity (MTBS), and the LANDFIRE Refresh events data call. Vegetation growth was modeled where both disturbance and non-disturbance occurs. The data was subset by: Sanborn Solutions 610 SW Broadway, Ste #310 Portland, OR 97205 (503)228-8708

Service Item Id: a8fe1562ca8e4c5e8c43523983e2ff5b

Copyright Text: Data have been collected and analyzed by teams at both USGS EROS, Sioux Falls, SD and at the USFS, Rocky Mountain Research Station, Missoula, MT. Depending on the data set described primary responsibility may reside with USGS EROS or with USFS. Contact information will be listed in the Contact Section and in the Metadata Reference section with regards to the primary responsibility.

Default Visibility: false

MaxRecordCount: 0

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: false

Supports Statistics: false

Has Labels: false

Can Modify Layer: false

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: -1.4046186555459585E7
YMin: 4955822.696051056
XMax: -1.2800436555459585E7
YMax: 6042242.696051056
Spatial Reference: 102100  (3857)

Drawing Info:

N/A

Advanced Query Capabilities:

Supports Statistics: false
Supports OrderBy: false
Supports Distinct: false
Supports Pagination: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: false
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeNone

Type ID Field: null

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• VALUE ( type: esriFieldTypeInteger, alias: VALUE )
• COUNT ( type: esriFieldTypeInteger, alias: COUNT )
• EVT_NAME ( type: esriFieldTypeString, alias: EVT_NAME, length: 100 )
• SYSTEMGROU ( type: esriFieldTypeDouble, alias: SYSTEMGROU )
• SYSTMGRPNA ( type: esriFieldTypeString, alias: SYSTMGRPNA, length: 100 )
• SAF_SRM ( type: esriFieldTypeString, alias: SAF_SRM, length: 100 )
• NVCSORDER ( type: esriFieldTypeString, alias: NVCSORDER, length: 100 )
• NVCSCLASS ( type: esriFieldTypeString, alias: NVCSCLASS, length: 100 )
• NVCSSUBCLA ( type: esriFieldTypeString, alias: NVCSSUBCLA, length: 100 )
• SYSTMGRPPH ( type: esriFieldTypeString, alias: SYSTMGRPPH, length: 100 )
• R ( type: esriFieldTypeSmallInteger, alias: R )
• G ( type: esriFieldTypeSmallInteger, alias: G )
• B ( type: esriFieldTypeSmallInteger, alias: B )
• RED ( type: esriFieldTypeSingle, alias: RED )
• GREEN ( type: esriFieldTypeSingle, alias: GREEN )
• BLUE ( type: esriFieldTypeSingle, alias: BLUE )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata