{ "culture": "en-US", "name": "", "guid": "", "catalogPath": "", "snippet": "The stormwater Outfalls layer is a point-based dataset that documents the locations of stormwater pipe outfall locations throughout the city of Harrisonburg, VA. This layer will contain the data needed for Public Works and MS4 stormwater tracking and will be included in the annual report to the Department of Environmental Quality.", "description": "

INDEX<\/SPAN><\/SPAN><\/P>

Section 1: <\/SPAN><\/SPAN>Responsible Parties<\/SPAN><\/SPAN><\/P>

Section 2: <\/SPAN><\/SPAN>Explanation of Attribute Data<\/SPAN><\/SPAN><\/P>

Section 3: <\/SPAN><\/SPAN>Handling of Data and Recommendations<\/SPAN><\/P>

Section 4: Additional Considerations <\/SPAN><\/P>

SECTION 1<\/SPAN><\/SPAN><\/P>

Responsible Parties<\/SPAN><\/SPAN><\/P>

Parties responsible for updating this layer:<\/SPAN><\/SPAN><\/P>

- 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>

- 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>

SECTION 2<\/SPAN><\/SPAN><\/P>

Explanation of Attribute Data<\/SPAN><\/SPAN><\/P>

Unique_ID<\/SPAN><\/SPAN>- <\/SPAN><\/SPAN>Unique identifying value assigned to a feature, generally same as OBJECTID<\/SPAN><\/SPAN>(this will replace existing Outfall ID).<\/SPAN><\/SPAN><\/P>

Dominant Watershed (VAHU6)<\/SPAN><\/SPAN>\u2013 the watershed that the outfall is geographically located in, this does not take drainage area to the outfall into consideration.<\/SPAN><\/SPAN><\/P>

  1. PS22 \u2013 Blacks Run<\/SPAN><\/SPAN><\/P><\/LI>

  2. PS23 \u2013 Cooks Creek<\/SPAN><\/SPAN><\/P><\/LI>

  3. PS26 \u2013 North River-Mill Creek<\/SPAN><\/SPAN><\/P><\/LI>

  4. PS33 \u2013 Cub Rub<\/SPAN><\/SPAN><\/P><\/LI>

  5. PS56 \u2013 Linville Creek<\/SPAN><\/SPAN><\/P><\/LI>

  6. PS59 \u2013 Dry Fork<\/SPAN><\/SPAN><\/P>

    TMDLs<\/SPAN><\/SPAN>\u2013 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>

  7. PS22; E.Coli, TSS<\/SPAN><\/SPAN><\/P><\/LI>

  8. PS23; E.Coli, TSS, Total P<\/SPAN><\/SPAN><\/P><\/LI>

  9. PS26; E.Coli<\/SPAN><\/SPAN><\/P><\/LI>

  10. PS33; E.Coli<\/SPAN><\/SPAN><\/P><\/LI>

  11. PS56; E.Coli, TSS<\/SPAN><\/SPAN><\/P><\/LI>

  12. PS59; E.Coli, TSS<\/SPAN><\/SPAN><\/P><\/LI>

  13. None<\/SPAN><\/SPAN><\/P><\/LI><\/OL>

    Notes:<\/SPAN><\/SPAN><\/P>

    - All local waterways in Harrisonburg are impaired at this time.<\/SPAN><\/SPAN><\/P>

    City_MS4<\/SPAN><\/SPAN>\u2013 Designates outfalls owned and maintained by a City entity (most likely Public Works)<\/SPAN><\/SPAN><\/P>

    • Yes \u2013 publically owned/maintained<\/SPAN><\/SPAN><\/P><\/LI>

    • No \u2013 not publically owned or maintained <\/SPAN><\/SPAN><\/P><\/LI><\/UL>

      Outfalls_Type<\/SPAN><\/SPAN>\u2013 This designates where the drainage comes from and where it is being relayed. <\/SPAN><\/SPAN><\/P>

      • City to Stream<\/SPAN><\/SPAN><\/P><\/LI>

      • VDOT to Stream<\/SPAN><\/SPAN><\/P><\/LI>

      • JMU to Stream<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

        Install_Date<\/SPAN><\/SPAN>\u2013 date that the pipe was first installed.<\/SPAN><\/SPAN><\/P>

        Owned By<\/SPAN><\/SPAN>\u2013 <\/SPAN><\/SPAN>designation of the entity that has ownership of the BMP<\/SPAN><\/SPAN><\/P>

        • Private<\/SPAN><\/SPAN><\/P><\/LI>

        • City<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

          Notes:<\/SPAN><\/SPAN><\/P>

          - There may be circumstances where an outfall is owned by a certain entity but maintained by another.<\/SPAN><\/SPAN><\/P>

          Maintained By<\/SPAN><\/SPAN>- <\/SPAN><\/SPAN>designation of the entity that is responsible for maintaining the BMP<\/SPAN><\/SPAN><\/P>

          • Private<\/SPAN><\/SPAN><\/P><\/LI>

          • City<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

            Notes:<\/SPAN><\/SPAN><\/P>

            - There may be circumstances where an outfall is owned by a certain entity but maintained by another.<\/SPAN><\/SPAN><\/P>

            Last_Inspection_Date<\/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>

            Condition<\/SPAN><\/SPAN>- <\/SPAN><\/SPAN>date of condition report filing.<\/SPAN><\/SPAN><\/P>

            • 1 \u2013 Good<\/SPAN><\/SPAN><\/P><\/LI>

            • 2 \u2013 Okay<\/SPAN><\/SPAN><\/P><\/LI>

            • 3 \u2013 Poor<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

              Condition_Date<\/SPAN><\/SPAN>- <\/SPAN><\/SPAN>date of condition report filing.<\/SPAN><\/SPAN><\/P>

              Enabled <\/SPAN><\/SPAN>\u2013 1 or 0<\/SPAN><\/SPAN><\/P>

              Attachment<\/SPAN><\/SPAN>\u2013 static photo taken in the field during inspections.<\/SPAN><\/SPAN><\/P>

              Plan_Link <\/SPAN><\/SPAN>- file path to location where site plans for the corresponding outfalls are found.<\/SPAN><\/SPAN><\/P>

              Inspections_Link \u2013 <\/SPAN><\/SPAN>link to City Works report form.<\/SPAN><\/SPAN><\/P>

              Location<\/SPAN><\/SPAN>\u2013 Closest address to incident location, full address - without ZIP code.<\/SPAN><\/SPAN><\/P>

              PlanDate <\/SPAN><\/SPAN>\u2013 date of the site plan where the corresponding outfalls are found.<\/SPAN><\/SPAN><\/P>

              SECTION 3<\/SPAN><\/SPAN><\/P>

              Handling of Data and Recommendations<\/SPAN><\/SPAN><\/P>

              Existing City Layers<\/SPAN><\/SPAN><\/P><\/TD>

              There is a related layer used for historical cross-referencing, called: \u201cOutfall_Recon_Inspection_and_data\u201d<\/SPAN><\/SPAN><\/P>

              Refer to \u201cStorm Pipe Information\u201d below as well.<\/SPAN><\/SPAN><\/P><\/TD>

              <\/TD><\/TR>

              Storm Pipe Information<\/SPAN><\/P><\/TD>

              During inspections, pipe sizes and pipe material are noted on the inspection form, NOT in Outfalls.<\/SPAN><\/P>

              These values are updated into the <\/SPAN><\/SPAN>storm pipes layer<\/SPAN><\/SPAN>, \u201charrisonburg_vector.HARRISONBURG.swSTORMPIPES\u201d<\/SPAN><\/SPAN><\/P><\/TD>

              <\/TD><\/TR>

              Placing the Outfall Point<\/SPAN><\/P><\/TD>

              The point should be located on the exposed, open, end of the pipe where contents exit the pipe.<\/SPAN><\/P><\/TD>

              <\/TD><\/TR>

              Last Inspection Date<\/SPAN><\/P><\/TD>

              This should be the date of the most recent inspection report for the outfall.<\/SPAN><\/P><\/TD>

              The inspection data should be the same date as the Condition Date field.<\/SPAN><\/SPAN><\/P><\/TD><\/TR><\/TBODY><\/TABLE>

              SECTION 4<\/SPAN><\/SPAN><\/P>

              Additional Considerations<\/SPAN><\/SPAN><\/P>

              A. History & Logic of the Data<\/SPAN><\/SPAN><\/P>

              - 6/21/2018 \u2013 The outfall\u2019s last inspection data should be the same as the condition date.<\/SPAN><\/SPAN><\/P>

              > The data of the most recent inspection report should be the value in this field \u2013 which is should be the same as the Condition Date field.<\/SPAN><\/SPAN><\/P>

              B. Department Notes<\/SPAN><\/SPAN><\/P>

              ***During inspections, pipe sizes and pipe material are noted on the inspection form, NOT in Outfalls. These values are updated into the <\/SPAN><\/SPAN>storm pipes layer<\/SPAN><\/SPAN>, \u201charrisonburg_vector.HARRISONBURG.swSTORMPIPES\u201d***<\/SPAN><\/SPAN><\/P>

              1. 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>

              2. Kathy (Community Development) adds new outfalls with new construction projects<\/SPAN><\/SPAN><\/P><\/LI>

              3. Alfredo (Public Works) adds new outfalls due to PW maintenance with notification from Cityworks<\/SPAN><\/SPAN><\/P><\/LI>

              4. Kelley/Alfredo (Public Works) will add discovered outfalls<\/SPAN><\/SPAN><\/P><\/LI>

              5. Inspectors should refer to the outfall policy and Outfall Inspection SOP for reference during inspections.<\/SPAN><\/SPAN><\/P><\/LI><\/OL>

                C. Unresolved Questions<\/SPAN><\/SPAN><\/P>

                - <\/SPAN><\/SPAN>Kelley: \u201cI\u2019m not sure where the break point is for box sizes to become culverts (and be inspected with bridges)\u201d<\/SPAN><\/SPAN><\/P>

                D. Other<\/SPAN><\/SPAN><\/P>

                - N/A<\/SPAN><\/SPAN><\/P><\/DIV><\/DIV><\/DIV>", "summary": "The stormwater Outfalls layer is a point-based dataset that documents the locations of stormwater pipe outfall locations throughout the city of Harrisonburg, VA. This layer will contain the data needed for Public Works and MS4 stormwater tracking and will be included in the annual report to the Department of Environmental Quality.", "title": "PublicWorks.HARRISONBURG.ms4Outfalls", "tags": [ "City of Harrisonburg", "Stormwater", "Stormwater Outfalls", "Outfalls", "Outfall", "ms4", "ms4 Outfalls", "ms4Outfalls" ], "type": "", "typeKeywords": [], "thumbnail": "", "url": "", "minScale": 150000000, "maxScale": 5000, "spatialReference": "", "accessInformation": "The ms4Outfalls data layer was created by Patrick Wade in the Public Works Department of the City of Harrisonburg, on 6/5/2017.\nThis 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.", "licenseInfo": "" }