Layers:

Layer: MS4 Outfalls (0)

Name: MS4 Outfalls

Display Field: UniqueID

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>INDEX</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Section 1: </SPAN></SPAN><SPAN><SPAN>Responsible Parties</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Section 2: </SPAN></SPAN><SPAN><SPAN>Explanation of Attribute Data</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Section 3: </SPAN></SPAN><SPAN STYLE="font-weight:bold;">Handling of Data and Recommendations</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;">Section 4: Additional Considerations </SPAN></P><P /><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>SECTION 1</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Responsible Parties</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-style:italic;"><SPAN>Parties responsible for updating this layer:</SPAN></SPAN></P><P><SPAN><SPAN>- The MS4 Coordinator/Public Works Environmental Compliance Manager at the Department of Public Works is responsible for the maintenance and updating of the database, as needed.</SPAN></SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN STYLE="font-size:12pt"><SPAN>- The GIS Technician at the Department of Community Development is responsible for the addition of new outfalls from recent/new construction projects.</SPAN></SPAN></P><P /><P /><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>SECTION 2</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Explanation of Attribute Data</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Unique_ID</SPAN></SPAN><SPAN><SPAN>- </SPAN></SPAN><SPAN><SPAN>Unique identifying value assigned to a feature, generally same as OBJECTID</SPAN></SPAN><SPAN><SPAN>(this will replace existing Outfall ID).</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Dominant Watershed (VAHU6)</SPAN></SPAN><SPAN><SPAN>– the watershed that the outfall is geographically located in, this does not take drainage area to the outfall into consideration.</SPAN></SPAN></P><OL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>PS22 – Blacks Run</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>PS23 – Cooks Creek</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>PS26 – North River-Mill Creek</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>PS33 – Cub Rub</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>PS56 – Linville Creek</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 72;"><SPAN><SPAN>PS59 – Dry Fork</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>TMDLs</SPAN></SPAN><SPAN><SPAN>– The TMDL (Total Maximum Daily Load) value that corresponds to the dominant watershed. This information is derived from the Virginia DEQ. </SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>PS22; E.Coli, TSS</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>PS23; E.Coli, TSS, Total P</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>PS26; E.Coli</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>PS33; E.Coli</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>PS56; E.Coli, TSS</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>PS59; E.Coli, TSS</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>None</SPAN></SPAN></P></LI></OL><P STYLE="font-weight:bold;text-indent:48;margin:0 0 0 0;"><SPAN><SPAN>Notes:</SPAN></SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN><SPAN>- All local waterways in Harrisonburg are impaired at this time.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>City_MS4</SPAN></SPAN><SPAN><SPAN>– Designates outfalls owned and maintained by a City entity (most likely Public Works)</SPAN></SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Yes – publically owned/maintained</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>No – not publically owned or maintained </SPAN></SPAN></P></LI></UL><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Outfalls_Type</SPAN></SPAN><SPAN><SPAN>– This designates where the drainage comes from and where it is being relayed. </SPAN></SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>City to Stream</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>VDOT to Stream</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>JMU to Stream</SPAN></SPAN></P></LI></UL><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Install_Date</SPAN></SPAN><SPAN><SPAN>– date that the pipe was first installed.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Owned By</SPAN></SPAN><SPAN><SPAN>– </SPAN></SPAN><SPAN><SPAN>designation of the entity that has ownership of the BMP</SPAN></SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Private</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>City</SPAN></SPAN></P></LI></UL><P STYLE="margin:0 0 0 24;"><SPAN STYLE="font-weight:bold;"><SPAN>Notes:</SPAN></SPAN></P><P STYLE="text-indent:24;margin:0 0 0 0;"><SPAN><SPAN>- There may be circumstances where an outfall is owned by a certain entity but maintained by another.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Maintained By</SPAN></SPAN><SPAN><SPAN>- </SPAN></SPAN><SPAN><SPAN>designation of the entity that is responsible for maintaining the BMP</SPAN></SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Private</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>City</SPAN></SPAN></P></LI></UL><P STYLE="margin:0 0 0 24;"><SPAN STYLE="font-weight:bold;"><SPAN>Notes:</SPAN></SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN><SPAN>- There may be circumstances where an outfall is owned by a certain entity but maintained by another.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Last_Inspection_Date</SPAN></SPAN><SPAN><SPAN>- </SPAN></SPAN><SPAN><SPAN>date of the most recent inspection on the BMP site, this should be the same as the condition date.</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Condition</SPAN></SPAN><SPAN><SPAN>- </SPAN></SPAN><SPAN><SPAN>date of condition report filing.</SPAN></SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>1 – Good</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>2 – Okay</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>3 – Poor</SPAN></SPAN></P></LI></UL><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Condition_Date</SPAN></SPAN><SPAN><SPAN>- </SPAN></SPAN><SPAN><SPAN>date of condition report filing.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Enabled </SPAN></SPAN><SPAN><SPAN>– 1 or 0</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Attachment</SPAN></SPAN><SPAN><SPAN>– static photo taken in the field during inspections.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Plan_Link </SPAN></SPAN><SPAN><SPAN>- file path to location where site plans for the corresponding outfalls are found.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Inspections_Link – </SPAN></SPAN><SPAN><SPAN>link to City Works report form.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Location</SPAN></SPAN><SPAN><SPAN>– Closest address to incident location, full address - without ZIP code.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>PlanDate </SPAN></SPAN><SPAN><SPAN>– date of the site plan where the corresponding outfalls are found.</SPAN></SPAN></P><P /><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>SECTION 3</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Handling of Data and Recommendations</SPAN></SPAN></P><P /><TABLE><TBODY><TR><TD><P STYLE="text-align:Center;font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Existing City Layers</SPAN></SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>There is a related layer used for historical cross-referencing, called: “Outfall_Recon_Inspection_and_data”</SPAN></SPAN></P><P /><P><SPAN><SPAN>Refer to “Storm Pipe Information” below as well.</SPAN></SPAN></P></TD><TD><P /></TD></TR><TR><TD><P STYLE="text-align:Center;margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;">Storm Pipe Information</SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN>During inspections, pipe sizes and pipe material are noted on the inspection form, NOT in Outfalls.</SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>These values are updated into the </SPAN></SPAN><SPAN STYLE="font-weight:bold;"><SPAN>storm pipes layer</SPAN></SPAN><SPAN><SPAN>, “harrisonburg_vector.HARRISONBURG.swSTORMPIPES”</SPAN></SPAN></P></TD><TD><P /></TD></TR><TR><TD><P STYLE="text-align:Center;margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;">Placing the Outfall Point</SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN>The point should be located on the exposed, open, end of the pipe where contents exit the pipe.</SPAN></P></TD><TD><P /></TD></TR><TR><TD><P STYLE="text-align:Center;margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;">Last Inspection Date</SPAN></P></TD><TD><P STYLE="margin:0 0 0 0;"><SPAN>This should be the date of the most recent inspection report for the outfall.</SPAN></P></TD><TD><P STYLE="font-style:italic;margin:0 0 0 0;"><SPAN><SPAN>The inspection data should be the same date as the Condition Date field.</SPAN></SPAN></P></TD></TR></TBODY></TABLE><P /><P /><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>SECTION 4</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Additional Considerations</SPAN></SPAN></P><P /><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>A. History &amp; Logic of the Data</SPAN></SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN><SPAN>- 6/21/2018 – The outfall’s last inspection data should be the same as the condition date.</SPAN></SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN><SPAN>&gt; The data of the most recent inspection report should be the value in this field – which is should be the same as the Condition Date field.</SPAN></SPAN></P><P /><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>B. Department Notes</SPAN></SPAN></P><P><SPAN><SPAN>***During inspections, pipe sizes and pipe material are noted on the inspection form, NOT in Outfalls. These values are updated into the </SPAN></SPAN><SPAN STYLE="font-weight:bold;"><SPAN>storm pipes layer</SPAN></SPAN><SPAN><SPAN>, “harrisonburg_vector.HARRISONBURG.swSTORMPIPES”***</SPAN></SPAN></P><OL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Inspection forms to be developed and tracked within city works which will outline outfall observations upon inspection, presence of illicit discharges, flow characteristics, notes section for infrastructure damage (to spark a new work order, separate from outfall information)</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Kathy (Community Development) adds new outfalls with new construction projects</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Alfredo (Public Works) adds new outfalls due to PW maintenance with notification from Cityworks</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Kelley/Alfredo (Public Works) will add discovered outfalls</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Inspectors should refer to the outfall policy and Outfall Inspection SOP for reference during inspections.</SPAN></SPAN></P></LI></OL><P /><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>C. Unresolved Questions</SPAN></SPAN></P><P STYLE="text-indent:48;margin:0 0 0 0;"><SPAN><SPAN>- </SPAN></SPAN><SPAN><SPAN>Kelley: “I’m not sure where the break point is for box sizes to become culverts (and be inspected with bridges)”</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>D. Other</SPAN></SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN><SPAN>- N/A</SPAN></SPAN></P></DIV></DIV></DIV>

