Name: MS4 Illicit Discharges

Display Field: UniqueID

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: 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:Suspect (Illicit Discharge): A dumping activity or spill that has not entered the storm sewer system or a live waterway.Potential (Illicit Discharge): A pollutant having entered the storm sewer system but there is no evidence that the pollutant entered a live waterway.Actual (Illicit Discharge): A pollutant having entered the storm sewer system and there is evidence that the pollutant entered a live waterway.InvestigationStatusOpen – investigation still is ongoing, case is still openClosed – incident resolved and case has been closedDateInvestigationClosed – 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 RecommendationsPlacing a PointIn 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_LINESThe 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 locationsInciden_IDThe "Tax Map Number" field should correspond to the location of the IDDE - NOT the parcel that it services.Should be within a parcel, otherwise use closestSelect IDDE’s for Certain Year(s)Use Definition Query: “DateReported >=” then select the date that all other values should be greater thanCan also use “<=” to select lower valuesSECTION 4Additional ConsiderationsNo similar ESRI layer Keep as a point database

Service Item Id: 1cf1e4499f54491abd71fac0241b25df

Copyright Text: City of Harrisonburg

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

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.136487292783758E7
YMin: 6827413.01855506
XMax: 1.1387276582505241E7
YMax: 6857285.6668148935
Spatial Reference: 102746  (2283)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
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 )
• IncidentID ( type: esriFieldTypeString, alias: Incident_ID, length: 255 )
• DateReported ( type: esriFieldTypeDate, alias: Date_Reported, length: 8 )
• IncidentTMNumber ( type: esriFieldTypeString, alias: Incident_TM_Number, length: 255 )
• IncidentType ( type: esriFieldTypeString, alias: IncidentType, length: 255 , Coded Values: [Potential: Potential] , [Actual: Actual] , [Suspect: Suspect] , ...1 more... )
• InvestigationStatus ( type: esriFieldTypeString, alias: Investigation_Status, length: 255 , Coded Values: [Open: Open] , [Closed: Closed] , [Complete: Complete] , ...1 more... )
• DateInvestigationClosed ( type: esriFieldTypeDate, alias: Date_Investigation_Closed, length: 8 )
• InvestigationLink ( type: esriFieldTypeString, alias: Investigation_Link, length: 255 )
• Location ( type: esriFieldTypeString, alias: Location, length: 255 )
• 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 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )

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

  Iteminfo   Thumbnail   Metadata