20160719 15571400 1.0 FALSE ms4IllicitDischarges 002 11365076.701052 11387276.582505 6827413.018555 6857285.666815 1 ms4IllicitDischarges__ATTACHREL Relationship ms4IllicitDischarges__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>-100000</ZOrigin><ZScale>10000</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 10211500 20230424 10211500 150000000 5000 ItemDescription Version 6.2 (Build 9200) ; Esri ArcGIS 10.8.1.14362 ms4IllicitDischarges 0.000000 0.000000 1 -78.911640 -78.833713 38.477959 38.395683 The Illicit Discharges layer is a point-based dataset that documents the locations of Illicit Discharge Detection & Elimination events throughout the city of Harrisonburg, VA. This layer will contain the data needed for Public Works, Cityworks, and MS4 stormwater tracking and will be included in the annual report to the Department of Environmental Quality. <DIV STYLE="text-align:Left;">Description of ms4IllicitDischarges:INDEXSection 1: Responsible PartiesSection 2: Explanation of Attribute DataSection 3: Handling of Data and RecommendationsSection 4: Additional ConsiderationsSECTION 1Responsible PartiesParties responsible for updating this layer:- MS4 Coordinator/Public Works Environmental Compliance Manager will maintain database, as needed.- City Works will be responsible for managing inspection forms as well as schedule/remind staff to conduct follow up’s.SECTION 2Explanation of Attribute DataUniqueID - Unique identifying value assigned to a feature, generally same as OBJECTIDIncidenID – Tax Map ID Number and Date incident was first observed Notes: - Format: Tax Map ID Number [Space] Date- (000-A-00) (YYYY-MM-DD)- Example: 035-X-3 2 014-08-01DateReported – Date suspected illicit discharge reported to City/ staff was made aware of dischargeIncidentTMNumber - 3-part tax map identification number where the feature is located, Sheet# Block# Parcel # Notes:- Format: 000-A-00- Example: 035-X-3 2 014-08-01IncidentType:<OL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI STYLE="margin:0 0 0 60;">Suspect (Illicit Discharge): A dumping activity or spill that has not entered the storm sewer system or a live waterway.</LI><LI STYLE="margin:0 0 0 60;">Potential (Illicit Discharge): A pollutant having entered the storm sewer system but there is no evidence that the pollutant entered a live waterway.</LI><LI STYLE="margin:0 0 0 60;">Actual (Illicit Discharge): A pollutant having entered the storm sewer system and there is evidence that the pollutant entered a live waterway.</LI></OL>InvestigationStatus<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI STYLE="margin:0 0 0 48;">Open – investigation still is ongoing, case is still open</LI><LI STYLE="margin:0 0 0 48;">Closed – incident resolved and case has been closed</LI></UL>DateInvestigationClosed – The date that the investigation has been officially resolvedInvestigationLink – Linked to City Works report Location – Closest address to incident location, full address - without ZIP codeSECTION 3Handling of Data and Recommendations<TABLE STYLE="margin:0 0 0 0;"><TBODY><TR><TD STYLE="padding:1 1 1 1;">Placing a Point</TD><TD STYLE="padding:1 1 1 1;">In some cases, a manhole or line is referenced as the incident location, this dataset should use in conjunction with layers:gis_warehouse.HARRISONBURG.SANITARYsewermanholesgis_warehouse.HARRISONBURG.SANITARYsewerlinesgis_warehouse.HARRISONBURG.HRRSA_MHgis_warehouse.HARRISONBURG.HRRSA_LINES</TD><TD STYLE="padding:1 1 1 1;">The point for the IDDE incident should be as close to the actual area of the incident as possible, use other layers as reference for point locations</TD></TR><TR><TD STYLE="padding:1 1 1 1;">Inciden_ID</TD><TD STYLE="padding:1 1 1 1;">The "Tax Map Number" field should correspond to the location of the IDDE - NOT the parcel that it services.</TD><TD STYLE="padding:1 1 1 1;">Should be within a parcel, otherwise use closest</TD></TR><TR><TD STYLE="padding:1 1 1 1;">Select IDDE’s for Certain Year(s)</TD><TD STYLE="padding:1 1 1 1;">Use Definition Query: “DateReported >=” then select the date that all other values should be greater than</TD><TD STYLE="padding:1 1 1 1;">Can also use “<=” to select lower values</TD></TR></TBODY></TABLE>SECTION 4Additional Considerations<OL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI STYLE="margin:0 0 0 24;">No similar ESRI layer </LI><LI STYLE="margin:0 0 0 24;">Keep as a point database</LI></OL></DIV> City of Harrisonburg City of Harrisonburg Stormwater Runoff IDDE Illicit Illicit Discharge Illicit Discharges Discharge Discharges Feature Class dataset EPSG 5.3(9.0.0) 0 Simple FALSE 0 TRUE FALSE ms4IllicitDischarges Feature Class 0 OBJECTID OBJECTID OID 4 10 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. UniqueID Unique_ID String 50 0 0 IncidentID Incident_ID String 255 0 0 DateReported Date_Reported Date 8 0 0 IncidentTMNumber Incident_TM_Number String 255 0 0 IncidentType IncidentType String 255 0 0 InvestigationStatus Investigation_Status String 255 0 0 DateInvestigationClosed Date_Investigation_Closed Date 8 0 0 InvestigationLink Investigation_Link String 255 0 0 Location Location String 255 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 last_edited_date last_edited_date Date 8 0 0 20230424