PublicWorks/Illicit_Discharges (FeatureServer)

View In: ArcGIS Online Map Viewer

View Footprint In: ArcGIS Online Map Viewer

Service Description:

Description of ms4IllicitDischarges:

INDEX

Section 1: Responsible Parties

Section 2: Explanation of Attribute Data

Section 3: Handling of Data and Recommendations

Section 4: Additional Considerations

SECTION 1

Responsible Parties

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

Explanation of Attribute Data

UniqueID - Unique identifying value assigned to a feature, generally same as OBJECTID

IncidenID – 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-01

DateReported – Date suspected illicit discharge reported to City/ staff was made aware of discharge

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

IncidentType:

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.

InvestigationStatus

Open – investigation still is ongoing, case is still open
Closed – incident resolved and case has been closed

DateInvestigationClosed – The date that the investigation has been officially resolved

InvestigationLink – Linked to City Works report

Location – Closest address to incident location, full address - without ZIP code

SECTION 3

Handling of Data and Recommendations

Placing a Point
In some cases, a manhole or line is referenced as the incident location, this dataset should use in conjunction with layers:
gis_warehouse.HARRISONBURG.SANITARYsewermanholes
gis_warehouse.HARRISONBURG.SANITARYsewerlines
gis_warehouse.HARRISONBURG.HRRSA_MH
gis_warehouse.HARRISONBURG.HRRSA_LINES
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
Inciden_ID
The "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 closest
Select IDDE’s for Certain Year(s)
Use Definition Query: “DateReported >=” then select the date that all other values should be greater than
Can also use “<=” to select lower values

SECTION 4

Additional Considerations

No similar ESRI layer
Keep as a point database

All Layers and Tables

Has Versioned Data: true

MaxRecordCount: 2000

Supported Query Formats: JSON

Supports Query Data Elements: true

Layers:

MS4 Illicit Discharges (0)

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

Copyright Text: City of Harrisonburg

Spatial Reference: 102746 (2283)

Initial Extent:

Full Extent:

Units: esriFeet

Document Info:

Enable Z Defaults: false

Supports ApplyEdits With Global Ids: false

Support True Curves : true

Only Allow TrueCurve Updates By TrueCurveClients : true

Supports Return Service Edits Option : true

Supports Dynamic Layers: false

Child Resources: Info Query Data Elements Relationships

Supported Operations: Query Query Contingent Values QueryDomains Extract Changes