ArcGIS REST Services Directory Login | Get Token
Home > services > EA_Waters (MapServer) > Non-Pond Stormwater BMPs API Reference
JSON

Layer: Non-Pond Stormwater BMPs (ID: 8)

Name: Non-Pond Stormwater BMPs

Display Field: Address

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: Goal eventually is to enter a description of all the fields- Gregg and Jessie can work on this.Here is some info to start:"Maintenance Responsibility" for other waterbodies will also be aliased as "MS4/Maintenance Responsibility": For WATERBODIES, there will be no difference between who is responsible for maintenance and who has MS4 jurisdiction/responsibility. This may not be true for other stormwater infrastructure, but it is true for waterbodies. This field has a domain with these values: City of Eagan, Private, Dakota Co, State of MN. A BMP's maintenance responsibility could be more simply just that- who is the entity responsible for maintaining? This will mean something different than the waterbodies maintenace responsibility field.Domain values are:City of Eagan = city inspects, maintains, reports .Private = a private owner is responsible for maintenance; the City still does the inspectionsCounty = they inspect via their own MS4 (this is basically anything inside Lebanon Hills)State = meaning MN DOT. They inspect via their MS4. We do not have or need access.For the purposes of submitting the required list of non-pond BMPs to the state of MN in March 2015, we will submit anything that's City or Private but not County or State becuase they have their own MS4s. Exceptions may occur; deal with these case by case; see applicable maintenance agreements/JPAs etc).MS4Inspection (Yes/No) = Is it required by this permit to be inspected? For non-pond BMPs, annual inspections are required. Most of the time this will be "yes" but these will be inspected by Water Quality staff, not utilities staff.Access Status = For waterbodies, access may be more difficult. Most non-pond BMPs will either be on public ROW or in a private location, not always with an easement, but because part of the maintenance agreement will ask for city staff to do yearly inspection, this field may not apply as much here as it would to waterbodies. Use this field (with its domain values) as much as applies.MS4 Inspection year (1-5) and comments year (1-5): Because annual inspections are required by the MS4 permit, we can reord the date these were done and any comments here, in a rotating 5-year inspection. For example if you inspect a BMP in 2014, 2015, 2016, 2017, and 2018, these will be recorded in years 1 thru 5. Then when you inspect in 2019, it will replace year 1 and so on. Really what are the chances of having the same system in 5 years anyway?? but that's the idea at the moment.

Copyright Text:

Default Visibility: false

MaxRecordCount: 1000

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

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: BMPFeatureType

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

  Iteminfo   Thumbnail   Metadata