ArcGIS REST Services Directory Login | Get Token
Home > services > Test_DPW_Stormwater (FeatureServer) > Stormwater BMPs Help | API Reference
JSON

Layer: Stormwater BMPs (ID: 8)

View In:   ArcGIS Online Map Viewer

Name: Stormwater BMPs

Display Field: ProjectName

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: 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:- The GIS Technician at the Community Development office is responsible for entering new features into the dataset from site plans of recent construction projects in the City of Harrisonburg,- The Systems Analyst at the Public Works Department is responsible for updating and maintaining this layer. Additions or editing of features within this layer should be administered or approved by the Systems Analyst.SECTION 2Explanation of Attribute DataProjectName – Name of project farm pond or BMP is associated withTaxMapNumber– 3-part tax map identification number where the feature is located, Sheet# Block# Parcel #Longitude– this is required for DEQ reportingLatitude - 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.Date of Agreement – month/date/year that maintenance agreement was recordedAgreementType Private BMP without Agreement: These BMPs will not have anything filed here U:\Stormwater\Construction-Post Construction BMPs-E&S-VSMP\Project - Facilities - Private With Maint AgreePrivate BMP required with development, Agreement signed at time of development: These BMPs will be filed here U:\Stormwater\Construction-Post Construction BMPs-E&S-VSMP\Project - Facilities - Private With Maint AgreePrivate 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 U:\Stormwater\Construction-Post Construction BMPs-E&S-VSMP\Project Facilities - Private Existing for SWM Utility Fee (There will not be many of them)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 U:\Stormwater\Utility Fee - Management\Application InformationPublic BMP (City-Owned)Nutrient Credit PurchasedNotes:- 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 installedDisconnectionSheet FlowGrass ChannelSoil AmendmentVegetated RoofRainwater HarvestingPermeable PavementInfiltrationBioretentionDry SwaleWet SwaleFiltering PracticesConstructed WetlandsWet PondsExtended Detention PondsDetention BasinRetention BasinManufactured BMP SystemsRegenerative Stormwater Conveyance SystemNutrient Credit PurchasedSand FilterUnderground Detention BasinNotes:- If Manufactured BMP System, then add field for manual entry of system name. - Domain: “BMP_Type”ManufacturedBMPSystem- type of BMP system installed, refer to supervisor on specifications for this fieldTotalAcresTreated- 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.HyrdrologicUnitCode6 – dominantwatershed farm pond or BMP is located inPS22 – Blacks RunPS23 – Cooks CreekPS26 – North River-Mill CreekPS33 – Cub RubPS56 – Linville CreekPS59 – Dry ForkNotes:- Domain: “BMP_Dominant_Watershed_VAHU6”HyrdrologicUnitCode12 – watershed farm pond or BMP is located inInstallDate- 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.CityOtherNotes:- Domain: “BMP_Owned_By”MaintainedBy- designation of the entity that is responsible for maintaining the BMP.CityOtherNotes:- Domain: “BMP_Maintained_By”Attachment– static photo of the BMP.Plan Link– file path to location where site plans for the corresponding BMP is found.InspectionLink- link to the City Works report form.Status – Status of the BMP.ActiveAbandonedRemovedProposedNotes:- Domain: “Storm_Structure_Status”Location - closest address to BMP's location, full address - without ZIP code.PlanDate – date of the site plan where the corresponding BMP is found.UniqueID - unique identifying value assigned to a feature, generally same as OBJECTID.Shape - geometric shape of these features are polygonsGlobalID- default editor tracking field, unique serial number for the feature.created_user – default editor tracking field, who created the feature.created_date – default editor tracking field, when the feature was created.last_edited_user– default editor tracking field, who last edited the feature.last_edited_date - default editor tracking field, when the feature was last edited.Shape.STArea() - default field, area of the polygonShape.STLength() – default field, length of the polygonSECTION 3Handling of Data and RecommendationsTax Map ID#The "Tax Map Number" field should correspond to the location of the BMP- NOT the parcel that it services.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.BMP's in City Right-Of-WayThis 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)***Sheet and Block numbers should correspond to the closest and most appropriate parcels, relative to the location of the BMP.Overlapping BMP'sOnly 1 instance of a particular BMP should be mapped, unless otherwise directed. 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.Site Plans - BMP LocationsThe locations of BMP's are delineated directly from their location as shown in their corresponding site plan.Digitizing point locations is easiest by using an up-to-date aerial imagery layer.Site Plans / Plan Links - ResearchSite 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.**The content in "P:\scans\Site Development Project Archives" should be used and linked before content from "P:\scans"Plan Links - Which Site Plans to UseThe site plans used in the attributes table contains direct visual representation of the BMP to be mapped in GIS, w/out any detailing information.Using Plan LinksOnly 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.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.Total Acres TreatedThis applies to any type of BMP that handles surface runoff. The value for this field may be found in the site plan.These values need to be recalculated in most instances.Impervious Acres TreatedThis 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.Nutrient Credit PurchaseFor more information on how to handle Nutrient Credit Purchases in GIS, please contact Kelley Junco, MS4 Program Coordinator, at Public Works Dept.It is unclear as to whether these events should be mapped at this time.SECTION 4Additional ConsiderationsA. History & Logic of the Data[For future reference, please list facets of the history of the decision-making process related to the data’s use – the howand why things were specifically done the way that they were.] (If the data should be handled/collected a specific way, that should be listed and explained here.)------B. Department Notes- Cityworks will need to track:Last Inspection DateConditionLast Maintenance DateSchedule MaintenanceC. Unresolved Questions- Link Unique_ID with that of Stormwater BMPs?D. Other- Not all BMPs will exist in this polygon layer. - Only BMPs greater than 4’x4’ will be in this layer. - Both above and underground BMPs will be here.- This layer is primarily for map making.

Copyright Text: The Drop Inlets data layer was created by Kathy Walker in the Department of Community Development of the City of Harrisonburg, on 6/21/2016. This information was created under the supervision of the Systems Analyst and in association with the City of Harrisonburg.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 15000.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Supports Datum Transformation: true

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

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field:

Fields: Templates:
Capabilities: Query,Create,Update,Delete,Uploads,Editing

Sync Can Return Changes: true

Is Data Versioned: true

Supports Rollback On Failure: false

Supports ApplyEdits With Global Ids: false

Supports ApplyEdits By Upload Id: true

Edit Fields Info:
Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Supported Operations:   Query   Query Attachments   Query Analytic   Apply Edits   Add Features   Update Features   Delete Features   Calculate   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata