All Layers and Tables (SW_Direct_Drivers_of

Layers:

Layer: Direct Drivers of Change (0)

Name:

Display Field:

Type:

Geometry Type:

Description:

The goal of the project is to support strategic identification and prioritization of sites for implementation in DEC’s Trees for Tribs program, which enlists the help of volunteers to plant native trees and shrubs in riparian buffers of streams to improve wildlife habitat, water quality, climate resiliency, and to provide flood protection during storm events. Further details on the project can be found here: http://nynhp.org/treesfortribsny

Catchments have up to three scores for any indicator- the raw value, the normalized value, and the percentile. Normalized values are named with a "N_" before the indicator code. Percentile values are named with a "P_" before the indicator code.

Example: Canopy Cover.

H1_CAN is the raw value, the average canopy cover in the catchment. The value in this field can be compared to the value of any other catchment in the state to accurately assess the relative conditions in the catchments.

N_H1_CAN is the normalized value. This is a rescaling of the raw value (which may have ranged from, for example, 5-80) so that the catchment in the subwatershed with the lowest raw value gets a normalized value of 0, and the catchment with the highest raw value in the subwatershed gets a normalized value of 1. Normalized scores were used to calculate composite scores like Ecological Health or the Comprehensive Score, which are the sum of muiltiple indicators whose raw values are measured in different scales. Normalized scores should not be used to compare the condition of catchments in different subwatersheds.

P_H1_CAN is the percentile value. This indicates the relative rank of the catchment's raw value relative to the other catchemnts in the subwatershed. It is used for display purposes only. In cases where every catchment in a subwatershed has the same score, they will all have a percentile value of 50. Catchments with the same percentle score in different subwatersheds do not necessesarily have the same habitat conditions. The percentile score merely indicates that both are the same relative rank in their respective subwatersheds. Percentile scores should not be used to compare the condition of catchments in different subwatersheds.

Be aware that composite scores like Ecological Health (pre_H0 and H0) , Ecological Stress (pre_S0 and S0), Comprehensive Score (pre_COMP and COMP), and Resilience (pre-R0 and R0), because they are the product of addition and subtraction of normalized scores, should not be compared across subwatersheds as raw values. The Community Involvement Score (C0) , because it is just a sum of the raw component scores (C1_CS, C2_WA,C3_TT), is the only composite score that can be accurately compared across subwatersheds.

See the report for more details.

Copyright Text:

Min. Scale:

Max. Scale:

Default Visibility:

Max Record Count:

Supported query Formats:

Use Standardized Queries:

Extent:

Drawing Info:

{"renderer":{"type":"classBreaks","authoringInfo":{"type":"classedColor","colorRamp":{"type":"algorithmic","algorithm":"esriHSVAlgorithm","fromColor":[245,245,0,255],"toColor":[245,0,0,255]},"classificationMethod":"esriClassifyManual"},"field":"Risk","classificationMethod":"esriClassifyManual","minValue":0,"classBreakInfos":[{"symbol":{"type":"esriSFS","style":"esriSFSSolid","color":[230,230,0,255],"outline":{"type":"esriSLS","style":"esriSLSSolid","color":[110,110,110,255],"width":0.7}},"classMaxValue":1,"label":"Low"},{"symbol":{"type":"esriSFS","style":"esriSFSSolid","color":[230,152,0,255],"outline":{"type":"esriSLS","style":"esriSLSSolid","color":[110,110,110,255],"width":0.7}},"classMaxValue":2,"label":"Medium"},{"symbol":{"type":"esriSFS","style":"esriSFSSolid","color":[230,76,0,255],"outline":{"type":"esriSLS","style":"esriSLSSolid","color":[110,110,110,255],"width":0.7}},"classMaxValue":3,"label":"High"}],"legendOptions":{"order":"ascendingValues"}},"scaleSymbols":true,"transparency":0,"labelingInfo":null}

HasZ:

HasM:

Has Attachments:

Has Geometry Properties:

HTML Popup Type:

Object ID Field:

Unique ID Field:

Global ID Field:

Type ID Field:

Fields:

FID (type: esriFieldTypeOID, alias: FID, SQL Type: sqlTypeOther, length: 0, nullable: false, editable: false)
FEATUREID (type: esriFieldTypeDouble, alias: FEATUREID, SQL Type: sqlTypeOther, nullable: true, editable: true)
NextDownID (type: esriFieldTypeDouble, alias: NextDownID, SQL Type: sqlTypeOther, nullable: true, editable: true)
HUC_12_Nam (type: esriFieldTypeString, alias: HUC_12_Nam, SQL Type: sqlTypeOther, length: 50, nullable: true, editable: true)
NAME (type: esriFieldTypeString, alias: NAME, SQL Type: sqlTypeOther, length: 120, nullable: true, editable: true)
HUC6 (type: esriFieldTypeString, alias: HUC6, SQL Type: sqlTypeOther, length: 50, nullable: true, editable: true)
Risk (type: esriFieldTypeInteger, alias: Risk, SQL Type: sqlTypeOther, nullable: true, editable: true)
Shape_Leng (type: esriFieldTypeDouble, alias: Shape_Leng, SQL Type: sqlTypeOther, nullable: true, editable: true)
Shape__Area (type: esriFieldTypeDouble, alias: Shape__Area, SQL Type: sqlTypeDouble, nullable: true, editable: false)
Shape__Length (type: esriFieldTypeDouble, alias: Shape__Length, SQL Type: sqlTypeDouble, nullable: true, editable: false)

Templates:

Risk: 0.5

Risk: 1.5

Risk: 2.5

Is Data Versioned:

Has Contingent Values:

Supports Rollback On Failure Parameter:

Last Edit Date:

Schema Last Edit Date:

Data Last Edit Date:

All Layers and Tables (SW_Direct_Drivers_of_Change)

Layers:

Layer: Direct Drivers of Change (0)