Service Item Id: 6b35458166af458c98e379283638ae45

Copyright Text: The ms4Outfalls data layer was created by Patrick Wade in the Public Works Department of the City of Harrisonburg, on 6/5/2017. This information was created under the supervision of the Systems Analyst, MS4 Coordinator and Environmental Compliance Manager and in association with the GIS Technician at the Department of Community Development.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 36111.909643

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: 1.1365311549335659E7
YMin: 6826356.953409985
XMax: 1.1385927797473162E7
YMax: 6857131.5549183935
Spatial Reference: 102746  (2283)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSMSCircle
Color: [0, 169, 230, 255]
Size: 10.0
Angle: 0.0
XOffset: 0
YOffset: 0
Outline:
[0, 0, 0, 255] Width: 0
Label: N/A
Description: N/A
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


HasZ: true

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• UniqueID ( type: esriFieldTypeString, alias: Unique_ID, length: 50 )
• DominantWatershed ( type: esriFieldTypeString, alias: DominantWatershed, length: 255 , Coded Values: [PS22 - Blacks Run: PS22 - Blacks Run] , [PS23 - Cooks Creek: PS23 - Cooks Creek] , [PS26 - North River-Mill Creek: PS26 - North River-Mill Creek] , ...3 more... )
• TMDLS ( type: esriFieldTypeString, alias: TMDLS, length: 255 , Coded Values: [None: None] , [PS26; E. Coli: PS26; E. Coli] , [PS56; E. Coli, TSS: PS56; E. Coli, TSS] , ...4 more... )
• CityMS4 ( type: esriFieldTypeString, alias: City_MS4, length: 255 , Coded Values: [City: City] , [Other: Other] )
• OutfallsType ( type: esriFieldTypeString, alias: Outfalls_Type, length: 255 , Coded Values: [City to Stream: City to Stream] , [VDOT to Stream: VDOT to Stream] , [JMU to Stream: JMU to Stream] )
• ConveyanceType ( type: esriFieldTypeString, alias: Conveyance_Type, length: 255 , Coded Values: [Box Culvert: Box Culvert] , [Ditch: Ditch] , [Pipe: Pipe] )
• InstallDate ( type: esriFieldTypeDate, alias: Install_Date, length: 8 )
• OwnedBy ( type: esriFieldTypeString, alias: Owned_By, length: 255 , Coded Values: [City: City] , [Other: Other] )
• MaintaintedBy ( type: esriFieldTypeString, alias: Maintainted_By, length: 255 , Coded Values: [City: City] , [Other: Other] )
• Condition ( type: esriFieldTypeSmallInteger, alias: Condition )
• ConditionDate ( type: esriFieldTypeDate, alias: Condition_Date, length: 8 )
• Enabled ( type: esriFieldTypeSmallInteger, alias: Enabled )
• Attachmant ( type: esriFieldTypeString, alias: Attachmant, length: 255 )
• PlanLink ( type: esriFieldTypeString, alias: Plan_Link, length: 255 )
• InspectionLink ( type: esriFieldTypeString, alias: Inspection_Link, length: 255 )
• Location ( type: esriFieldTypeString, alias: Location, length: 255 )
• PlanDate ( type: esriFieldTypeDate, alias: PlanDate, length: 8 )
• created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
• created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
• OutfallID ( type: esriFieldTypeString, alias: OutfallID, length: 50 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )
• LandUse ( type: esriFieldTypeString, alias: Land Use, length: 50 , Coded Values: [Forest/Vegetative: Forest/Vegetative] , [Urban/Residential: Urban/Residential] , [Agriculture: Agriculture] )
• InspDate ( type: esriFieldTypeDate, alias: Inspection Date, length: 8 )