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

Layer: BMPs (ID: 6)

View In:   ArcGIS Online Map Viewer

Name: BMPs

Display Field: ProjectName

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: INDEXSection 1: Responsible PartiesSection 2: Explanation of Attribute DataSection 3: Handling of Data and RecommendationsSection 4: Additional ConsiderationsSECTION 1 Responsible PartiesParties responsible for updating this layer:- The GIS Specialist is responsible for updating both layers for all new BMPs installed from site plans- MS4 Coordinator/Public Works Environmental Compliance Manager will update Property Type and Agreement date if maintenance agreement was signed for stormwater utilitySECTION 2Explanation of Attribute DataProject Name – enter name of development project BMP is associated withTax MapNumber – 3-part tax map identification number where the point is located, Sheet# Block# Parcel # Longitude – this is required for DEQ reporting Latitude – 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. DateofAgreement – month/date/year that maintenance agreement was recordedAgreementType – Private BMP without Agreement: These BMPs willnothave 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 ChannelsSoil AmendmentVegetated RoofRainwater HarvestingPermeable PavementInfiltrationBioretentionDry SwaleWet SwaleFiltering PracticesConstructed WetlandWet PondsExtended Detention PondDetention BasinRetention BasinSand FiltersManufactured BMP SystemsRegenerative Stormwater Conveyance SystemStream RestorationNutrient Credit PurchasedNotes: - If Manufactured BMP System, then add field for manual entry of system name. ManufacturedBMPSystem – type of BMP system installed, refer to supervisor on specifications for this fieldTotal AcresTreated – 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. Dominant Watershed(VAHU6) PS22 – Blacks RunPS23 – Cooks CreekPS26 – North River-Mill CreekPS33 – Cub RubPS56 – Linville CreekPS59 – Dry ForkWatershed(HUC 8)02070005 – South Fork Shenandoah02070006 – North Fork Shenandoah InstallDate - 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 BMPPrivateCityMaintainedBy - designation of the entity that is responsible for maintaining the BMPPrivateCityLastInspectionDate - date of the last inspection on the BMP site Condition – conditional status the BMP is in, pulls from Inspection Report ConditionDate - date of condition Report filingEnabled – 1 or 0Attachment– static photo taken in the field during inspectionsPlanLink - file path to location where site plans for the corresponding BMP are foundInspectionLink – link to City Works report formStatus – refer to supervisor on specifications for this fieldLocation – closest address to incident location, full address - without ZIP codePlanDate – date of the site plan where the corresponding outfalls are foundUnique_ID - Unique identifying value assigned to a feature, generally same as OBJECTIDSECTION 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- 10/18/2018 (KELLEY:) I think the BMP layer should have only ONE single point representing the BMP. Inspectors should not be using the GIS’ BMP point to inspect, only to [generally] locate and track BMPs. They should be using the as-built and/or plan set showing the BMP components. B. Department Notes- Wouldn’t the various structures (aside from ponds, of course) be reflected if the following layers were turned on? There is no need to repeat points in the swBMPs layer when structures are mapped in the following layers:swPIPESTRUCTURESswSTORMPIPESswDROPINLETC. Unresolved Questions- [Include any questions about or related to the data.]D. OtherCityworks Tracking Needs – we need to discuss these items furtherInspection DateSee Details within Inspection Forms – unique forms for each BMPMaintenance DatesWhat was performed …Cost…. Reports – how would these reports get generated?List of BMPs with owner information, HUC codes, etc. See DEQ Historic BMP spreadsheet for idea. List of City owned BMPs onlyWhere would department ownership information be visible? Questions / Considerations about:Nancy’s ID numbers vs Cityworks?Send Mark copy of Nancy’s Access DatabasesShare DEQ Historical Database with Sam – summer intern project to update GIS layers?Purchased Nutrient Credits to meet development stormwater quality requirementsSome hydrodynamic separators have been saved in stormstructures layer instead of BMPs. These need to move into BMPs. Parent – Child Features List (In CityWorks) for Detention/Retention/Bioretention PondsTrash Rack PresentYesNoTrash Rack MaterialMetalPlasticOrifice PresentYesNoSize: (Manual Entry)Sediment ForebayYesNoEmergency SpillwayYesNoForebay SpillwayYes NoSpillway MaterialGrass-linedRiprapConcrete

Copyright Text: City of Harrisonburg Public Works Department

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

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