Name: MRGP Hydrologically connected road segments

Display Field: MRGP2ID

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>The REI reassessment shall include all hydrologically-connected municipal road segments. This includes all hydrologically-connected road segments that appear on the ANR Atlas at the time that the REI is conducted, as well as all road segments likely to discharge to waters or wetlands. All hydrologically-connected road segments depicted on</SPAN></P><P><SPAN>the ANR Atlas shall be field visited and evaluated using the REI Form. Additionally, the applicant may propose to add road segments to its REI based on an evaluation of the following criteria:</SPAN></P><P><SPAN /></P><P><SPAN>1. For closed drainage roads : the catch basin outlet pipe is within 500 feet of a water of the State or wetland.</SPAN></P><P><SPAN>2. For all other municipal roads:</SPAN></P><P><SPAN>a) The municipal road segment is within 100 feet of a water of the State or wetland;</SPAN></P><P><SPAN>b) The municipal road segment bisects any water of the State or wetland, or a defined channel;</SPAN></P><P><SPAN>c) The municipal road segment is uphill from, and drains to, a municipal road that bisects a water of the State or wetland, and should be included in the REI to accurately capture the extent of the stormwater watershed.</SPAN></P><P><SPAN /></P><P><SPAN>If a road segment appears on the ANR Atlas and none of the above conditions are observed in the field, municipalities may propose to re-classify a segment as not hydrologically connected. Alternately, if none of the above conditions are observed in the field, but the segment is likely to discharge to waters or wetlands, a permittee shall propose to add this segment to the inventory following a field evaluation.</SPAN></P><P><SPAN>The addition or removal of any road segments not appearing on the ANR Atlas must be documented as part of the REI, and justification for the removal or addition shall be included in the Implementation Table.</SPAN></P><P><SPAN>The Secretary may determine at any time that a road segment not identified on the ANR Atlas is hydrologically connected, based on the criteria listed above, as well as other site specific factors that indicate the likelihood of a discharge, including slope, soil type, proximity to waters, etc. When the Secretary determines that an unmapped road segment is hydrologically connected and informs the municipality of its determination, the</SPAN></P><P><SPAN>permittee shall include the segment in its Implementation Table as part of the next annual report.</SPAN></P></DIV>

Copyright Text:

Default Visibility: false

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 150000

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: -8175718.062671552
YMin: 5269870.502431508
XMax: -7955591.73352605
YMax: 5624418.656924386
Spatial Reference: 102100  (3857)

Drawing Info:

Renderer:
Unique Value Renderer:
Field 1: HydroConSurvey
Field 2: N/A
Field 3: N/A
Field Delimiter: ,
Default Symbol:
N/A
Default Label: N/A
UniqueValueInfos:
• Value: Yes
  Label: Hydrologically connected road segment
  Description: N/A
  Symbol:
  Style: esriSLSSolid
  Color: [197, 0, 255, 255]
  Width: 2
• Value: No
  Label: Town highway road segment not connected
  Description: N/A
  Symbol:
  Style: esriSLSSolid
  Color: [204, 204, 204, 255]
  Width: 2
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• AssessmentDate ( type: esriFieldTypeDate, alias: AssessmentDate, length: 8 )
• TOWNGEOID ( type: esriFieldTypeString, alias: GEOID, length: 20 )
• MRGP2ID ( type: esriFieldTypeString, alias: MRGP2ID, length: 30 )
• SegmentID ( type: esriFieldTypeString, alias: SegmentID, length: 30 )
• SegLength ( type: esriFieldTypeDouble, alias: SegLength )
• RDFLNAME ( type: esriFieldTypeString, alias: RDFLNAME, length: 60 )
• HydroConSurvey ( type: esriFieldTypeString, alias: HydroConnected, length: 10 )
• RoadTypeID ( type: esriFieldTypeString, alias: RoadTypeID, length: 10 )
• CreationDate ( type: esriFieldTypeDate, alias: CreationDate, length: 8 )
• Creator ( type: esriFieldTypeString, alias: Creator, length: 128 )
• EditDate ( type: esriFieldTypeDate, alias: EditDate, length: 8 )
• Editor ( type: esriFieldTypeString, alias: Editor, length: 128 )
• Source ( type: esriFieldTypeString, alias: Source, length: 100 )
• COUNTY ( type: esriFieldTypeString, alias: COUNTY, length: 100 )
• RPC ( type: esriFieldTypeString, alias: RPC, length: 100 )
• MuniName ( type: esriFieldTypeString, alias: MuniName, length: 100 )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )

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

  Iteminfo   Thumbnail   Metadata