20160510 10510600 1.0 FALSE swBMPs 002 -110512500.000000 11388544.593749 -88858000.000000 6860545.817775 1 swBMPs__ATTACHREL Relationship swBMPs__ATTACHREL Relationship Projected GCS_North_American_1983 Linear Unit: Foot_US (0.304801) NAD_1983_StatePlane_Virginia_North_FIPS_4501_Feet <ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.8'><WKT>PROJCS["NAD_1983_StatePlane_Virginia_North_FIPS_4501_Feet",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",11482916.66666666],PARAMETER["False_Northing",6561666.666666666],PARAMETER["Central_Meridian",-78.5],PARAMETER["Standard_Parallel_1",38.03333333333333],PARAMETER["Standard_Parallel_2",39.2],PARAMETER["Latitude_Of_Origin",37.66666666666666],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",2283]]</WKT><XOrigin>-110512500</XOrigin><YOrigin>-88858000</YOrigin><XYScale>3048.00609601219</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.00328083333333333</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>102746</WKID><LatestWKID>2283</LatestWKID></ProjectedCoordinateSystem> 20230424 10233400 20230424 10233400 150000000 5000 ItemDescription Version 6.2 (Build 9200) ; Esri ArcGIS 10.8.1.14362 swBMPs 1 -180.000000 180.000000 38.486923 -70.120740 The stormwater BMP's layer is a point-based dataset that documents the locations of Best Management Practice (BMP) improvements throughout the city of Harrisonburg, VA. This layer will carry the data needed for Cityworks and for doing business and will not include farm ponds or anything that is not an approved BMP. The point will be located in the center of the BMP. Existing City layers: (Prior to City Works) • Ponds_and_stormwater (located currently under Stormwater, polygon) • BMPDATA (located currently under MS4, point) See also, "Farm Ponds" and "BMPs" for comparison. City of Harrisonburg Public Works Department City of Harrisonburg Stormwater Stormwater BMPs BMP's BMPs BMP <DIV STYLE="text-align:Left;">INDEXSection 1: Responsible PartiesSection 2: Explanation of Attribute DataSection 3: Handling of Data and RecommendationsSection 4: Additional ConsiderationsSECTION 1 Responsible PartiesParties responsible for updating this layer:- The GIS Specialist is responsible for updating both layers for all new BMPs installed from site plans- MS4 Coordinator/Public Works Environmental Compliance Manager will update Property Type and Agreement date if maintenance agreement was signed for stormwater utilitySECTION 2Explanation of Attribute DataProject Name – enter name of development project BMP is associated withTax MapNumber – 3-part tax map identification number where the point is located, Sheet# Block# Parcel # Longitude – this is required for DEQ reporting Latitude – this is required for DEQ reportingDeedBookNumber – manual entry. This is the number where BMP agreements filed at the Court House. Pre 2008/2010 BMPs may not have this number. DateofAgreement – month/date/year that maintenance agreement was recordedAgreementType – <UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI STYLE="margin:0 0 0 48;">Private BMP without Agreement: These BMPs willnothave anything filed here <A href="file:///Construction-Post Construction BMPs-E&S-VSMP\Project - Facilities - Private With Maint Agree</A></LI><LI STYLE="margin:0 0 0 48;">Private BMP required with development, Agreement signed at time of development: These BMPs will be filed here <A href="file:///Construction-Post Construction BMPs-E&S-VSMP\Project - Facilities - Private With Maint Agree</A></LI><LI STYLE="margin:0 0 0 48;">Private BMP required with development, Agreement signed for stormwater utility credit: These BMPs are part of the Public Works stormwater utility fee program and all approved agreements will be filed here <A href="file:///Construction-Post Construction BMPs-E&S-VSMP\Project Facilities - Private Existing for SWM Utility Fee </A>(There will not be many of them)</LI><LI STYLE="margin:0 0 0 48;">Private BMP not required with development/ voluntary, Agreement signed for stormwater utility credit: These BMPs are part of the Public Works stormwater utility fee program and all approved agreements will be filed by Tax Map ID here <A href="file:///Utility Fee - Management\Application Information</A></LI><LI STYLE="margin:0 0 0 48;">Public BMP (City-Owned)</LI><LI STYLE="margin:0 0 0 48;">Nutrient Credit Purchased</LI></UL>Notes:- Kathy/Chip/Nancy? should populate ii. from new plans- Kelley/Rebecca will populate iii. And iv. From sw utility fee program- Nancy/Kelley will populate v. and vi.- Patrick (2017 Summer Intern) should have i. handled through his work reviewing the Historical BMP Database (this should only be historical BMPs – all new BMPs have agreements)BMPType – type of BMP facility installed<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI STYLE="margin:0 0 0 48;">Disconnection</LI><LI STYLE="margin:0 0 0 48;">Sheet Flow</LI><LI STYLE="margin:0 0 0 48;">Grass Channels</LI><LI STYLE="margin:0 0 0 48;">Soil Amendment</LI><LI STYLE="margin:0 0 0 48;">Vegetated Roof</LI><LI STYLE="margin:0 0 0 48;">Rainwater Harvesting</LI><LI STYLE="margin:0 0 0 48;">Permeable Pavement</LI><LI STYLE="margin:0 0 0 48;">Infiltration</LI><LI STYLE="margin:0 0 0 48;">Bioretention</LI><LI STYLE="margin:0 0 0 48;">Dry Swale</LI><LI STYLE="margin:0 0 0 48;">Wet Swale</LI><LI STYLE="margin:0 0 0 48;">Filtering Practices</LI><LI STYLE="margin:0 0 0 48;">Constructed Wetland</LI><LI STYLE="margin:0 0 0 48;">Wet Ponds</LI><LI STYLE="margin:0 0 0 48;">Extended Detention Pond</LI><LI STYLE="margin:0 0 0 48;">Detention Basin</LI><LI STYLE="margin:0 0 0 48;">Retention Basin</LI><LI STYLE="margin:0 0 0 48;">Sand Filters</LI><LI STYLE="margin:0 0 0 48;">Manufactured BMP Systems</LI><LI STYLE="margin:0 0 0 48;">Regenerative Stormwater Conveyance System</LI><LI STYLE="margin:0 0 0 48;">Stream Restoration</LI><LI STYLE="margin:0 0 0 48;">Nutrient Credit Purchased</LI></UL>Notes: - If Manufactured BMP System, then add field for manual entry of system name. ManufacturedBMPSystem – type of BMP system installed, refer to supervisor on specifications for this fieldTotal AcresTreated – acres draining to BMP – look at DEQ BMP Historical data excel submittalImperviousAcresTreated – This field refers to the impervious acres that fall within the drainage area leading to each BMP.Notes:- This number impacts the water quantity requirements for these BMPs.- For historical BMPs, Patrick (2017 Summer Intern) should have pulled these numbers that were available. For new BMPs, the only way to populate this field is from the stormwater calculations. Dominant Watershed(VAHU6) <UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI STYLE="margin:0 0 0 48;">PS22 – Blacks Run</LI><LI STYLE="margin:0 0 0 48;">PS23 – Cooks Creek</LI><LI STYLE="margin:0 0 0 48;">PS26 – North River-Mill Creek</LI><LI STYLE="margin:0 0 0 48;">PS33 – Cub Rub</LI><LI STYLE="margin:0 0 0 48;">PS56 – Linville Creek</LI><LI STYLE="margin:0 0 0 48;">PS59 – Dry Fork</LI></UL>Watershed(HUC 8)<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI STYLE="margin:0 0 0 48;">02070005 – South Fork Shenandoah</LI><LI STYLE="margin:0 0 0 48;">02070006 – North Fork Shenandoah </LI></UL>InstallDate - this is the year that the BMP was physically installed.Notes:- Isn’t always the same as year the agreement was signed.- For old BMPs, this might be the date of plans.- For new BMPs, this is the date the as built has been approved.OwnedBy – designation of the entity that has ownership of the BMP<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI STYLE="margin:0 0 0 48;">Private</LI><LI STYLE="margin:0 0 0 48;">City</LI></UL>MaintainedBy - designation of the entity that is responsible for maintaining the BMP<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI STYLE="margin:0 0 0 48;">Private</LI><LI STYLE="margin:0 0 0 48;">City</LI></UL>LastInspectionDate - date of the last inspection on the BMP site Condition – conditional status the BMP is in, pulls from Inspection Report ConditionDate - date of condition Report filingEnabled – 1 or 0Attachment– static photo taken in the field during inspectionsPlanLink - file path to location where site plans for the corresponding BMP are foundInspectionLink – link to City Works report formStatus – refer to supervisor on specifications for this fieldLocation – closest address to incident location, full address - without ZIP codePlanDate – date of the site plan where the corresponding outfalls are foundUnique_ID - Unique identifying value assigned to a feature, generally same as OBJECTIDSECTION 3Handling of Data and Recommendations<TABLE STYLE="margin:0 0 0 0;"><TBODY><TR><TD STYLE="padding:1 1 1 1;">Tax Map ID#</TD><TD STYLE="padding:1 1 1 1;">The "Tax Map Number" field should correspond to the location of the BMP- NOT the parcel that it services.</TD><TD STYLE="padding:1 1 1 1;">If a BMP that handles runoff from one parcel, but is located in another parcel, then the "Tax Map Number" field should contain the parcel it is located in.</TD></TR><TR><TD STYLE="padding:1 1 1 1;">BMP's in City Right-Of-Way</TD><TD STYLE="padding:1 1 1 1;">This pertains to any BMP's that fall outside of Tax Parcels, but are within the city ROW. ***Notation: Sheet# Block# ‘City ROW’(Example: 124 B City ROW)</TD><TD STYLE="padding:1 1 1 1;">***Sheet and Block numbers should correspond to the closest and most appropriate parcels, relative to the location of the BMP.</TD></TR><TR><TD STYLE="padding:1 1 1 1;">Overlapping BMP's</TD><TD STYLE="padding:1 1 1 1;">Only 1 instance of a particular BMP should be mapped, unless otherwise directed. </TD><TD STYLE="padding:1 1 1 1;">If multiple points are being used to describe 1 BMP, any new or existing points should be discussed, as to their necessity in consolidation of data.</TD></TR><TR><TD STYLE="padding:1 1 1 1;">Site Plans - BMP Locations</TD><TD STYLE="padding:1 1 1 1;">The locations of BMP's are delineated directly from their location as shown in their corresponding site plan.</TD><TD STYLE="padding:1 1 1 1;">Digitizing point locations is easiest by using an up-to-date aerial imagery layer.</TD></TR><TR><TD STYLE="padding:1 1 1 1;">Site Plans / Plan Links - Research</TD><TD STYLE="padding:1 1 1 1;">Site plans are found in the P-drive ("Parcellookup"), in the "scans" folder. "Site Development Project Archives" is a subfolder that should also to be searched.*</TD><TD STYLE="padding:1 1 1 1;">*The content in "Site Development Project Archives" should be used and linked before content from "scans"</TD></TR><TR><TD STYLE="padding:1 1 1 1;">Plan Links - Which Site Plans to Use</TD><TD STYLE="padding:1 1 1 1;">The site plans used in the attributes table contains direct visual representation of the BMP to be mapped in GIS, w/out any detailing information.</TD><TD STYLE="padding:1 1 1 1;"></TD></TR><TR><TD STYLE="padding:1 1 1 1;">Using Plan Links</TD><TD STYLE="padding:1 1 1 1;">Only 1 site plan should be linked in the Plan Link field at any time. If conflict with more than 1, the plan that best pertains to the BMP should be used.</TD><TD STYLE="padding:1 1 1 1;">If folder is in "scans" folder, include file path with pdf doc. name, ending in ".pdf" If folder is in "Site Development Project Archives," link the folder's file path.</TD></TR><TR><TD STYLE="padding:1 1 1 1;">Total Acres Treated</TD><TD STYLE="padding:1 1 1 1;">This applies to any type of BMP that handles surface runoff. The value for this field may be found in the site plan.</TD><TD STYLE="padding:1 1 1 1;">These values need to be recalculated in most instances.</TD></TR><TR><TD STYLE="padding:1 1 1 1;">Impervious Acres Treated</TD><TD STYLE="padding:1 1 1 1;">This applies to any type of BMP that handles surface runoff from impervious surfaces. The value for this field may be found in the site plan.</TD><TD STYLE="padding:1 1 1 1;"></TD></TR><TR><TD STYLE="padding:1 1 1 1;">Nutrient Credit Purchase</TD><TD STYLE="padding:1 1 1 1;">For more information on how to handle Nutrient Credit Purchases in GIS, please contact Kelley Junco, MS4 Program Coordinator, at Public Works Dept.</TD><TD STYLE="padding:1 1 1 1;">It is unclear as to whether these events should be mapped at this time.</TD></TR></TBODY></TABLE>SECTION 4Additional ConsiderationsA. History & Logic of the Data- 10/18/2018 (KELLEY:) I think the BMP layer should have only ONE single point representing the BMP. Inspectors should not be using the GIS’ BMP point to inspect, only to [generally] locate and track BMPs. They should be using the as-built and/or plan set showing the BMP components. B. Department Notes- Wouldn’t the various structures (aside from ponds, of course) be reflected if the following layers were turned on? There is no need to repeat points in the swBMPs layer when structures are mapped in the following layers:swPIPESTRUCTURESswSTORMPIPESswDROPINLETC. Unresolved Questions- [Include any questions about or related to the data.]D. OtherCityworks Tracking Needs – we need to discuss these items furtherInspection DateSee Details within Inspection Forms – unique forms for each BMPMaintenance DatesWhat was performed …Cost…. Reports – how would these reports get generated?List of BMPs with owner information, HUC codes, etc. See DEQ Historic BMP spreadsheet for idea. List of City owned BMPs onlyWhere would department ownership information be visible? Questions / Considerations about:Nancy’s ID numbers vs Cityworks?Send Mark copy of Nancy’s Access DatabasesShare DEQ Historical Database with Sam – summer intern project to update GIS layers?Purchased Nutrient Credits to meet development stormwater quality requirementsSome hydrodynamic separators have been saved in stormstructures layer instead of BMPs. These need to move into BMPs. Parent – Child Features List (In CityWorks) for Detention/Retention/Bioretention PondsTrash Rack PresentYesNoTrash Rack MaterialMetalPlasticOrifice PresentYesNoSize: (Manual Entry)Sediment ForebayYesNoEmergency SpillwayYesNoForebay SpillwayYes NoSpillway MaterialGrass-linedRiprapConcrete</DIV> Feature Class dataset EPSG 5.3(9.0.0) 0 Simple FALSE 0 TRUE FALSE swBMPs Feature Class 0 OBJECTID OBJECTID OID 4 10 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. ProjectName Project Name String 255 0 0 TaxMapNumber Tax Map Number String 50 0 0 Longitude Longitude Double 8 38 8 Latitude Latitude Double 8 38 8 DeedBookNumber Deed Book Number String 50 0 0 DateofAgreement Date of Agreement String 50 0 0 AgreementType Agreement Type String 255 0 0 BMPType BMP Type String 255 0 0 ManufacturedBMPSystem Manufactured BMP System String 255 0 0 TotalAcresTreated Total Acres Treated String 255 0 0 ImperviousAcresTreated Impervious Acres Treated Double 8 38 8 DominantWatershedVAHU6 Dominant Watershed VAHU6 String 100 0 0 WatershedHUC8 Watershed HUC8 String 100 0 0 InstallDate Install Date Date 8 0 0 OwnedBy Owned By String 50 0 0 MaintainedBy Maintained By String 50 0 0 LastInspectionDate Last Inspection Date Date 8 0 0 Condition Condition SmallInteger 2 5 0 ConditionDate Condition Date Date 8 0 0 Enabled Enabled SmallInteger 2 5 0 Attachment Attachment String 50 0 0 PlanLink Plan Link String 255 0 0 InspectionLink Inspection Link String 255 0 0 Status Status String 255 0 0 Location Location String 255 0 0 PlanDate Plan Date String 50 0 0 UniqueID Unique ID String 50 0 0 SHAPE SHAPE Geometry 4 0 0 Feature geometry. Esri Coordinates defining the features. created_user created_user String 255 0 0 created_date created_date Date 8 0 0 last_edited_user last_edited_user String 255 0 0 BMPIDNBR BMP ID Number String 15 0 0 last_edited_date last_edited_date Date 8 0 0 20230424